Linked by Thom Holwerda on Sat 23rd Aug 2008 15:37 UTC
Editorial Earlier this week, we ran a story on GoboLinux, and the distribution's effort to replace the Filesystem Hierarchy Standard with a more pleasant, human-readable, and logical design. A lot of people liked the idea of modernising/replacing the FHS, but just as many people were against doing so. Valid arguments were presented both ways, but in this article, I would like to focus on a common sentiment that came forward in that discussion: normal users shouldn't see the FHS, and advanced users are smart enough to figure out how the FHS works.
Thread beginning with comment 327803
To read all comments associated with this story, please click here.
Comment by synclee
by synclee on Sun 24th Aug 2008 10:17 UTC
synclee
Member since:
2006-06-21

How about a filesystem layed out as this:

/Home
    /User
        /Applications
        /Settings
        /Frameworks
        /Data
        /Documents
        /Desktop
        /Temp
/Common
    /Applications
    /Settings
    /Frameworks
    /Data
    /Documents
    /Desktop
    /Temp
/Shared
    /WWW
    /FTP
    /NFS
/System
    /Applications
    /Settings
    /Frameworks
    /Data
    /Documents
    /Desktop
    /Temp
/Boot
    /Applications
    /Settings
    /Frameworks
    /Data
    /Documents
    /Desktop
    /Temp

A FS would be split into the five domains below the root (/) levet: Boot, System, Shared, Common and Home. The Boot domain would contain files vital to the system bootstrap and nothing else. This domain will be always local, and reside on the separate read-only flash device. The System domain will contain rest of the OS, including drivers and frameworks for advanced functions such as network, sound and accelerated graphics. Common domain is for application and data common to all local users. All non-vital services such as HTTP servers should be placed here. Home domain is for user files only, and the Shared domain must only contain resources shared over network. A technology like unionfs should be implemented, so if there are files /Home/User/Applications/ping, /Common/Applications/ping and System/Applications/ping only third should be visible on the working system, second should be visible to the users which don't have /Home/User/Application/ping, and /System/Applications/ping is only for startup and system maintenance.

Reply Score: 0

RE: Comment by synclee
by sorpigal on Sun 24th Aug 2008 11:55 in reply to "Comment by synclee"
sorpigal Member since:
2005-11-02

Define "boot". When my laptop boots I get a graphical login screen. Should X be in the boot domain?

I see that you advocate a unionfs solution, so that could answer this question. It's certainly an interesting approach. I'm trying to say... be careful, because deciding which things belong in which domain can be very tricky and debatable.

Also please be aware that no system which includes routinely capitalized first letters is likely to replace the current FHS. There's really no harm to saying /system/application/ping, is there?

Reply Parent Score: 2

RE[2]: Comment by synclee
by synclee on Sun 24th Aug 2008 15:31 in reply to "RE: Comment by synclee"
synclee Member since:
2006-06-21

No, is should not. /Boot (or /boot) should contain only kernel, storage and system console drivers, a set of hardware testing and filesystem repair tools and a flashing tool for updating the /Boot from some storage device.

Services for user authentification, network, graphic, sound, etc should be in /System, along with WM and decorator, frameworks like OpenGL and OpenAL and servers. Also, here is where system configuration tools should be placed.

/Common and /Home/John Doe/ sould contain user level application only.

Reply Parent Score: 1