World Library  
Flag as Inappropriate
Email this Article

Filesystem Hierarchy Standard

Article Id: WHEBN0000287790
Reproduction Date:

Title: Filesystem Hierarchy Standard  
Author: World Heritage Encyclopedia
Language: English
Subject: Linux Standard Base, Nokia N900, GoboLinux, Home directory, Unix filesystem
Collection: Computer Standards, File System Directories, Linux, System Administration, Unix File System Technology
Publisher: World Heritage Encyclopedia

Filesystem Hierarchy Standard

Filesystem Hierarchy Standard
Developed by Linux Foundation
Initial release 14 February 1994 (1994-02-14)
Latest release
(3 June 2015 (2015-06-03))
Website Official website
Official website (Historical)

The Filesystem Hierarchy Standard (FHS) defines the directory structure and directory contents in Unix and Unix-like operating systems. It is maintained by the Linux Foundation. The latest version is 3.0, released on 3 June 2015. [1] Currently it is only used by Linux distributions.


  • Directory structure 1
  • FHS compliance 2
  • History 3
    • Release history 3.1
  • See also 4
  • References 5
  • External links 6

Directory structure

In the FHS all files and directories appear under the root directory /, even if they are stored on different physical or virtual devices. Note however that some of these directories may or may not be present on a Unix system depending on whether certain subsystems, such as the X Window System, are installed.

The majority of these directories exist in all UNIX operating systems and are generally used in much the same way; however, the descriptions here are those used specifically for the FHS, and are not considered authoritative for platforms other than Linux.

Directory Description
Primary hierarchy root and root directory of the entire file system hierarchy.
Essential command binaries that need to be available in single user mode; for all users, e.g., cat, ls, cp.
Boot loader files, e.g., kernels, initrd.
Essential devices, e.g., /dev/null.
Host-specific system-wide configuration files

There has been controversy over the meaning of the name itself. In early versions of the UNIX Implementation Document from Bell labs, /etc is referred to as the etcetera directory,[2] as this directory historically held everything that did not belong elsewhere (however, the FHS restricts /etc to static configuration files and may not contain binaries).[3] Since the publication of early documentation, the directory name has been re-explained in various ways. Recent interpretations include backronyms such as "Editable Text Configuration" or "Extended Tool Chest".[4]

Configuration files for add-on packages that are stored in /opt/.
Configuration files, such as catalogs, for software that processes SGML.
Configuration files for the X Window System, version 11.
Configuration files, such as catalogs, for software that processes XML.
Users' home directories, containing saved files, personal settings, etc.
Libraries essential for the binaries in /bin/ and /sbin/.
Alternate format essential libraries. Such directories are optional, but if they exist, they have some requirements.
Mount points for removable media such as CD-ROMs (appeared in FHS-2.3).
Temporarily mounted filesystems.
Optional application software packages.[5]
Virtual filesystem providing process and kernel information as files. In Linux, corresponds to a procfs mount.
Home directory for the root user.
Run-time variable data: Information about the running system since last boot, e.g., currently logged-in users and running daemons.
Essential system binaries, e.g., fsck, init, route.
Site-specific data which are served by the system.
Temporary files (see also /var/tmp). Often not preserved between system reboots, and may be severely size restricted.
Secondary hierarchy for read-only user data; contains the majority of (multi-)user utilities and applications.[6]
Non-essential command binaries (not needed in single user mode); for all users.
Standard include files.
Libraries for the binaries in /usr/bin/ and /usr/sbin/.
Alternate format libraries (optional).
Tertiary hierarchy for local data, specific to this host. Typically has further subdirectories, e.g., bin/, lib/, share/.[7]
Non-essential system binaries, e.g., daemons for various network-services.
Architecture-independent (shared) data.
Source code, e.g., the kernel source code with its header files.
X Window System, Version 11, Release 6 (up to FHS-2.3, optional).
Variable files—files whose content is expected to continually change during normal operation of the system—such as logs, spool files, and temporary e-mail files.
Application cache data. Such data are locally generated as a result of time-consuming I/O or calculation. The application must be able to regenerate or restore the data. The cached files can be deleted without loss of data.
State information. Persistent data modified by programs as they run, e.g., databases, packaging system metadata, etc.
Lock files. Files keeping track of resources currently in use.
Log files. Various logs.
Users' mailboxes.
Variable data from add-on packages that are stored in /opt/.
Run-time variable data. This directory contains system information data describing the system since it was booted.[8]

