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 505223
To read all comments associated with this story, please click here.
RE[2]: why not / instead of /usr
by kragil on Mon 30th Jan 2012 23:56 UTC in reply to "RE: why not / instead of /usr"
Member since:

I don't think it makes a big difference wheter it is / or /usr, but I'll add my .02 cents anyway:

Long run / for real files (Fedora 18,19, maybe 20):


that looks pretty tidy _to_me_, but I'll admit it is not obvious what all the dirs do, but it can be explained in a few sentences if you are interested. People with no interest will never get any filesystem PERIOD
Cluttering that with runtime dirs and bin, games, include, lib, libexec, local, sbin, share, src and tmp really makes it a mess.
Everything else will be either not as flexible or will still need explaining.

Edited 2012-01-31 00:00 UTC

Reply Parent Score: 6