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 505331
To read all comments associated with this story, please click here.
RE[2]: why not / instead of /usr
by milki on Tue 31st Jan 2012 21:16 UTC in reply to "RE: why not / instead of /usr"
milki
Member since:
2012-01-31

That's what I thought too. Consolidation makes sense, but why further the / root and /usr split, if that was the historic problem to begin with?

And if I have a look at my root directory:

bin cdrom hardy initrd.img.old lib64 media proc sbin sys usr vmlinuz.old
boot dev home lib lost+found mnt root selinux tftpboot var www
build etc initrd.img lib32 maverick opt run srv tmp vmlinuz

And then at my /usr:

bin etc games include lib lib32 lib64 local sbin share src

It's clear which the appendix is. And if you were to move the /usr stuff onto main (nowadays have only one partition anyway), then there would hardly be additions.

But it also becomes appearant that "/games" is kind of redundant. There's little point in having a separate binary directory for one type of applications. That is just other historic cruft (namely to shame those users who have games installed). Likewise should /include actually be part of /src. And I'm not entirely sure about /share, but that should probably go into /var anyway.

Reply Parent Score: 1