Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
General Unix Finally something really interesting to talk about. If you've used UNIX or any of its derivatives, you've probably wondered why there's /bin, /sbin, /usr/bin, /usr/sbin in the file system. You may even have a rationalisation for the existence of each and every one of these directories. The thing is, though - all these rationalisations were thought up after these directories were created. As it turns out, the real reasoning is pretty damn straightforward.
Thread beginning with comment 505215
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: About time...
by shmerl on Mon 30th Jan 2012 23:26 UTC in reply to "RE[4]: About time..."
shmerl
Member since:
2010-06-08

You can see problems with it already with scripts hardcoding /usr/bin or something. Normally you don't have to change anything since it already works, it's just at some point legacy clutter becomes too numerous obscuring the big picture.

Edited 2012-01-30 23:27 UTC

Reply Parent Score: 4

RE[6]: About time...
by WorknMan on Tue 31st Jan 2012 01:12 in reply to "RE[5]: About time..."
WorknMan Member since:
2005-11-13

You can see problems with it already with scripts hardcoding /usr/bin or something. Normally you don't have to change anything since it already works, it's just at some point legacy clutter becomes too numerous obscuring the big picture.


Yes, and we who are Windows users know this well ;) Glad to see we're not the only ones dealing with it. One thing we all seem to have in common is that backwards compatibility = the bane of our existence.

Reply Parent Score: 4