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 505308
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: why not / instead of /usr
by phoenix on Tue 31st Jan 2012 17:57 UTC in reply to "RE[5]: why not / instead of /usr"
Member since:

User installed application gets put into /usr, along with all the "OS" utilities. Some user-installed apps end up in /opt. Which goes where is completely random.

Every single configuration file for the OS utilities and user installed apps is jumbled together into /etc. And then split between /etc/default, /etc/<appname>, /etc/<appname>/conf.d-style directories, and a few other places.

Log files are scattered around /var/log, /var/run, /var/lib, /var/<appname>.

The Linux filesystem hierarchy is a mess.

Reply Parent Score: 3