If you say "stuff should be in a /config file in someone's home" you are
bound to confuse everyone. Prepending a slash means you are talking
about an entry in the root. If you want to describe something in
someone's home, say ~/config.
Andrei
On 1/28/11 2:19 PM, spir wrote:
On 01/28/2011 08:32 PM, Jonathan M Davis wrote:
Exactly; there should definitely/config (for /all/ user definable config
> files). That's one of the numerous points showing how the std Unix
> filesystem hierarchy is designed for sysadmins, not for users ;-)
And why would I want /config for all users? The config files in $HOME
are user-
specific and have no business being system specific. It's /etc that
has system
specific config files. And maybe /config would have been a better name
than /etc,
but I don't think that a name change would help anything at this point.
Regardless, I_want_ my user-specific settings to be user-specific. I
see_zero_
benefit in putting them in /config. That makes no sense to me whatsoever.
Indeed. I did not write "all users" but "all user definable config
files". Maybe should have added a hyphen "all user-definable config
files"? I did not mean that all users should have the same configs, lol!
rather that user configs should be in a /config folder (inside their
home); thus files (1) don't clutter their home folder (2) don't need be
hidden.
Denis
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
