Linked by Thom Holwerda on Thu 28th May 2009 19:17 UTC
Permalink for comment 365925
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-06
It's not worth quibbling over such a distinction. No matter what name you choose, there will be exceptions unless you just want to call it 'stuff'. 'bin' is short, concise and easy to type.
The choice of usr as a name was questionable, but I'm not really sure what else you'd call it frankly. One reason for its existence is that it should be sharable over NFS amongst multiple boxes.
/svr is suppose to be for read-only files. /var is for read-write. That said, almost no packagers actually follow the spec here. Again, /svr is supposed to be sharable via NFS.
The stuff under /etc aren't necessarily config files. The init system lives in there for one. Yes, while it is used for configuration, the init script are not themselves configuration files. It also often gets used as a dumping ground for ad hoc scripts written by systems admins for backups, reports, ETC (emphasis intended).
I don't think spelling everything out, capitalization and using naive categorization schemes really adds anything useful. There are 30 years of accumulated wisdom in the current layout. Wanting to throw it all away reminds of me fresh out school CS graduates that always want to throw the existing code base away and start over because everyone before them were obviously idiots.