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 505224
To view parent comment, click here.
To read all comments associated with this story, please click here.
cjcoats
Member since:
2006-04-16

AND /bin and /sbin had statically linked executables, so that you can't corrupt the essential part of the system by installing a malicious .so (still true on the BSDs but no longer true on Linux, where the ideology is to have everything possible dynamically linked, in spite of the fact that vendors' insufficiently-tested .so's break mission critical apps. Much too frequently.

Reply Parent Score: 4

Lennie Member since:
2007-09-22

The part about statically linked executables isn't true these days on all Linux/Unix, it just is: without dependencies on /usr

Then again in Linux you just have an initrd these days anyway.

Reply Parent Score: 2