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 505185
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Wow, That Was Simple
by kenji on Mon 30th Jan 2012 21:33 UTC in reply to "RE[2]: Wow, That Was Simple"
Member since:

/boot or something similar would also be necessary to have it mounted read only.

The problem with dumping files into a less 'structured' hierarchy is that you limit versatility and customization options. Is it better to have 500+ executables in one directory rather than ORGANIZING (ie compartmentalizing) them?

I think the best solution lies somewhere in between over simplifying and over complicating.

Edited 2012-01-30 21:35 UTC

Reply Parent Score: 6