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 505208
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: About time...
by shmerl on Mon 30th Jan 2012 22:59 UTC in reply to "RE[2]: About time..."
shmerl
Member since:
2010-06-08

Sounds good, but the name itself is totally obsolete. It could be renamed from /usr to /system or something, but I guess legacy weight is too big for it.

Reply Parent Score: 2

RE[4]: About time...
by Carewolf on Mon 30th Jan 2012 23:22 in reply to "RE[3]: About time..."
Carewolf Member since:
2005-09-08

Don't break things if you don't have to. You can always present it in a nicer way in the GUI, but don't break things if you don't have to..

Reply Parent Score: 2

RE[5]: About time...
by shmerl on Mon 30th Jan 2012 23:26 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[4]: About time...
by r_a_trip on Tue 31st Jan 2012 09:17 in reply to "RE[3]: About time..."
r_a_trip Member since:
2005-07-06

Sounds good, but the name itself is totally obsolete. It could be renamed from /usr to /system or something, but I guess legacy weight is too big for it.

Why? What is wrong with Unified System Resources? :-D

Reply Parent Score: 4