- System devices, namely the devfs.
- User home directories only. No applications will have any directories here
as ftp and http have in the past.
- Mount points for floppy, zip disks, nfs shares, etc.
- One directory per application.
<appname>/whatever else the app wants
- Symlinks to binaries found in /sys/apps/<appname>/bin/*.
- System configuration files.
- System kernels.
- Kernel modules.
- Symlinks to libraries found in /sys/apps/<appname>/lib/*. Also, system libraries that don't pertain to any particular application.
- System logs. Not logs pertaining to individual apps (they go in /sys/apps/<appname>/log/).
- Symlinks to man pages found in /sys/apps/<appname>/man/*. Also, system man pages that don't pertain to any particular application, such as those for the system libraries.
- The proc filesystem.
- Mount point for shm filesystem.
- Here is root's home dir. Placed here since it must exist even if /home isn't mounted.
- Temporary files.
- One directory per application--same format as for /sys/apps/.
- Symlinks to binaries found in /usr/apps/<appname>/bin/*.
- Symlinks to libraries found in /usr/apps/<appname>/lib/*.
- Symlinks to man pages found in /usr/apps/<appname>/man/*.
Stricter 'domains' of control
This layout allows a more natural mapping to control domains:
- The only place where an end user actually modifies files (except tmp and mnt).
- Controlled by the system (well, system apps, but user initiated or automounted).
(ie, no user will ever have to know what it means to 'mount' something)
- Files here are owned and controlled by the distribution itself--not applications.
- Files here are pretty much domain-less since this is scratch space.
- Controlled by applications. This is their only system-wide playground. Apps
of course can have user-specific data stored in the user's home dirs.
Simpler Resultant Environment
This directory layout results in a much simpler environment: