Ken Moffat wrote: > On Tue, Dec 20, 2011 at 05:50:31PM -0600, Bruce Dubbs wrote: >> My only concern is to keep something like the /etc directory at a >> reasonable number of entries. Right now I have 90. Compare that to >> ubuntu that has 217 or RHEL with 199. I think of the /etc directory as >> a place where I may need to browse to figure out a file to update. >> Something like php.ini is OK because it is only one file. A few more is >> not a problem, but I think 200 is too many. It just makes sense to me >> to group related functionality together. >> > Just out of interest, how often do you update files in /etc (or, if > I've misunderstood, read them to update a file somewhere else) ? > The only time I remember doing that in the last 2+ years was when I > looked at the pulse files (trying to get it to work). Arguably, I > should mention that I update vimrc on every build (so, I know what I > want there, but a new builder might need to experiment), and > similarly I create the dhclient-exit-hooks. But, *on a desktop* > (since we're talking about gnome) - what else do you expect to look > at to get it working ?
I guess my philosophy is that I want to know why every entry in /etc is there. Since I'm developing for the book, I look at /etc all the time. I'm not sure what I would expect to update for a desktop, but I certainly would look in /etc/kde if I was investigating a problem. Sometimes the gui interfaces in a desktop will update something (more likely in ~/.kde), but for system updates, it's good to at least recognize what files affect what you are seeing. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
