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:
common
has been removed, or more correctly it has been merged intosystem
. All system-wide software is now installed (only) insystem
.The
develop
directory has been removed and its contents has been moved to thesystem/develop
directory.The
include
directory has been removed. Its contents lives indevelop/headers
now.optional
has been removed. Optional features can just be installed via the package manager.share
andetc
(incommon
) have been removed. Their contents goes todata
,documentation
, orsettings
(insystem
or, for packages installed there, inhome
) as appropriate. There’ssettings/etc
which is where ported Unix software will usually store their global settings.apps
andpreferences
have been moved tosystem
for consistency.system
andhome/config
each sport apackages
directory, which contains the activated packages.system
andhome/config
themselves are mount points for two instances of the packagefs, i.e. each contains the virtually extracted contents of the activated packages in the respectivepackages
subdirectory. 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.system
andhome/config
each contain a directorynon-packaged
which has the same structure as their parent directory minus the shine-through directories. In thenon-packaged
directories software can be installed the traditional – non-packaged – way.