On Tue, Aug 31, 2010 at 04:33:25PM -0400, seth vidal wrote:
> 1. More with Less
[...]
try removing dbus sometime... I can't remember - why is dbus
needed on a
KVM guest? yum remove dbus\*
I think the case can be made that dbus is a useful technology for a lot of
server systems. But I agree, it's the sort of thing where the case needs to
be made.
> 2. Avoid Churn at the Core
[...]
Should the churn be avoided BETWEEN releases, too? Ie: f13->f14
should
we avoid core churn?
You're right; the statement should include that too. The balance is
_different_ at that point, but yes, there's a cost there too, and that cost
should be remembered.
> 3. Fedora is Unix-like
[...]
Except when they are obsoleted and ignored and the only way to get
them
back in place is to have a long thread vociferously arguing for them.
Good times, that. It doesn't take a lot of those to stop wanting to be
involved at all, does it?
Yeah. That's why we put this somewhere in some guiding principles.
> 4. The Command Line is Power, and Key=Value is a Key Value
[...]
So gconf and dconf are..... what? A tree of key=value pairs,
aren't
they?
If you config file needs trees, you are probably Doing It Wrong.
For example, see:
http://sourceforge.net/mailarchive/message.php?msg_name=20100827144215.GA...
(I have high hopes for that actually going somewhere, by the way. It's too
bad I didn't look at it before the RHEL6 documentation was written.)
Ever looked inside the gconf variables that evolution makes?
You'll claw
your eyes out.
Key=Accounts
Value=<xmldump>
Hey, if I clawed my eyes out every time I saw a horrible configuration file
syntax choice, I would have been run out of eyes a long time ago.
But yeah. Gconf is a stellar example of Please, Not Like That. The files are
text, but they are not meant for human consumption.
--
Matthew Miller <mattdm(a)mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Harvard School of Engineering & Applied Sciences