Re: And what about using "Brain"
> Yes, I mean the thing stuffed inside
> your head.
> Why do you need single configuration
> interface to
> all things that can be configured? Are
> you too lazy
> to learn how to configure each single
> one by one?
> Are you too lame?
This is not intended as flame either, but you have got to be kidding. While I agree that you should learn how to configure commonly used programs, the problem is that it can be as hard as hell to figure out how to configure less common applications.
I mean, I often do support for third party systems. I waste a lot of time trying to figure out how they've configured their systems. For instance, some applications might put a configuration file in /etc, and others in /usr/local/etc, and others in /etc/appname, and still others in /usr/share/appname or /usr/local/share/appname or /usr/local/appname/conf. The configuration files may or may not have a logical relationship to the name of the application, so locate doesn't necessarily help.
[Don't get me started on documentation, either. Some programs use info, some man, some use html docs, and for some you have to read the startup script or the source to figure it out.]
While the author's proposal sounds a bit overengineered to me, I do think he's trying to address a real need. Personally, stricter adherence to existing standards (a la the LSB) would go a long ways towards helping.