Viewing file:  fhs-3.0.html (218.3 KB) -rw-r--r--
Select action/file-type:
 (+) | (+) |  (+) | Code (+) | Session (+) |  (+) | SDB (+) |  (+) |  (+) |  (+) |  (+) |  (+) |
Filesystem Hierarchy StandardFilesystem Hierarchy StandardLSB Workgroup, The Linux FoundationCopyright © 2015 The Linux Foundation Copyright © 1994-2004 Daniel Quinlan Copyright © 2001-2004 Paul 'Rusty' Russell Copyright © 2003-2004 Christopher Yeoh All trademarks and copyrights are owned by their owners, unless
specifically noted otherwise. Use of a term in this document should not
be regarded as affecting the validity of any trademark or service
mark. Permission is granted to make and distribute verbatim copies of
this standard provided the copyright and this permission notice are
preserved on all copies. Permission is granted to copy and distribute modified versions of this
standard under the conditions for verbatim copying, provided also that
the title page is labeled as modified including a reference to the
original standard, provided that information on retrieving the original
standard is included, and provided that the entire resulting derived
work is distributed under the terms of a permission notice identical to
this one. Permission is granted to copy and distribute translations of this
standard into another language, under the above conditions for modified
versions, except that this permission notice may be stated in a
translation approved by the copyright holder. Abstract This standard consists of a set of requirements and guidelines for file
and directory placement under UNIX-like operating systems. The
guidelines are intended to support interoperability of applications,
system administration tools, development tools, and scripts as well as
greater uniformity of documentation for these systems.
This release is dedicated to the memory of Christopher Yeoh,
a long-time friend and colleague, and one of the original editors
of the FHS. Without his dedication this work would not have been possible.
This standard enables: Software to predict the location of installed files and
directories, and Users to predict the location of installed files and
directories.
We do this by: Specifying guiding principles for each area of the filesystem, Specifying the minimum files and directories required, Enumerating exceptions to the principles, and Enumerating specific cases where there has been historical conflict.
The FHS document is used by: Independent software suppliers to create applications which are FHS
compliant, and work with distributions which are FHS compliant, OS creators to provide systems which are FHS compliant, and Users to understand and maintain the FHS compliance of a system.
The FHS document has a limited scope: Local placement of local files is a local issue, so FHS does not
attempt to usurp system administrators. FHS addresses issues where file placements need to be coordinated
between multiple parties such as local sites, distributions,
applications, documentation, etc.
We recommend that you read a typeset version of this document rather
than the plain text version. In the typeset version, the names of files
and directories are displayed in a constant-width font. Components of filenames that vary are represented by a description
of the contents enclosed in "<" and
">" characters,
<thus>. Electronic mail addresses are also
enclosed in "<" and ">" but are shown in the usual
typeface. Optional components of filenames are enclosed in
"[" and "]" characters and may
be combined with the "<" and
">" convention. For example, if a filename is
allowed to occur either with or without an extension, it might be
represented by
<filename>[.<extension>]. Variable substrings of directory names and filenames are indicated
by "*". The sections of the text marked as
Rationale are explanatory and are
non-normative. Chapter 2. The FilesystemThis standard assumes that the operating system underlying an
FHS-compliant file system supports the same basic security features
found in most UNIX filesystems. It is possible to define two independent distinctions among
files: shareable vs. unshareable and variable vs. static. In general,
files that differ in either of these respects should be located in
different directories. This makes it easy to store files with
different usage characteristics on different filesystems. "Shareable" files are those that can be stored on one host
and used on others. "Unshareable" files are those that are not
shareable. For example, the files in user home directories are
shareable whereas device lock files are not. "Static" files include binaries, libraries, documentation
files and other files that do not change without system administrator
intervention. "Variable" files are files that are not static. RationaleShareable files can be stored on one host and used on several
others. Typically, however, not all files in the filesystem
hierarchy are shareable and so each system has local storage
containing at least its unshareable files. It is convenient if all
the files a system requires that are stored on a foreign host can be
made available by mounting one or a few directories from the foreign
host. Static and variable files should be segregated because static
files, unlike variable files, can be stored on read-only media and
do not need to be backed up on the same schedule as variable
files. Historical UNIX-like filesystem hierarchies contained both
static and variable files under both /usr and
/etc. In order to realize the advantages
mentioned above, the /var hierarchy was
created and all variable files were transferred from
/usr to /var.
Consequently /usr can now be mounted read-only
(if it is a separate filesystem). Variable files have been
transferred from /etc to
/var over a longer period as technology has
permitted. Here is an example of a FHS-compliant system.
(Other FHS-compliant layouts are possible.) Chapter 3. The Root FilesystemThe contents of the root filesystem must be adequate to boot,
restore, recover, and/or repair the system. To boot a system, enough software and data must be present on the root partition
to mount other filesystems. This includes utilities, configuration,
boot loader information, and other essential start-up data.
/usr, /opt, and
/var are designed such that they may be located
on other partitions or filesystems. To enable recovery and/or repair of a system, those utilities
needed by an experienced maintainer to diagnose and reconstruct a
damaged system must be present on the root filesystem. To restore a system, those utilities needed to restore from
system backups (on floppy, tape, etc.) must be present on the root
filesystem.
RationaleThe minimum requirements for the root filesystem should be as
small as reasonably possible, but no smaller. While many users may
not want the extra complexity of a partitioned system, the option to
keep the root small should be preserved for several reasons: It is occasionally mounted from very small media. The root filesystem contains many system-specific configuration
files. Possible examples include a kernel that is specific to the
system, a specific hostname, etc. This means that the root filesystem
isn't always shareable between networked systems. Keeping it small on
servers in networked systems minimizes the amount of lost space for
areas of unshareable files. It also allows workstations with smaller
local hard drives. While you may have the root filesystem on a large partition, and
may be able to fill it to your heart's content, there will be people
with smaller partitions. If you have more files installed, you may
find incompatibilities with other systems using root filesystems on
smaller partitions. If you are a developer then you may be turning
your assumption into a problem for a large number of users. Disk errors that corrupt data on the root filesystem are a
greater problem than errors on any other partition. A small root
filesystem is less prone to corruption as the result of a system
crash.
These considerations must be balanced against the need for a
minimally useful operating environment, for the sake of the boot
process as well as in failure recovery situations. Applications must never create or require special files or
subdirectories in the root directory. Other locations in the FHS
hierarchy provide more than enough flexibility for any package. RationaleThere are several reasons why creating a new subdirectory of
the root filesystem is prohibited: It demands space on a root partition which the system
administrator may want kept small and simple for either performance or
security reasons. It evades whatever discipline the system administrator may have
set up for distributing standard file hierarchies across mountable
volumes.
Distributions should not create new directories in the root
hierarchy without extremely careful consideration of the consequences
including for application portability. The following directories, or symbolic links to directories, are
required in /. Each directory listed above is specified in detail in separate
subsections below. /usr and
/var each has a complete section in this
document due to the complexity of those directories. The following directories, or symbolic links to directories,
must be in /, if the corresponding subsystem is
installed: Each directory listed above is specified in detail in separate
subsections below. 3.4. /bin : Essential user command binaries (for use by all users)/bin contains commands that may be used by
both the system administrator and by users, but which are required
when no other filesystems are mounted (e.g. in single user mode). It
may also contain commands which are used indirectly by scripts.
There must be no subdirectories in /bin. The following commands, or symbolic links to commands, are
required in /bin: If /bin/sh is not the POSIX compatible shell
command itself, it must be a hard or symbolic link to the real shell
command. The [ and test
commands must be placed together in either /bin
or /usr/bin. RationaleVarious shells behave differently when called as
sh, so as to preserve POSIX compatibility while
allowing changes or extensions to POSIX when desired. The requirement for the [ and
test commands to be included as binaries (even if
implemented internally by the shell) is shared with the POSIX.1-2008
standard. The following programs, or symbolic links to programs, must be
in /bin if the corresponding subsystem is
installed: /bin/csh may be a symbolic link to
/bin/tcsh or
/usr/bin/tcsh. RationaleThe tar, gzip
and cpio
commands have been added to make restoration of a
system possible (provided that / is intact). Conversely, if no restoration from the root partition is ever
expected, then these binaries might be omitted (e.g., a ROM chip root,
mounting /usr through NFS). If restoration of a
system is planned through the network, then ftp
or tftp (along with everything necessary to get
an ftp connection) must be available on the root partition. 3.5. /boot : Static files of the boot loaderThis directory contains everything required for the boot process
except configuration files not needed at boot time and the map
installer. Thus /boot stores data that is used
before the kernel begins executing user-mode programs. This may
include saved master boot sectors and sector map files. Programs necessary to arrange for the boot loader to be able to
boot a file must be placed in /sbin.
Configuration files for boot loaders that are not required at boot
time must be placed in /etc. The operating system kernel must be located in either
/ or /boot. Certain architectures may have other requirements for
/boot related to limitations or expectations
specific to that architecture. These requirements are not enumerated
here; distributions are allowed to add requirements as needed to
enable system startup on these architectures. The /dev directory is the location of
special or device files. If it is possible that devices in /dev will
need to be manually created, /dev must contain a
command named MAKEDEV, which can create devices
as needed. It may also contain a MAKEDEV.local
for any local devices. If required, MAKEDEV must have provisions
for creating any device that may be found on the system, not just
those that a particular distribution installs. 3.7. /etc : Host-specific system configurationThe /etc hierarchy contains configuration
files. A "configuration file" is a local file used to control the
operation of a program; it must be static and cannot be an executable
binary.
It is recommended that files be stored in subdirectories of
/etc rather than directly in
/etc.
No binaries may be located under
/etc. The following directories, or symbolic links to directories are
required in /etc: The following directories, or symbolic links to directories must
be in /etc, if the corresponding subsystem is
installed: The following files, or symbolic links to files, must be in
/etc if the corresponding subsystem is
installed:
mtab does not fit the static nature of
/etc: it is excepted for historical reasons.
3.7.4. /etc/opt : Configuration files for /optHost-specific configuration files for add-on application
software packages must be installed within the directory
/etc/opt/<subdir>, where
<subdir> is the name of the subtree in
/opt where the static data from that package is
stored. No structure is imposed on the internal arrangement of
/etc/opt/<subdir>. If a configuration file must reside in a different location in
order for the package or system to function properly, it may be placed
in a location other than
/etc/opt/<subdir>. RationaleRefer to the rationale for /opt. 3.7.5. /etc/X11 : Configuration for the X Window System (optional)/etc/X11 is the location for all X11
host-specific configuration. This directory is necessary to allow
local control if /usr is mounted read
only. 3.7.5.2. Specific OptionsThe following files, or symbolic links to files, must be in
/etc/X11 if the corresponding subsystem is
installed: Subdirectories of /etc/X11 may include
those for xdm and for any other programs (some
window managers, for example) that need them.
3.7.6. /etc/sgml : Configuration files for SGML (optional)Generic configuration files defining high-level parameters of
the SGML systems are installed here. Files with names
*.conf indicate generic configuration files.
File with names *.cat are the DTD-specific
centralized catalogs, containing references to all other catalogs
needed to use the given DTD. The super catalog file
catalog references all the centralized
catalogs. 3.7.7. /etc/xml : Configuration files for XML (optional)Generic configuration files defining high-level parameters of
the XML systems are installed here. Files with names
*.conf indicate generic configuration files.
The super catalog file
catalog references all the centralized
catalogs. 3.8. /home : User home directories (optional)/home is a fairly standard concept, but it
is clearly a site-specific filesystem.
The setup will differ from host to host. Therefore, no program should
assume any specific location for a home directory, rather it
should query for it.
User specific configuration files for applications are stored in the
user's home directory in a file that starts with the '.' character (a
"dot file"). If an application needs to create more than one dot file
then they should be placed in a subdirectory with a name starting with
a '.' character, (a "dot directory"). In this case the configuration
files should not start with the '.' character.
3.8.3. Home Directory Specifications and Conventions
A number of efforts have been made in the past to standardize
the layout of home directories,
including the XDG Base Directories specification
and the GLib conventions on user directory contents.
Additional efforts in this direction are possible in the future.
To accomodate software which makes use of these specifications and conventions,
distributions may create directory hierarchies which follow
the specifications and conventions. Those directory hierarchies may be located
underneath home directories.
3.9. /lib : Essential shared libraries and kernel modulesThe /lib directory contains those shared
library images needed to boot the system and run the commands in the
root filesystem, ie. by binaries in /bin and
/sbin.
At least one of each of the following filename patterns are
required (they may be files, or symbolic links): If a C preprocessor is installed, /lib/cpp
must be a reference to it, for historical reasons.
The following directories, or symbolic links to directories,
must be in /lib, if the corresponding subsystem
is installed: 3.10. /lib<qual> : Alternate format essential shared libraries (optional)There may be one or more variants of the
/lib directory on systems which support more than
one binary format requiring separate libraries.
If one or more of these directories exist, the requirements for
their contents are the same as the normal /lib
directory, except that /lib<qual>/cpp is
not required.
3.11. /media : Mount point for removable mediaThis directory contains subdirectories which are used as mount
points for removable media such as floppy disks, cdroms and zip
disks. RationaleHistorically there have been a number of other different places
used to mount removable media such as /cdrom,
/mnt or /mnt/cdrom. Placing
the mount points for all removable media directly in the root
directory would potentially result in a large number of extra
directories in /. Although the use of
subdirectories in /mnt as a mount point has
recently been common, it conflicts with a much older tradition of
using /mnt directly as a temporary mount point.
The following directories, or symbolic links to directories,
must be in /media, if the corresponding subsystem
is installed: On systems where more than one device exists for mounting a
certain type of media, mount directories can be created by appending a
digit to the name of those available above starting with '0', but the
unqualified name must also exist.
3.12. /mnt : Mount point for a temporarily mounted filesystemThis directory is provided so that the system administrator may
temporarily mount a filesystem as needed. The content of this
directory is a local issue and should not affect the manner in which
any program is run. This directory must not be used by installation programs: a
suitable temporary directory not in use by the system must be used
instead. 3.13. /opt : Add-on application software packages/opt is reserved for the installation of
add-on application software packages.
A package to be installed in /opt must
locate its static files in a separate
/opt/<package> or
/opt/<provider> directory
tree, where <package> is a name that
describes the software package and
<provider> is the provider's LANANA
registered name. The directories /opt/bin,
/opt/doc, /opt/include,
/opt/info, /opt/lib, and
/opt/man are reserved for local system
administrator use. Packages may provide "front-end" files intended to
be placed in (by linking or copying) these reserved directories by the
local system administrator, but must function normally in the absence
of these reserved directories. Programs to be invoked by users must be located in the directory
/opt/<package>/bin or under the
/opt/<provider> hierarchy. If the package
includes UNIX manual pages, they must be located in
/opt/<package>/share/man or under the
/opt/<provider> hierarchy, and the same
substructure as /usr/share/man must be
used. Package files that are variable (change in normal operation)
must be installed in /var/opt. See the section
on /var/opt for more information. Host-specific configuration files must be installed in
/etc/opt. See the section on
/etc for more information. No other package files may exist outside the
/opt, /var/opt, and
/etc/opt hierarchies except for those package
files that must reside in specific locations within the filesystem
tree in order to function properly. For example, device lock files
must be placed in /var/lock and devices must be
located in /dev. Distributions may install and otherwise manage software in
/opt under an appropriately registered
subdirectory. RationaleThe use of /opt for add-on software is a
well-established practice in the UNIX community. The System V
Application Binary Interface [AT&T 1990], based on the System V
Interface Definition (Third Edition), provides for an
/opt structure very similar to the one defined
here. The Intel Binary Compatibility Standard v. 2 (iBCS2) also
provides a similar structure for /opt. Generally, all data required to support a package on a system
must be present within /opt/<package>,
including files intended to be copied into
/etc/opt/<package> and
/var/opt/<package> as well as reserved
directories in /opt. The minor restrictions on distributions using
/opt are necessary because conflicts are possible
between distribution-installed and locally-installed software,
especially in the case of fixed pathnames found in some binary
software. The structure of the directories below
/opt/<provider> is left up to the packager
of the software, though it is recommended that packages are installed
in /opt/<provider>/<package> and
follow a similar structure to the guidelines for
/opt/<package>. A valid reason for diverging from
this structure is for support packages which may have files installed
in /opt/<provider>/lib or
/opt/<provider>/bin. 3.14. /root : Home directory for the root user (optional)The root account's home directory may be determined by developer
or local preference, but this is the recommended default
location.
3.15. /run : Run-time variable dataThis directory contains system information data describing the
system since it was booted. Files under this directory must be
cleared (removed or truncated as appropriate) at the beginning of the
boot process. The purposes of this directory were once served by
/var/run. In general, programs may continue to
use /var/run to fulfill the requirements set out
for /run for the purposes of backwards
compatibility. Programs which have migrated to use
/run should cease their usage of
/var/run, except as noted in the section on
/var/run. Programs may have a subdirectory of
/run; this is encouraged for programs that
use more than one run-time file. Users may also have a subdirectory
of /run, although care must be taken to
appropriately limit access rights to prevent unauthorized use of
/run itself and other subdirectories.
Process identifier (PID) files, which were originally placed in
/etc, must be placed in
/run. The naming convention for PID files is
<program-name>.pid. For example, the
crond PID file is named
/run/crond.pid. The internal format of PID files remains unchanged. The file
must consist of the process identifier in ASCII-encoded decimal,
followed by a newline character. For example, if
crond was process number 25,
/run/crond.pid would contain three characters:
two, five, and newline. Programs that read PID files should be somewhat flexible in what
they accept; i.e., they should ignore extra whitespace, leading
zeroes, absence of the trailing newline, or additional lines in the
PID file. Programs that create PID files should use the simple
specification located in the above paragraph. System programs that maintain transient UNIX-domain sockets must
place them in this directory or an appropriate subdirectory as
outlined above. 3.16. /sbin : System binariesUtilities used for system administration (and other root-only
commands) are stored in /sbin,
/usr/sbin, and
/usr/local/sbin. /sbin
contains binaries essential for booting, restoring, recovering, and/or
repairing the system in addition to the binaries in
/bin.
Programs executed after
/usr is known to be mounted (when there are no
problems) are generally placed into /usr/sbin.
Locally-installed system administration programs should be placed into
/usr/local/sbin.
There must be no subdirectories in /sbin. The following commands, or symbolic links to commands, are
required in /sbin: The following files, or symbolic links to files, must be in
/sbin if the corresponding subsystem is
installed: 3.17. /srv : Data for services provided by this system/srv contains site-specific data which is
served by this system.
Rationale
This main purpose of specifying this is so that users may find the
location of the data files for a particular service, and so that
services which require a single tree for readonly data, writable data
and scripts (such as cgi scripts) can be reasonably placed. Data that
is only of interest to a specific user should go in that users' home
directory. If the directory and file structure of the data is not
exposed to consumers, it should go in /var/lib.
The methodology used to name subdirectories of
/srv is unspecified as there is currently no
consensus on how this should be done. One method for structuring data
under /srv is by protocol,
eg. ftp, rsync,
www, and cvs. On large
systems it can be useful to structure /srv by
administrative context, such as /srv/physics/www,
/srv/compsci/cvs, etc. This setup will differ
from host to host. Therefore, no program should rely on a specific
subdirectory structure of /srv existing or data
necessarily being stored in /srv. However
/srv should always exist on FHS compliant systems
and should be used as the default location for such data.
Distributions must take care not to remove locally placed files in
these directories without administrator permission.
3.18. /tmp : Temporary filesThe /tmp directory must be made available
for programs that require temporary files. Programs must not assume that any files or directories in
/tmp are preserved between invocations of the
program. RationaleIEEE standard POSIX.1-2008 lists requirements
similar to the above section. Although data stored in /tmp may be deleted
in a site-specific manner, it is recommended that files and
directories located in /tmp be deleted whenever
the system is booted. FHS added this recommendation on the basis of historical
precedent and common practice, but did not make it a requirement
because system administration is not within the scope of this
standard. Chapter 4. The /usr Hierarchy/usr is the second major section of the
filesystem. /usr is shareable, read-only data.
That means that /usr should be shareable between
various FHS-compliant hosts and must not be written to. Any
information that is host-specific or varies with time is stored
elsewhere.
Large software packages must not use a direct subdirectory under
the /usr hierarchy. The following directories, or symbolic links to directories, are
required in /usr. An exception is made for the X Window System because of
considerable precedent and widely-accepted practice. The following symbolic links to directories may be present. This
possibility is based on the need to preserve compatibility with older
systems until all distribution can be assumed to use the
/var hierarchy.
/usr/spool -> /var/spool
/usr/tmp -> /var/tmp
/usr/spool/locks -> /var/lock
Once a system no longer requires any one of the above symbolic links,
the link may be removed, if desired. 4.4. /usr/bin : Most user commandsThis is the primary directory of executable commands on the
system. There must be no subdirectories in /usr/bin. The following files, or symbolic links to files, must be in
/usr/bin, if the corresponding subsystem is
installed: RationaleIn many executable scripts, the interpreter to be invoked to
execute the script is specified using
#!path_to_interpreter
on the first line of a script.
To make such scripts portable among different systems,
it is advantageous to standardize the interpreter locations.
The shell interpreter is already
fixed in /bin by this specification,
but interpreters for Perl, Python, Tcl and expect may be installed
in various places. The locations specified here may be implemented
as symbolic links to the physical location of the interpreters.
4.5. /usr/include : Directory for standard include files.This is where all of the system's general-use include files for the C
programming language should be placed. The following directories, or symbolic links to directories,
must be in /usr/include, if the corresponding
subsystem is installed: 4.6. /usr/lib : Libraries for programming and packages/usr/lib includes object files and libraries.
On some systems, it may also include internal binaries that are not
intended to be executed directly by users or shell scripts.
Applications may use a single subdirectory under
/usr/lib. If an application uses a subdirectory,
all architecture-dependent data exclusively used by the application
must be placed within that subdirectory.
For historical reasons, /usr/lib/sendmail
must be a symbolic link which resolves to the
sendmail-compatible command provided by the
system's mail transfer agent, if the latter exists.
4.7. /usr/libexec : Binaries run by other programs (optional)/usr/libexec includes internal binaries
that are not intended to be executed directly by users or shell
scripts. Applications may use a single subdirectory under
/usr/libexec.
Applications which use /usr/libexec in this
way must not also use /usr/lib to store internal
binaries, though they may use /usr/lib for the
other purposes documented here. RationaleSome previous versions of this document did not support
/usr/libexec, despite it being standard practice
in a number of environments.
To accomodate this restriction, it became common practice to use
/usr/lib instead. Either practice is now
acceptable, but each application must choose one way or the other to
organize itself.
4.8. /usr/lib<qual> : Alternate format libraries (optional)/usr/lib<qual> performs the same role as /usr/lib for an
alternate binary format, except that the symbolic links
/usr/lib<qual>/sendmail and /usr/lib<qual>/X11 are not required.
4.9. /usr/local : Local hierarchyThe /usr/local hierarchy is for use by the
system administrator when installing software locally. It needs to be
safe from being overwritten when the system software is updated. It
may be used for programs and data that are shareable amongst a group
of hosts, but not found in /usr. Locally installed software must be placed within
/usr/local rather than /usr
unless it is being installed to replace or upgrade software in
/usr.
The following directories, or symbolic links to directories,
must be in /usr/local No other directories, except those listed below, may be in
/usr/local after first installing a FHS-compliant
system. If directories /lib<qual> or
/usr/lib<qual> exist, the equivalent
directories must also exist in /usr/local. /usr/local/etc may be a symbolic link to
/etc/local.
RationaleThe consistency of /usr/local/etc is
beneficial to installers, and is already used in other systems. As
all of /usr/local needs to be backed up to
reproduce a system, it introduces no additional maintenance overhead,
but a symlink to /etc/local is suitable if
systems want all their configuration under one hierarchy.
Note that /usr/etc is still not allowed: programs
in /usr should place configuration files in
/etc.
If the directory /usr/share/color exists as
specified in this document, then the directory
/usr/local/share/color must also exist, governed
by the same rules as /usr/share/color. RationaleThis usage allows the sysadmin a place to install color profiles
manually when necessary. 4.9.4. /usr/local/share : Local architecture-independent hierarchyThe requirements for the contents of this directory are the same
as for /usr/share.
4.10. /usr/sbin : Non-essential standard system binariesThis directory contains any non-essential binaries used
exclusively by the system administrator. System administration
programs that are required for system repair, system recovery,
mounting /usr, or other essential functions must
be placed in /sbin instead.
There must be no subdirectories in /usr/sbin. 4.11. /usr/share : Architecture-independent dataThe /usr/share hierarchy is for all
read-only architecture independent data files.
This hierarchy is intended to be shareable among all
architecture platforms of a given OS; thus, for example, a site with
i386, Alpha, and PPC platforms might maintain a single
/usr/share directory that is centrally-mounted.
Note, however, that /usr/share is generally not
intended to be shared by different OSes or by different releases of
the same OS. Any program or package which contains or requires data that
doesn't need to be modified should store that data in
/usr/share (or
/usr/local/share, if installed locally). It is
recommended that a subdirectory be used in
/usr/share for this purpose. Applications using
a single file may use /usr/share/misc. Game data stored in /usr/share/games must
be purely static data. Any modifiable files, such as score files,
game play logs, and so forth, should be placed in
/var/games. The following directories, or symbolic links to directories,
must be in /usr/share The following directories, or symbolic links to directories, must be in /usr/share, if the corresponding
subsystem is installed: It is recommended that application-specific,
architecture-independent directories be placed here. Such directories
include groff, perl,
ghostscript, texmf, and
kbd (Linux) or syscons
(BSD). They may, however, be placed in /usr/lib
for backwards compatibility, at the distributor's discretion.
Similarly, a /usr/lib/games hierarchy may be used
in addition to the /usr/share/games hierarchy if
the distributor wishes to place some game data there. 4.11.4. /usr/share/color : Color management information (optional)This directory is the home for ICC color management files
installed by the system. 4.11.4.2. Specific
OptionsThe following directories must be in
/usr/share/color, if the corresponding subsystem
is installed: The top-level directory /usr/share/color
must not contain any files; all files should be in subdirectories of
/usr/share/color. 4.11.5. /usr/share/dict : Word lists (optional)This directory is the home for word lists on the system;
Traditionally this directory contains only the English
words file, which is used by
look(1) and various spelling programs.
words may use either American or British
spelling. RationaleThe reason that only word lists are located here is that they
are the only files common to all spell checkers. 4.11.5.2. Specific OptionsThe following files, or symbolic links to files, must be in
/usr/share/dict, if the corresponding subsystem
is installed: Sites that require both American and British spelling may link
words to
/usr/share/dict/american-english or
/usr/share/dict/british-english. Word lists for other languages may be added using the English
name for that language, e.g.,
/usr/share/dict/french,
/usr/share/dict/danish, etc. These should, if
possible, use a character set based on Unicode, with the UTF-8
character set being the preferred option. Other word lists must be included here, if present. 4.11.6. /usr/share/man : Manual pagesThis section details the organization for manual pages
throughout the system, including /usr/share/man.
Also refer to the section on
/var/cache/man. The primary <mandir> of the system is
/usr/share/man.
/usr/share/man contains manual information for
commands and data under the / and
/usr filesystems.
Manual pages are stored in
<mandir>/<locale>/man<section>/<arch>.
An explanation of <mandir>,
<locale>,
<section>, and
<arch> is given below. A description of each section follows: man1: User programs
Manual pages that describe publicly accessible commands are contained in
this chapter. Most program documentation that a user will need to use
is located here.
man2: System calls
This section describes all of the system calls (requests for the
kernel to perform operations).
man3: Library functions and subroutines
Section 3 describes program library routines that are not direct calls
to kernel services. This and chapter 2 are only really of interest to
programmers.
man4: Special files
Section 4 describes the special files, related driver functions, and
networking support available in the system. Typically, this includes
the device files found in /dev and the kernel interface to
networking protocol support.
man5: File formats
The formats for many data files are documented in the
section 5. This includes various include files, program output files,
and system files.
man6: Games
This chapter documents games, demos, and generally trivial programs.
Different people have various notions about how essential this is.
man7: Miscellaneous
Manual pages that are difficult to classify are designated as being
section 7. The troff and other text processing macro packages are found
here.
man8: System administration
Programs used by system administrators for system operation and
maintenance are documented here. Some of these programs are also
occasionally useful for normal users.
4.11.6.2. Specific OptionsThe following directories, or symbolic links to directories,
must be in
/usr/share/<mandir>/<locale>, unless
they are empty:
The component <section> describes the
manual section. Provisions must be made in the structure of
/usr/share/man to support manual pages which are
written in different (or multiple) languages. These provisions must
take into account the storage and reference of these manual pages.
Relevant factors include language (including geographical-based
differences), and character code set. This naming of language subdirectories of
/usr/share/man is based on Appendix E of the
POSIX 1003.1 standard which describes the locale identification string
— the most well-accepted method to describe a cultural
environment. The <locale> string
is: <language>[_<territory>][.<character-set>][,<version>]
The <language> field must be taken
from ISO 639 (a code for the representation of names of languages).
It must be two characters wide and specified with lowercase letters
only. The <territory> field must be the
two-letter code of ISO 3166 (a specification of representations of
countries), if possible. (Most people are familiar with the
two-letter codes used for the country codes in email addresses.) It
must be two characters wide and specified with uppercase letters
only.
The <character-set> field must
represent the standard describing the character set. If the
<character-set> field is just a
numeric specification, the number represents the number of the
international standard describing the character set. It is
recommended that this be a numeric representation if possible (ISO
standards, especially), not include additional punctuation symbols,
and that any letters be in lowercase. A parameter specifying a <version> of
the profile may be placed after the
<character-set> field, delimited by a
comma. This may be used to discriminate between different cultural
needs; for instance, dictionary order versus a more systems-oriented
collating order. This standard recommends not using the
<version> field, unless it is
necessary. Systems which use a unique language and code set for all manual
pages may omit the <locale> substring and
store all manual pages in <mandir>. For
example, systems which only have English manual pages coded with
ASCII, may store manual pages (the
man<section> directories) directly in
/usr/share/man. (That is the traditional
circumstance and arrangement, in fact.) Countries for which there is a well-accepted standard character
code set may omit the <character-set>
field, but it is strongly recommended that it be included, especially
for countries with several competing standards. Various examples: Similarly, provision must be made for manual pages which are
architecture-dependent, such as documentation on device-drivers or
low-level system administration commands. These must be placed under
an <arch> directory in the appropriate
man<section> directory; for example, a man
page for the i386 ctrlaltdel(8) command might be placed in
/usr/share/man/<locale>/man8/i386/ctrlaltdel.8.
Manual pages for commands and data under
/usr/local are stored in
/usr/local/man or
/usr/local/share/man.
All manual page hierarchies in the system must have the same structure as
/usr/share/man, as this structure is expected
by commands which consume manual page content.
The cat page sections (cat<section>)
containing formatted manual page entries are also found within
subdirectories of <mandir>/<locale>,
but are not required nor may they be distributed in lieu of nroff
source manual pages. The numbered sections "1" through "8" are traditionally defined.
In general, the file name for manual pages located within a particular
section end with .<section>. In addition, some large sets of application-specific manual
pages have an additional suffix appended to the manual page filename.
For example, the MH mail handling system manual pages must have
mh appended to all MH manuals. All X Window
System manual pages must have an x appended to
the filename. The practice of placing various language manual pages in
appropriate subdirectories of /usr/share/man also
applies to the other manual page hierarchies, such as
/usr/local/man. (This portion of the standard
also applies later in the section on the optional
/var/cache/man structure.) 4.11.7. /usr/share/misc : Miscellaneous architecture-independent dataThis directory contains miscellaneous architecture-independent
files which don't require a separate subdirectory under
/usr/share. 4.11.7.1. Specific OptionsThe following files, or symbolic links to files, must be in
/usr/share/misc, if the corresponding subsystem
is installed: Other (application-specific) files may appear here, but a distributor
may place them in /usr/lib at their discretion.
4.11.8. /usr/share/ppd : Printer definitions (optional)/usr/share/ppd contains PostScript Printer
Definition (PPD) files, which are used as descriptions of printer
drivers by many print systems. PPD files may be placed in this
directory, or in a subdirectory.
4.11.9. /usr/share/sgml : SGML data (optional)/usr/share/sgml contains
architecture-independent files used by SGML applications, such
as ordinary catalogs (not the centralized ones, see
/etc/sgml), DTDs, entities, or style
sheets.
4.11.9.2. Specific OptionsThe following directories, or symbolic links to directories,
must be in /usr/share/sgml, if the corresponding
subsystem is installed: Other files that are not specific to a given DTD may reside in
their own subdirectory. 4.11.10. /usr/share/xml : XML data (optional)/usr/share/xml contains
architecture-independent files used by XML applications, such
as ordinary catalogs (not the centralized ones, see
/etc/sgml), DTDs, entities, or style
sheets.
4.11.10.2. Specific OptionsThe following directories, or symbolic links to directories,
must be in /usr/share/xml, if the corresponding
subsystem is installed: 4.12. /usr/src : Source code (optional)Source code may be placed in this
subdirectory, only for reference purposes.
Chapter 5. The /var Hierarchy/var contains variable data files. This
includes spool directories and files, administrative and logging data,
and transient and temporary files.
Some portions of /var are not shareable
between different systems. For instance,
/var/log, /var/lock, and
/var/run. Other portions may be shared, notably
/var/mail, /var/cache/man,
/var/cache/fonts, and
/var/spool/news. /var is specified here in order to make it
possible to mount /usr read-only. Everything
that once went into /usr that is written to
during system operation (as opposed to installation and software
maintenance) must be in /var.
If /var cannot be made a separate
partition, it is often preferable to move /var
out of the root partition and into the /usr
partition. (This is sometimes done to reduce the size of the root
partition or when space runs low in the root partition.) However,
/var must not be linked to
/usr because this makes separation of
/usr and /var more difficult
and is likely to create a naming conflict. Instead, link
/var to /usr/var. Applications must generally not add directories to the top level
of /var. Such directories should only be added
if they have some system-wide implication, and in consultation with
the FHS mailing list. The following directories, or symbolic links to directories, are
required in /var: Several directories are `reserved' in the sense that they must
not be used arbitrarily by some new application, since they would
conflict with historical and/or local practice. They are:
/var/backups
/var/cron
/var/msgs
/var/preserve
The following directories, or symbolic links to directories,
must be in /var, if the corresponding subsystem
is installed: 5.4. /var/account : Process accounting logs (optional)This directory holds the current active process accounting log
and the composite process usage data (as used in some UNIX-like
systems by lastcomm and
sa). 5.5. /var/cache : Application cache data/var/cache is intended for cached data from
applications. Such data is locally generated as a result of
time-consuming I/O or calculation. The application must be able to
regenerate or restore the data. Unlike
/var/spool, the cached files can be deleted
without data loss. The data must remain valid between invocations of
the application and rebooting the system.
Files located under /var/cache may be
expired in an application specific manner, by the system
administrator, or both. The application must always be able to
recover from manual deletion of these files (generally because of a
disk space shortage). No other requirements are made on the data
format of the cache directories. RationaleThe existence of a separate directory for cached data allows
system administrators to set different disk and backup policies from
other directories in /var. 5.5.3. /var/cache/fonts : Locally-generated fonts (optional)The directory /var/cache/fonts should be used to store any
dynamically-created fonts. In particular, all of the fonts which are
automatically generated by mktexpk must be located in
appropriately-named subdirectories of /var/cache/fonts.
5.5.3.2. Specific OptionsOther dynamically created fonts may also be placed in this tree,
under appropriately-named subdirectories of
/var/cache/fonts. 5.5.4. /var/cache/man : Locally-formatted manual pages (optional)This directory provides a standard location for sites that provide a
read-only /usr partition, but wish to allow caching of
locally-formatted man pages. Sites that mount /usr as writable
(e.g., single-user installations) may choose not to use
/var/cache/man and may write formatted man pages into the
cat<section> directories in /usr/share/man directly. We
recommend that most sites use one of the following options instead: Preformat all manual pages alongside the unformatted versions. Allow no caching of formatted man pages, and require formatting to be
done each time a man page is brought up. Allow local caching of formatted man pages in /var/cache/man.
The structure of /var/cache/man needs to
reflect both the fact of multiple man page hierarchies and the
possibility of multiple language support. Given an unformatted manual page that normally appears in
<path>/man/<locale>/man<section>,
the directory to place formatted man pages in is
/var/cache/man/<catpath>/<locale>/cat<section>,
where <catpath> is derived from
<path> by removing any leading
usr and/or trailing share
pathname components. (Note that the
<locale> component may be missing.)
Man pages written to /var/cache/man may
eventually be transferred to the appropriate preformatted directories
in the source man hierarchy or expired; likewise
formatted man pages in the source man hierarchy
may be expired if they are not accessed for a period of time. If preformatted manual pages come with a system on read-only
media (a CD-ROM, for instance), they must be installed in the source
man hierarchy
(e.g. /usr/share/man/cat<section>).
/var/cache/man is reserved as a writable cache
for formatted manual pages. RationaleRelease 1.2 of this standard specified
/var/catman for this hierarchy. The path has
been moved under /var/cache to better reflect the
dynamic nature of the formatted man pages. The directory name has
been changed to man to allow for enhancing the
hierarchy to include post-processed formats other than "cat", such as
PostScript, HTML, or DVI. 5.6. /var/crash : System crash dumps (optional)This directory holds system crash dumps. As of the date of this
release of the standard, system crash dumps were not supported under
Linux but may be supported by other systems which may comply with the
FHS. 5.7. /var/games : Variable game data (optional)Any variable data relating to games in /usr
should be placed here. /var/games should hold
the variable data previously found in /usr;
static data, such as help text, level descriptions, and so on, must
remain elsewhere, such as
/usr/share/games. Rationale/var/games has been given a hierarchy of
its own, rather than leaving it underneath
/var/lib as in release 1.2 of this standard.
The separation
allows local control of backup strategies, permissions, and disk
usage, as well as allowing inter-host sharing and reducing clutter in
/var/lib. Additionally,
/var/games is the path traditionally used by BSD.
5.8. /var/lib : Variable state informationThis hierarchy holds state information pertaining to an
application or the system. State information is data that programs
modify while they run, and that pertains to one specific host. Users
must never need to modify files in /var/lib to
configure a package's operation, and the specific file hierarchy
used to store the data must not be exposed to regular users.
State information is generally used to preserve the condition of
an application (or a group of inter-related applications) between
invocations and between different instances of the same application.
State information should generally remain valid after a reboot, should
not be logging output, and should not be spooled data. An application (or a group of inter-related applications) must
use a subdirectory of /var/lib for its data.
There is one required subdirectory,
/var/lib/misc, which is intended for state files
that don't need a subdirectory; the other subdirectories should only
be present if the application in question is included in the
distribution.
/var/lib/<name> is the location that
must be used for all distribution packaging support. Different
distributions may use different names, of course.
The following directories, or symbolic links to directories, are
required in /var/lib: The following directories, or symbolic links to directories, must be in /var/lib, if the
corresponding subsystem is installed: 5.8.4. /var/lib/<editor> : Editor backup files and state (optional)These directories contain saved files generated by any
unexpected termination of an editor (e.g., elvis,
jove, nvi). Other editors may not require a directory for crash-recovery
files, but may require a well-defined place to store other information
while the editor is running. This information should be stored in a
subdirectory under /var/lib (for example, GNU
Emacs would place lock files in
/var/lib/emacs/lock). Future editors may require additional state information beyond
crash-recovery files and lock files — this information should
also be placed under
/var/lib/<editor>. RationalePrevious Linux releases, as well as all commercial vendors, use
/var/preserve for vi or its clones. However,
each editor uses its own format for these crash-recovery files, so a
separate directory is needed for each editor. Editor-specific lock files are usually quite different from the
device or resource lock files that are stored in
/var/lock and, hence, are stored under
/var/lib. 5.8.5. /var/lib/color : Color management information (optional)This directory is the home for ICC color management files
installed dynamically. This directory shall be laid out using the
same rules as the /usr/share/color
directory. 5.8.6. /var/lib/hwclock : State directory for hwclock (optional)This directory contains the file
/var/lib/hwclock/adjtime. RationaleIn FHS 2.1, this file was /etc/adjtime, but
as hwclock updates it, that was obviously
incorrect. 5.8.7. /var/lib/misc : Miscellaneous variable dataThis directory contains variable data not placed in a
subdirectory in /var/lib. An attempt should be
made to use relatively unique names in this directory to avoid
namespace conflicts.
5.9. /var/lock : Lock filesLock files should be stored within the
/var/lock directory structure. Lock files for devices and other resources shared by multiple
applications, such as the serial device lock files that were
originally found in either /usr/spool/locks or
/usr/spool/uucp, must now be stored in
/var/lock. The naming convention which must be
used is "LCK.." followed by the base name of the device. For example,
to lock /dev/ttyS0 the file "LCK..ttyS0" would be created.
The format used for the contents of such lock files must be the
HDB UUCP lock file format. The HDB format is to store the process
identifier (PID) as a ten byte ASCII decimal number, with a trailing
newline. For example, if process 1230 holds a lock file, it would
contain the eleven characters: space, space, space, space, space,
space, one, two, three, zero, and newline. 5.10. /var/log : Log files and directoriesThis directory contains miscellaneous log files. Most logs must
be written to this directory or an appropriate subdirectory. The following files, or symbolic links to files, must be in
/var/log, if the corresponding subsystem is
installed: 5.11. /var/mail : User mailbox files (optional)The mail spool must be accessible through
/var/mail and the mail spool files must take the
form <username>.
User mailbox files in this location must be stored in the standard
UNIX mailbox format. RationaleThe logical location for this directory was changed from
/var/spool/mail in order to bring FHS in-line
with nearly every UNIX distribution. This change is important for
inter-operability since a single /var/mail is
often shared between multiple hosts and multiple UNIX distribution
(despite NFS locking issues). It is important to note that there is no requirement to
physically move the mail spool to this location. However, programs
and header files must be changed to use
/var/mail. 5.12. /var/opt : Variable data for /optVariable data of the packages in /opt must
be installed in /var/opt/<subdir>, where
<subdir> is the name of the subtree in
/opt where the static data from an add-on
software package is stored, except where superseded by another file in
/etc. No structure is imposed on the internal
arrangement of /var/opt/<subdir>. RationaleRefer to the rationale for /opt. 5.13. /var/run : Run-time variable dataThis directory was once intended for system information data
describing the system since it was booted. These functions have been
moved to /run; this directory exists to ensure
compatibility with systems and software using an older version of this
specification. In general, the requirements for /run shall
also apply to /var/run. It is valid to implement
/var/run as a symlink to
/run. The utmp file, which stores information
about who is currently using the system, is located in this
directory. Programs should not access both /var/run
and /run directly, except to access
/var/run/utmp.
5.14. /var/spool : Application spool data/var/spool contains data which is awaiting
some kind of later processing. Data in
/var/spool represents work to be done in the
future (by a program, user, or administrator); often data is deleted
after it has been processed.
The following directories, or symbolic links to directories,
must be in /var/spool, if the corresponding
subsystem is installed: 5.14.3. /var/spool/lpd : Line-printer daemon print queues (optional)The lock file for lpd,
lpd.lock, must be placed in
/var/spool/lpd. It is suggested that the lock
file for each printer be placed in the spool directory for that
specific printer and named lock. 5.14.3.2. Specific Options5.14.4. /var/spool/rwho : Rwhod files (optional)This directory holds the rwhod information
for other systems on the local net. RationaleSome BSD releases use /var/rwho for this
data; given its historical location in /var/spool
on other systems and its approximate fit to the definition of
`spooled' data, this location was deemed more appropriate. 5.15. /var/tmp : Temporary files preserved between system rebootsThe /var/tmp directory is made available
for programs that require temporary files or directories that are
preserved between system reboots. Therefore, data stored in
/var/tmp is more persistent than data in
/tmp. Files and directories located in /var/tmp
must not be deleted when the system is booted. Although data stored
in /var/tmp is typically deleted in a
site-specific manner, it is recommended that deletions occur at a less
frequent interval than /tmp. 5.16. /var/yp : Network Information Service (NIS) database files (optional)Variable data for the Network Information Service (NIS),
formerly known as the Sun Yellow Pages (YP), must be placed in this
directory. Rationale/var/yp is the standard directory for NIS
(YP) data and is almost exclusively used in NIS documentation and
systems.
Chapter 6. Operating System Specific AnnexThis section is for additional requirements and recommendations
that only apply to a specific operating system. The material in this
section should never conflict with the base standard. This is the annex for the Linux operating system. 6.1.1. / : Root directoryOn Linux systems, if the kernel is located in
/, we recommend using the names
vmlinux or vmlinuz, which
have been used in recent Linux kernel source packages. 6.1.2. /bin : Essential user command binaries (for use by all users)Linux systems which require them place these additional files into
/bin: 6.1.3. /dev : Devices and special filesThe following devices must exist under
/dev.
/dev/null
All data written to this device is discarded. A read from this device
will return an EOF condition.
/dev/zero
This device is a source of zeroed out data. All data written to this
device is discarded. A read from this device will return as many bytes
containing the value zero as was requested.
/dev/tty
This device is a synonym for the controlling terminal of a
process. Once this device is opened, all reads and writes will behave
as if the actual controlling terminal device had been opened.
RationalePrevious versions of the FHS had stricter requirements for
/dev.
Other devices may also exist in /dev.
Device names may exist as symbolic links to other device nodes
located in /dev
or subdirectories of /dev.
There is no requirement
concerning major/minor number values.
6.1.4. /etc : Host-specific system configurationLinux systems which require them place these additional files into
/etc. 6.1.5. /proc : Kernel and process information virtual filesystemThe proc filesystem
is the de-facto
standard Linux method for handling process and system information,
rather than /dev/kmem
and other similar methods.
We strongly encourage this for the storage and retrieval of process
information as well as other kernel and memory information. 6.1.6. /sbin : Essential system binariesLinux systems place commands relating to filesystem maintenance and
boot loader management into /sbin.
Optional files for /sbin: Static binaries: Static ln (sln) and
static sync (ssync) are
useful when things go wrong. The primary use of
sln (to repair incorrect symlinks in
/lib after a poorly orchestrated upgrade) is no
longer a major concern now that the ldconfig
program (usually located in /usr/sbin)
exists and
can act as a guiding hand in upgrading the dynamic libraries. Static
sync is useful in some emergency situations.
Note that these need not be statically linked versions of the standard
ln and sync, but may
be. The ldconfig binary is optional for
/sbin since a site may choose to run
ldconfig at boot time, rather than only when
upgrading the shared libraries. (It's not clear whether or not it is
advantageous to run ldconfig on each boot.) Even
so, some people like ldconfig around for the
following (all too common) situation: I've just removed /lib/<file>. I can't find out the name of the library because ls is
dynamically linked, I'm using a shell that doesn't have ls
built-in, and I don't know about using "echo *" as a
replacement. I have a static sln, but I don't know what to call the link.
Miscellaneous: So as to cope with the fact that some keyboards come up with
such a high repeat rate as to be unusable,
kbdrate may be installed in
/sbin on some systems. Since the default action in the kernel for the Ctrl-Alt-Del key
combination is an instant hard reboot, it is generally advisable to
disable the behavior before mounting the root filesystem in read-write
mode. Some init suites are able to disable
Ctrl-Alt-Del, but others may require the
ctrlaltdel program, which may be installed in
/sbin on those systems.
6.1.7. /sys : Kernel and system information virtual filesystemThe sys filesystem
is the location where
information about devices, drivers, and some kernel features is
exposed. Its underlying structure is determined by the particular
Linux kernel being used at the moment, and is otherwise
unspecified. 6.1.8. /usr/include : Header files included by C programsThese symbolic links are required if a C or C++ compiler is
installed and only for systems not based on glibc.
/usr/include/asm -> /usr/src/linux/include/asm-<arch>
/usr/include/linux -> /usr/src/linux/include/linux
6.1.9. /usr/src : Source codeFor systems based on
glibc,
there are no specific guidelines for
this directory. For systems based on Linux
libc revisions prior to
glibc,
the following guidelines and rationale apply: The only source code that should be placed in a specific
location is the Linux kernel source code. It is located in
/usr/src/linux. If a C or C++ compiler is installed, but the complete Linux
kernel source code is not installed, then the include files from the
kernel source code must be located in these directories:
/usr/src/linux/include/asm-<arch>
/usr/src/linux/include/linux
<arch> is the name of the system
architecture.
Note/usr/src/linux
may be a symbolic link to a kernel source code tree.
RationaleIt is important that the kernel include files be located in
/usr/src/linux and not in
/usr/include
so there are no problems when system
administrators upgrade their kernel version for the first time. 6.1.10. /var/spool/cron : cron and at jobsThis directory contains the variable data for the
cron and at programs. 7.2. Background of the FHSThe process of developing a standard filesystem hierarchy began
in August 1993 with an effort to restructure the file and directory
structure of Linux. The FSSTND, a filesystem hierarchy standard
specific to the Linux operating system, was released on February 14,
1994. Subsequent revisions were released on October 9, 1994 and March
28, 1995. In early 1995, the goal of developing a more comprehensive
version of FSSTND to address not only Linux, but other UNIX-like
systems was adopted with the help of members of the BSD development
community. As a result, a concerted effort was made to focus on
issues that were general to UNIX-like systems. In recognition of this
widening of scope, the name of the standard was changed to Filesystem
Hierarchy Standard or FHS for short. Volunteers who have contributed extensively to this standard are
listed at the end of this document. This standard represents a
consensus view of those and other contributors. Thanks to Network Operations at the University of California at
San Diego, and later to SourceForge, who allowed us to use their
excellent mailing list servers during earlier phases of development. Here are some of the guidelines that have been used in the development
of this standard: Solve technical problems while limiting transitional difficulties. Make the specification reasonably stable. Gain the approval of distributors, developers, and other decision-makers
in relevant development groups and encourage their participation. Provide a standard that is attractive to the implementors of different
UNIX-like systems.
This document specifies a standard filesystem hierarchy for FHS
filesystems by specifying the location of files and directories, and
the contents of some system files. This standard has been designed to be used by system
integrators, package developers, and system administrators in the
construction and maintenance of FHS compliant filesystems. It is
primarily intended to be a reference and is not a tutorial on how to
manage a conforming filesystem hierarchy. The FHS grew out of earlier work on FSSTND, a filesystem
organization standard for the Linux operating system. It builds on
FSSTND to address interoperability issues not just in the Linux
community but in a wider arena including 4.4BSD-based operating
systems. It incorporates lessons learned in the BSD world and
elsewhere about multi-architecture support and the demands of
heterogeneous networking. Although this standard is more comprehensive than previous
attempts at filesystem hierarchy standardization, periodic updates may
become necessary as requirements change in relation to emerging
technology. It is also possible that better solutions to the problems
addressed here will be discovered so that our solutions will no longer
be the best possible solutions. Supplementary drafts may be released
in addition to periodic updates to this document. However, a specific
goal is backwards compatibility from one release of this document to
the next. Comments related to this standard are welcome. Any comments or
suggestions for changes may be directed to the
FHS mailing list, or filed as bugs, or both.
Typographical or grammatical comments should be filed as bugs.
The bugtracker is at
http://bugs.linuxfoundation.org
- use the category FHS.
Before sending mail to the mailing list it is requested that you
first glance at the mailing list archives to avoid excessive re-discussion
of old topics. Questions about how to interpret items in this document may
occasionally arise. If you have need for a clarification, please
contact the FHS mailing list. Since this standard represents a
consensus of many participants, it is important to make certain that
any interpretation also represents their collective opinion. For this
reason it may not be possible to provide an immediate response unless
the inquiry has been the subject of previous discussion. The developers of the FHS wish to thank the developers, system
administrators, and users whose input was essential to this standard.
We wish to thank each of the contributors who helped to write,
compile, and compose this standard. The FHS Group also wishes to thank those Linux developers who
supported the FSSTND, the predecessor to this standard. If they
hadn't demonstrated that the FSSTND was beneficial, the FHS could
never have evolved. |