Boot Volume Directory Structure¶
This is the directory layout of the boot volume:
home/config <like system, but without haiku_loader, kernel_<arch>, and runtime_loader> system add-ons apps bin boot cache* data demos develop documentation lib non-packaged* packages* preferences servers settings* var* haiku_loader kernel_<arch> runtime_loader trash
The structure mostly equals the pre-package management directory structure with the following changes:
commonhas been removed, or more correctly it has been merged into
system. All system-wide software is now installed (only) in
developdirectory has been removed and its contents has been moved to the
includedirectory has been removed. Its contents lives in
optionalhas been removed. Optional features can just be installed via the package manager.
common) have been removed. Their contents goes to
systemor, for packages installed there, in
home) as appropriate. There’s
settings/etcwhich is where ported Unix software will usually store their global settings.
preferenceshave been moved to
home/configeach sport a
packagesdirectory, which contains the activated packages.
home/configthemselves are mount points for two instances of the packagefs, i.e. each contains the virtually extracted contents of the activated packages in the respective
packagessubdirectory. The directories marked with
*are “shine-through” directories. They are not provided by the packagefs, but are the underlying directories of the boot volume. Unlike the other directories they are writable.
home/configeach contain a directory
non-packagedwhich has the same structure as their parent directory minus the shine-through directories. In the
non-packageddirectories software can be installed the traditional – non-packaged – way.