Re: Spaces, the filename frontier...
> Or to better yet improve the
> configuration system, we could have:
> /System Preferences/*.xml
> It's about time we migrate folder
> names to Plain Damn English. If someone
> has a real religious problem with this, [...]
A big problem with that is that many existing shell scripts assume that there are no spaces in file names. The shell splits lines into tokens on whitespace. Spaces in filenames thus cause trouble unless the scripts are carefully written. (insert perl banner ad here). Zsh and Bash both support array variables, and filenames can be gotten via "find -print0"...
It would take a certain amount of effort to audit all scripts for this weakness. It would also require the addition of a clause in the distribution policy document, and once that's done, all new scripts would require audits for "sif" (space if filename) bugs.
Re: And what about using "Brain"
The real problem is not having to edit conffiles, but that there is so much redundancy in them. How many of them contain the hostname, or the IP, or ranges of IP's, etc. When you change your hostname or domain, you must edit several conffiles to fix things up. That's not very often on most boxes, but what about on a laptop?
The big thing that a centralized conf manager would do would be to consolidate that redundant data... to normalize the global confdata schema.