In FHS 3.0, /var/run is replaced by /run; a system should either continue to provide a /var/run directory, or provide a symbolic link from /var/run to /run, for backwards compatibility.[9]

Spool for tasks waiting to be processed, e.g., print queues and outgoing mail queue.
Deprecated location for users' mailboxes.[10]
Temporary files to be preserved between reboots.

FHS compliance

Most Linux distributions follow the Filesystem Hierarchy Standard and declare it their own policy to maintain FHS compliance.[11][12][13][14] GoboLinux[15] and NixOS[16] provide examples of intentionally non-compliant filesystem implementations.

Some distributions that generally follow the standard deviate from it in some areas. Common deviations include:

  • Modern Linux distributions include a /sys directory as a virtual filesystem (sysfs, comparable to /proc, which is a procfs), which stores and allows modification of the devices connected to the system, whereas many traditional UNIX and Unix-like operating systems use /sys as a symbolic link to the kernel source tree.
  • Many modern UNIX systems (like FreeBSD via its ports system) install third party packages into /usr/local while keeping code considered part of the operating system in /usr.
  • Some Linux distributions no longer differentiate between /lib versus /usr/lib and have /lib symlinked to /usr/lib.[17]
  • Some Linux distributions no longer differentiate between /bin versus /usr/bin and /sbin versus /usr/sbin. They symlink /bin to /usr/bin and /sbin to /usr/sbin. And /usr/sbin may get symlinked to /usr/bin.[18]

