Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
Permalink for comment 505296
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-06-12
/system
/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: http://www.osnews.com/story/19711/The_Utopia_of_Program_Management/... ).
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).