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 intosystem. All system-wide software is now installed (only) insystem.The
developdirectory has been removed and its contents has been moved to thesystem/developdirectory.The
includedirectory has been removed. Its contents lives indevelop/headersnow.optionalhas been removed. Optional features can just be installed via the package manager.shareandetc(incommon) have been removed. Their contents goes todata,documentation, orsettings(insystemor, for packages installed there, inhome) as appropriate. There’ssettings/etcwhich is where ported Unix software will usually store their global settings.appsandpreferenceshave been moved tosystemfor consistency.systemandhome/configeach sport apackagesdirectory, which contains the activated packages.systemandhome/configthemselves are mount points for two instances of the packagefs, i.e. each contains the virtually extracted contents of the activated packages in the respectivepackagessubdirectory. 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.systemandhome/configeach contain a directorynon-packagedwhich has the same structure as their parent directory minus the shine-through directories. In thenon-packageddirectories software can be installed the traditional – non-packaged – way.