Modern Linux distributions include a /run directory as a temporary filesystem (tmpfs) which stores volatile runtime data, following the FHS version 3.0. According to the FHS version 2.3, such data were stored in /var/run but this was a problem in some cases because this directory isn't always available at early boot. As a result, these programs have had to resort to trickery, such as using /dev/.udev, /dev/.mdadm, /dev/.systemd or /dev/.mount directories, even though the device directory isn't intended for such data.[19] Among other advantages, this makes the system easier to use normally with the root filesystem mounted read-only. For example, below are the changes Debian made in its 2013 Wheezy release:[20]

  • /dev/.*/run/*
  • /dev/shm/run/shm
  • /dev/shm/*/run/*
  • /etc/* (writeable files) → /run/*
  • /lib/init/rw/run
  • /var/lock/run/lock
  • /var/run/run
  • /tmp/run/tmp


When the FHS was created, other UNIX and Unix-like operating systems already had their own standards. Notable examples are these: the hier(7) description of file system layout,[21] which has existed since the release of Version 7 Unix (in 1979); the SunOS filesystem(7)[22] and its successor, the Solaris filesystem(5).[23][24]

Release history

Version Release Date Notes
Old version, no longer supported: 1.0 1994-02-14 FSSTND[25]
Old version, no longer supported: 1.1 1994-10-09 FSSTND[26]
Old version, no longer supported: 1.2 1995-03-28 FSSTND[27]
Old version, no longer supported: 2.0 1997-10-26 FHS 2.0 is the direct successor for FSSTND 1.2. Name of the standard was changed to Filesystem Hierarchy Standard.[28][29][30]
Old version, no longer supported: 2.1 2000-04-12 FHS[31][32][33]
Old version, no longer supported: 2.2 2001-05-23 FHS[34]
Older version, yet still supported: 2.3 2004-01-29 FHS[35]
Current stable version: 3.0 2015-05-18 FHS[36]
Old version
Older version, still supported
Latest version
Latest preview version
Future release

See also


  1. ^ "Filesystem Hierarchy Standard Specifications Archive". Retrieved 3 June 2015. 
  2. ^ J. DeFelicc (1972-03-17). "E.0". Preliminary Release of UNIX Implementation Document (PDF) (D). p. 8. IMO.1-1. 
  3. ^ "/etc : Host-specific system configuration". Filesystem Hierarchy Standard. Retrieved 18 October 2012. 
  4. ^ Define - /etc?, Posted by Cliff, 3 March 2007 - Slashdot
  5. ^ "/opt : Add-on application software packages". Filesystem Hierarchy Standard. Retrieved 18 October 2012. 
  6. ^ Should be shareable and read-only, cf.
  7. ^ Historically and strictly according to the standard, /usr/local/ is for data that must be stored on the local host (as opposed to /usr/, which may be mounted across a network). Most of the time /usr/local/ is used for installing software/data that are not part of the standard operating system distribution (in such case, /usr/ would only contain software/data that are part of the standard operating system distribution). It is possible that the FHS standard may in the future be changed to reflect this de facto convention).
  8. ^ "Filesystem Hierarchy Standard". FHS 2.3. Section /var/run : Run-time variable data. 
  9. ^ "5.13. /var/run : Run-time variable data". FHS 3.0. 
  10. ^ "File System Standard" (PDF). Linux Foundation. p. 5.11.1. 
  11. ^ Red Hat reference guide on file system structure
  12. ^ SuSE Linux Enterprise Server Administration, Novell authorized courseware, by Jason W. Eckert, Novell; Course Technology, 2006; ISBN 1-4188-3731-8, ISBN 978-1-4188-3731-0
  13. ^ Debian policy on FHS compliance
  14. ^ Ubuntu Linux File system Tree Overview - Community Ubuntu Documentation
  15. ^ Hisham Muhammad (9 May 2003). "The Unix tree rethought: an introduction to GoboLinux". Retrieved 2008-03-17. 
  16. ^ Dolstra, E. and Löh, A. "NixOS: A Purely Functional Linux Distribution." In ICFP 2008: 13th ACM SIGPLAN International Conference on Functional Programming, pages 367–378, Victoria, British Columbia, Canada. September 2008.
  17. ^ Allan McRae. "Arch Linux - News: The /lib directory becomes a symlink". Archived from the original on 9 September 2014. Retrieved 28 December 2014. 
  18. ^ Allan McRae. "Arch Linux - News: Binaries move to /usr/bin requiring update intervention". Archived from the original on 10 September 2014. Retrieved 28 December 2014. 
  19. ^
  20. ^
  21. ^  – FreeBSD Miscellaneous Information Manual
  22. ^ SunOS 4.1.3 manual page for filesystem(7), dated 10 January 1988 (from the FreeBSD Man Pages library)
  23. ^  – Solaris 10 Standards, Environments and Macros Reference Manual
  24. ^ "filesystem man page - Solaris 10 11/06 Man Pages". Retrieved 2011-10-15. 
  25. ^ "Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.0/". Retrieved 2012-10-16. 
  26. ^ "Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.1/". Retrieved 2012-10-16. 
  27. ^ "Index of /pub/Linux/docs/fsstnd/old/". Retrieved 2012-10-16. 
  28. ^ "FHS 2.0 Announcement". Retrieved 2012-10-16. 
  29. ^ Quinlan, Daniel (14 March 2012) [1997], "FHS 2.0 Announcement", BSD, Linux and Unix Information - Research by Kenneth R. Saborio (San Jose, Costa Rica: Kenneth R. Saborio), retrieved 18 October 2012 
  30. ^ "Index of /pub/Linux/docs/fsstnd/". Retrieved 2012-10-16. 
  31. ^ "FHS 2.1 Announcement". Retrieved 2012-10-16. 
  32. ^ "FHS 2.1 is released". 2000-04-13. Retrieved 2012-10-16. 
  33. ^ Quinlan, Daniel (12 April 2000). "Filesystem Hierarchy Standard — Version 2.1, Filesystem Hierarchy Standard Group" (PDF). Acadia Linux Tutorials. Wolfville, Nova Scotia, Canada: Jodrey School of Computer Science,  
  34. ^  
  35. ^  
  36. ^ Yeoh, Christopher; Russell, Rusty; Quinlan, Daniel, eds. (19 March 2015). "Filesystem Hierarchy Standard" (PDF).  

External links

  • Official Home of the Filesystem Hierarchy Standard (FHS) at The Linux Foundation
    • New homepage for specs
  • objectroot – a proposal for a new filesystem hierarchy, based on object-oriented design principles
  • The Dotted Standard Filename Hierarchy, yet another very different hierarchy (used in cLIeNUX) (mirror)
  • Linux Filesystem Hierarchy Version 0.65
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.