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.
Permalink for comment 505177
To read all comments associated with this story, please click here.
RE[3]: Wow, That Was Simple
by saso on Mon 30th Jan 2012 21:24 UTC in reply to "RE[2]: Wow, That Was Simple"
saso
Member since:
2007-04-18

/users
/system
/programs (or /Apps, in this day and age).

More is not needed at root.

What if your boot process forces you to put the kernel and base module on a separate volume? (e.g. you keep most of your OS on a RAID-5/6 volume, but most bootloaders have trouble loading from anything other than a plain or RAID-1 volume).

Also, where do you put site-local overrides for distribution maintainer tools (e.g. a custom version of some libraries)?

Reply Parent Score: 6