On Mon, 2006-12-04 at 12:09 -0500, Matthew Miller wrote:
> I'm just not convinced that not being able to ssh in to a server and edit
> some config files but rather have to figure out how to tweak the
> policy-daemon-of-the-month is the user experience a large segment of "we"
> wants at all. Human-editable config files are a huge strength. Using a
> policy daemon may be part of the answer, but it should be able to get its
> configuration from something that can be fixed with vi.
No-one says you can't have command line tools to set g-p-m preferences
and that you can't use them while logging in via ssh. Heck, since
gconftool-2 already exists you can do this already; just write a small
shell script, gpm-set-governor or whatever, and it'll already work. I
can't speak for Richard but if we do this thing of making g-p-m run in
the unusual cases when no-one is logged in, I'm pretty damn sure he
would take patches providing such functionality. You or others would
probably have to do the work however.
We're not taking functionality away from you and no-one prevents you or
others from writing and using software that utilizes configuration files
if that's what you want. I just don't think this is what Fedora needs in
a default install. And if I have it my way you'll have a much more
powerful way of controlling policy on servers; one that provides UI for
system administrators and one that, down the road, scales to getting the
policy from the network via some futuristic networked LDAP backend for
gconf or whatever. The price you pay? Maybe you'll have to use dedicated
command line tools instead of editing a file in /etc. Understand that
we, the developers of these bits, are actually trying to reach out and
make it easier for system administrators like yourself. Both sides gotta
give a little.
David
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
