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 505296
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Wow, That Was Simple
by Elv13 on Tue 31st Jan 2012 14:53 UTC in reply to "RE[2]: Wow, That Was Simple"
Member since:

/programs (or /Apps, in this day and age).

More is not needed at root.

(although I personally would like to see a /settings as well, as I argued in my proposal: ).

Add /config, /logs /services to that (aka, srv, what var have been renamed too some time ago).

You don't want service data (database, upload, VMs, repositories...) to be with the program data. Those subvolumes/partitions/disks have different backup policy, mount options and SELinux policies. Merginf the two would be a security issue. It would also make impossible to use alternative medium like SAN or NAS.

As for config, you don't want them to be spread across the system. /etc is a terrible name, but the concept is good.

/logs is quite obvious (it fit in no categories you described above, it would be stupid to force it into one).

Reply Parent Score: 2