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 505260
To read all comments associated with this story, please click here.
RE[4]: Wow, That Was Simple
by lindkvis on Tue 31st Jan 2012 09:10 UTC in reply to "RE[3]: Wow, That Was Simple"
lindkvis
Member since:
2006-11-21


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).

Then you fix the bloody bootloader.


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


Wherever you want. Seriously, you can create your own directory structure and put whatever you want there, and then you can add this to the users' PATH ahead of /bin. There is absolutely no reason for every Linux distribution coming with a predefined place for something which is actually a very rare occurrence.

Reply Parent Score: 4