Filesystem Hierarchy Standard

{{Infobox technology standard

| title = Filesystem Hierarchy Standard

| status = Published

| year_started = {{Start date and age|1994|02|14|df=yes}}

| version = 3.0

| version_date = {{Start date and age|2015|06|03|df=yes}}

| organization = Linux Foundation

| related_standards =

| abbreviation = FHS

| domain = Directory structure

| website = {{Official website|https://refspecs.linuxfoundation.org/fhs.shtml}}
{{Official website|http://www.pathname.com/fhs/|Official website (Historical)}}

}}

The Filesystem Hierarchy Standard (FHS) is a reference describing the conventions used for the layout of Unix-like systems. It has been made popular by its use in Linux distributions, but it is used by other Unix-like systems as well.{{Cite web|url=https://wiki.linuxfoundation.org/lsb/fhs|title=FHS|website=The Linux Foundation Wiki|access-date=2022-01-04}} It is maintained by the Linux Foundation. The latest version is 3.0, released on 3 June 2015.{{Cite web |title=lsb:fhs-30 [Wiki] |url=https://wiki.linuxfoundation.org/lsb/fhs-30 |access-date=2023-02-22 |website=wiki.linuxfoundation.org}}

Directory structure

File:Root directory hierarchy on Linux screenshot.webp]]

In the FHS, all files and directories appear under the root directory /, even if they are stored on different physical or virtual devices. Some of these directories only exist in a particular system if certain subsystems, such as the X Window System, are installed.

Most of these directories exist in all Unix-like 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.

class="wikitable" summary="A description of the hierarchy specified in the FHS."

class="wikitable" summary="A description of the hierarchy specified in the FHS."
Directory !Description
`/` \|Primary hierarchy root and root directory of the entire file system hierarchy.
`/bin` \|Essential command binaries that need to be available in single-user mode, including to bring up the system or repair it,{{Cite web\|title=hier(7) - Linux manual page\|url=https://man7.org/linux/man-pages/man7/hier.7.html\|access-date=2021-01-06\|website=man7.org}} for all users (e.g., cat, ls, cp).
`/boot` \|Boot loader files (e.g., kernels, initrd).
`/dev` \|Device files (e.g., `/dev/null`, `/dev/disk0`, `/dev/sda1`, `/dev/tty`, `%2Fdev%2Frandom`).
`/etc` \|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,{{cite book \|author=J. DeFelicc \|title=Preliminary Release of UNIX Implementation Document \|date=1972-03-17 \|id=IMO.1-1 \|section=E.0 \|page=8 \|issue=D \|url=http://www.bitsavers.org/pdf/att/unix/Early_UNIX/PreliminaryUnixImplementationDocument_Jun72.pdf \|access-date=6 June 2024}} 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).{{cite web \|url= http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION \|title=/etc : Host-specific system configuration \|work=Filesystem Hierarchy Standard 2.3\|access-date=18 February 2016}} 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".[http://ask.slashdot.org/article.pl?sid=07/03/03/028258 Define - /etc?], Posted by Cliff, 3 March 2007 - Slashdot.
`/etc/opt` \|Configuration files for add-on packages stored in `/opt`.
`/etc/sgml` \|Configuration files, such as catalogs, for software that processes SGML.
`/etc/X11` \|Configuration files for the X Window System, version 11.
`/etc/xml` \|Configuration files, such as catalogs, for software that processes XML.
`/home` \|Users' home directories, containing saved files, personal settings, etc.
`/lib` \|Libraries essential for the binaries in `/bin` and `/sbin`.
`/lib<qual>` \|Alternate format essential libraries. These are typically used on systems that support more than one executable code format, such as systems supporting 32-bit and 64-bit versions of an instruction set. Such directories are optional, but if they exist, they have some requirements.
`/media` \|Mount points for removable media such as CD-ROMs (appeared in FHS-2.3 in 2004).
`/mnt` \|Temporarily mounted filesystems.
`/opt` \|Add-on application software packages.{{cite web \|url=http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES \|title=/opt : Add-on application software packages \|work=Filesystem Hierarchy Standard 2.3 \|access-date=18 February 2016}}
`/proc` \|Virtual filesystem providing process and kernel information as files. In Linux, corresponds to a procfs mount. Generally, automatically generated and populated by the system, on the fly.
`/root` \|Home directory for the root user.
`/run` \|Run-time variable data: Information about the running system since last boot, e.g., currently logged-in users and running daemons. Files under this directory must be either removed or truncated at the beginning of the boot process, but this is not necessary on systems that provide this directory as a temporary filesystem (tmpfs) (appeared in FHS-3.0 in 2015).
`/sbin` \|Essential system binaries (e.g., fsck, init, route).
`/srv` \|Site-specific data served by this system, such as data and scripts for web servers, data offered by FTP servers, and repositories for version control systems (appeared in FHS-2.3 in 2004).
`/sys` \|Contains information about devices, drivers, and some kernel features.{{cite web \|url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch06.html#sysKernelAndSystemInformation \|title=/sys : Kernel and system information virtual filesystem \|work=Filesystem Hierarchy Standard 3.0 \|access-date=4 June 2017}}
`/tmp` \|Directory for temporary files (see also `/var/tmp`). Often not preserved between system reboots and may be severely size-restricted.
`/usr` \|Secondary hierarchy for read-only user data; contains the majority of (multi-)user utilities and applications. Should be shareable and read-only.{{cite web\|url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#THEUSRHIERARCHY\|work=Filesystem Hierarchy Standard 2.3\|title=Chapter 4. The /usr Hierarchy}}{{cite web\|url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#purpose18\|work=Filesystem Hierarchy Standard 3.0\|title=Chapter 4. The /usr Hierarchy, Section 4.1 Purpose}}
`/usr/bin` \|Non-essential command binaries (not needed in single-user mode); for all users.
`/usr/include` \|Standard include files.
`/usr/lib` \|Libraries for the binaries in `/usr/bin` and `/usr/sbin`.
`/usr/libexec` \|Binaries run by other programs that are not intended to be executed directly by users or shell scripts (optional).
`/usr/lib<qual>` \|Alternative-format libraries (e.g., `/usr/lib32` for 32-bit libraries on a 64-bit machine (optional)).
`/usr/local` \|Tertiary hierarchy for local data, specific to this host. Typically has further subdirectories (e.g., `bin`, `lib`, `share`).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.
`/usr/sbin` \|Non-essential system binaries (e.g., daemons for various network services).
`/usr/share` \|Architecture-independent (shared) data.
`/usr/src` \|Source code (e.g., the kernel source code with its header files).
`/usr/X11R6` \|X Window System, Version 11, Release 6 (up to FHS-2.3, optional).
`/var` \|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.
`/var/cache` \|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.
`/var/lib` \|State information. Persistent data modified by programs as they run (e.g., databases, packaging system metadata, etc.).
`/var/lock` \|Lock files. Files keeping track of resources currently in use.
`/var/log` \|Log files. Various logs.
`/var/mail` \|Mailbox files. In some distributions, these files may be located in the deprecated `/var/spool/mail`.
`/var/opt` \|Variable data from add-on packages that are stored in `/opt`.
`/var/run` \|Run-time variable data. This directory contains system information data describing the system since it was booted.{{cite web \|url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA \|title=/var/run : Run-time variable data \|work=Filesystem Hierarchy Standard 2.3}} 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.{{cite web \|url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html \|title=5.13. /var/run : Run-time variable data \|work=Filesystem Hierarchy Standard 3.0}}
`/var/spool` \|Spool for tasks waiting to be processed (e.g., print queues and outgoing mail queue).
`/var/spool/mail` \|Deprecated location for users' mailboxes.{{cite web \|title=File System Standard \|url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.pdf \|publisher=Linux Foundation \|page=5.11.1}}
`/var/tmp` \|Temporary files to be preserved between reboots.

Directory

!Description

/

|Primary hierarchy root and root directory of the entire file system hierarchy.

/bin

|Essential command binaries that need to be available in single-user mode, including to bring up the system or repair it,{{Cite web|title=hier(7) - Linux manual page|url=https://man7.org/linux/man-pages/man7/hier.7.html|access-date=2021-01-06|website=man7.org}} for all users (e.g., cat, ls, cp).

/boot

|Boot loader files (e.g., kernels, initrd).

/dev

|Device files (e.g., /dev/null, /dev/disk0, /dev/sda1, /dev/tty, %2Fdev%2Frandom).

/etc

|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,{{cite book |author=J. DeFelicc |title=Preliminary Release of UNIX Implementation Document |date=1972-03-17 |id=IMO.1-1 |section=E.0 |page=8 |issue=D |url=http://www.bitsavers.org/pdf/att/unix/Early_UNIX/PreliminaryUnixImplementationDocument_Jun72.pdf |access-date=6 June 2024}} 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).{{cite web |url= http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION |title=/etc : Host-specific system configuration |work=Filesystem Hierarchy Standard 2.3|access-date=18 February 2016}} 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".[http://ask.slashdot.org/article.pl?sid=07/03/03/028258 Define - /etc?], Posted by Cliff, 3 March 2007 - Slashdot.

/etc/opt

|Configuration files for add-on packages stored in /opt.

/etc/sgml

|Configuration files, such as catalogs, for software that processes SGML.

/etc/X11

|Configuration files for the X Window System, version 11.

/etc/xml

|Configuration files, such as catalogs, for software that processes XML.

/home

|Users' home directories, containing saved files, personal settings, etc.

/lib

|Libraries essential for the binaries in /bin and /sbin.

/lib<qual>

|Alternate format essential libraries. These are typically used on systems that support more than one executable code format, such as systems supporting 32-bit and 64-bit versions of an instruction set. Such directories are optional, but if they exist, they have some requirements.

/media

|Mount points for removable media such as CD-ROMs (appeared in FHS-2.3 in 2004).

/mnt

|Temporarily mounted filesystems.

/opt

|Add-on application software packages.{{cite web |url=http://www.pathname.com/fhs/pub/fhs-2.3.html#OPTADDONAPPLICATIONSOFTWAREPACKAGES |title=/opt : Add-on application software packages |work=Filesystem Hierarchy Standard 2.3 |access-date=18 February 2016}}

/proc

|Virtual filesystem providing process and kernel information as files. In Linux, corresponds to a procfs mount. Generally, automatically generated and populated by the system, on the fly.

/root

|Home directory for the root user.

/run

|Run-time variable data: Information about the running system since last boot, e.g., currently logged-in users and running daemons. Files under this directory must be either removed or truncated at the beginning of the boot process, but this is not necessary on systems that provide this directory as a temporary filesystem (tmpfs) (appeared in FHS-3.0 in 2015).

/sbin

|Essential system binaries (e.g., fsck, init, route).

/srv

|Site-specific data served by this system, such as data and scripts for web servers, data offered by FTP servers, and repositories for version control systems (appeared in FHS-2.3 in 2004).

/sys

|Contains information about devices, drivers, and some kernel features.{{cite web |url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch06.html#sysKernelAndSystemInformation |title=/sys : Kernel and system information virtual filesystem |work=Filesystem Hierarchy Standard 3.0 |access-date=4 June 2017}}

/tmp

|Directory for temporary files (see also /var/tmp). Often not preserved between system reboots and may be severely size-restricted.

/usr

|Secondary hierarchy for read-only user data; contains the majority of (multi-)user utilities and applications. Should be shareable and read-only.{{cite web|url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#THEUSRHIERARCHY|work=Filesystem Hierarchy Standard 2.3|title=Chapter 4. The /usr Hierarchy}}{{cite web|url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.html#purpose18|work=Filesystem Hierarchy Standard 3.0|title=Chapter 4. The /usr Hierarchy, Section 4.1 Purpose}}

/usr/bin

|Non-essential command binaries (not needed in single-user mode); for all users.

/usr/include

|Standard include files.

/usr/lib

|Libraries for the binaries in /usr/bin and /usr/sbin.

/usr/libexec

|Binaries run by other programs that are not intended to be executed directly by users or shell scripts (optional).

/usr/lib<qual>

|Alternative-format libraries (e.g., /usr/lib32 for 32-bit libraries on a 64-bit machine (optional)).

/usr/local

|Tertiary hierarchy for local data, specific to this host. Typically has further subdirectories (e.g., bin, lib, share).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.

/usr/sbin

|Non-essential system binaries (e.g., daemons for various network services).

/usr/share

|Architecture-independent (shared) data.

/usr/src

|Source code (e.g., the kernel source code with its header files).

/usr/X11R6

|X Window System, Version 11, Release 6 (up to FHS-2.3, optional).

/var

|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.

/var/cache

|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.

/var/lib

|State information. Persistent data modified by programs as they run (e.g., databases, packaging system metadata, etc.).

/var/lock

|Lock files. Files keeping track of resources currently in use.

/var/log

|Log files. Various logs.

/var/mail

|Mailbox files. In some distributions, these files may be located in the deprecated /var/spool/mail.

/var/opt

|Variable data from add-on packages that are stored in /opt.

/var/run

|Run-time variable data. This directory contains system information data describing the system since it was booted.{{cite web |url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA |title=/var/run : Run-time variable data |work=Filesystem Hierarchy Standard 2.3}}

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.{{cite web |url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s13.html |title=5.13. /var/run : Run-time variable data |work=Filesystem Hierarchy Standard 3.0}}

/var/spool

|Spool for tasks waiting to be processed (e.g., print queues and outgoing mail queue).

/var/spool/mail

|Deprecated location for users' mailboxes.{{cite web |title=File System Standard |url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.pdf |publisher=Linux Foundation |page=5.11.1}}

/var/tmp

|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.Red Hat reference guide on [https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Storage_Administration_Guide/index.html#s1-filesystem-fhs file system structure].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}}.Debian policy on [https://www.debian.org/doc/debian-policy/#file-system-hierarchy FHS compliance].Ubuntu [https://help.ubuntu.com/community/LinuxFilesystemTreeOverview Linux File system Tree Overview]{{snd}} Community Ubuntu Documentation. GoboLinux{{cite web | title = The Unix tree rethought: an introduction to GoboLinux | url = http://www.gobolinux.org/?page=k5 | author = Hisham Muhammad | date = 9 May 2003 | access-date = 2016-10-04}} and NixOS{{cite conference |last1=Dolstra |first1=E. |last2=Löh |first2=A. |url=https://nixos.org/~eelco/pubs/nixos-icfp2008-final.pdf |title=NixOS: A Purely Functional Linux Distribution |conference-url=http://www.icfpconference.org/icfp2008/ |conference=ICFP 2008: 13th ACM SIGPLAN International Conference on Functional Programming |pages=367–378 |location=Victoria, British Columbia, Canada |date=September 2008}} provide examples of intentionally non-compliant filesystem implementations.

Some distributions generally follow the standard but deviate from it in some areas. The FHS is a "trailing standard", and so documents common practices at a point in time. Of course, times change, and distribution goals and needs call for experimentation. Some 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,{{cite web |title=5.3 About the /sys Virtual File System |url=http://docs.oracle.com/cd/E37670_01/E41138/html/ol_sysfs.html |website=docs.oracle.com |publisher=Oracle |access-date=8 July 2016 |archive-url=https://web.archive.org/web/20160708193213/https://docs.oracle.com/cd/E37670_01/E41138/html/ol_sysfs.html |archive-date=8 July 2016}} whereas many traditional Unix-like operating systems use /sys as a symbolic link to the kernel source tree.{{cite book |last1=Lehey |first1=Greg |title=The Complete FreeBSD: Documentation from the Source |date=May 2003 |publisher=O'Reilly Media, Incorporated |isbn=9780596005160 |pages=188, 609 |edition=Fourth |url=https://books.google.com/books?id=7Y5kfaRmtKUC}}
Many modern Unix-like systems (such as FreeBSD and OpenBSD) via their ports systems 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 and /usr/lib and have /lib symlinked to /usr/lib.{{cite web |author1=Allan McRae |title=Arch Linux – News: The /lib directory becomes a symlink |url=https://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ |website=archlinux.org |access-date=14 December 2019 |archive-url=https://web.archive.org/web/20140909234433/https://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/ |archive-date=9 September 2014 |url-status=live}}
Some Linux distributions no longer differentiate between /bin and /usr/bin and between /sbin and /usr/sbin. They may symlink /bin to /usr/bin and /sbin to /usr/sbin. Other distributions choose to consolidate all four, symlinking them to /usr/bin.{{cite web |author1=Allan McRae |title=Arch Linux – News: Binaries move to /usr/bin requiring update intervention |url=https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ |website=archlinux.org |access-date=15 December 2019 |archive-url=https://web.archive.org/web/20140910093202/https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/ |archive-date=10 September 2014 |url-status=live}}

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 is not 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 is not intended for such data.{{cite mailing list |url=https://www.mail-archive.com/devel@lists.fedoraproject.org/msg23576.html |title=What's this /run directory doing on my system and where does it come from? |author=Lennart Poettering |date=30 March 2011 |mailing-list=devel@lists.fedoraproject.org}} 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:{{cite web |url=http://wiki.debian.org/ReleaseGoals/RunDirectory |title=ReleaseGoalsRunDirectory |website=Debian Wiki}}

/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

History

= The name of <code>usr</code> =

/usr originally stood for "user".{{Cite web |title=/usr |url=https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/usr.html |access-date=2023-12-10 |website=tldp.org}} This was an artifact of early Unix programming. Specifically, when Ken Thompson and Dennis Ritchie were migrating Unix to a PDP-11, the contents of the /bin and /lib directories, which were to be the first directories mounted on startup and to contain all essentials for the OS to function, became too large to fit on an RK05 disk drive. So they put some of those files on a second RK05, making sure that the first drive contained everything required for loading the second one. The rest of the files were put into the /usr directory.{{cite web |author-link=Doug McIlroy |author=M. D. McIlroy |date=1987 |url=http://www.cs.dartmouth.edu/~doug/reader.pdf |title=A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 |id=CSTR 139 |publisher=Bell Labs}} When they got a third drive, users' files were moved to a new directory named /home.{{cite mailing list |url=http://lists.busybox.net/pipermail/busybox/2010-December/074114.html |title=Understanding the bin, sbin, usr/bin , usr/sbin split |mailing-list=busybox |first=Rob |last=Landley |date=December 9, 2010}}

FHS was created as the FSSTND (short for "Filesystem Standard"{{cite web |url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/FSSTND-FAQ |title=FSSTND FAQ page |access-date=2016-05-10}}), largely based on similar standards for other Unix-like operating systems. Notable examples are these: the {{mono|hier(7)}} description of file system layout,{{man|7|hier|FreeBSD}}. which has existed since the release of Version 7 Unix (in 1979);{{man|7|hier|v7}} the SunOS {{mono|filesystem(7)}}[http://www.freebsd.org/cgi/man.cgi?query=filesystem&manpath=SunOS+4.1.3 SunOS 4.1.3 manual page for filesystem(7)], dated 10 January 1988 (from the FreeBSD Man Pages library). and its successor, the Solaris {{mono|filesystem(7)}}.{{man|7|filesystem|Solaris}}.{{cite web |url=http://manpages.unixforum.co.uk/man-pages/unix/solaris-10-11_06/5/filesystem-man-page.html |archive-url=https://archive.today/20070704090908/http://manpages.unixforum.co.uk/man-pages/unix/solaris-10-11_06/5/filesystem-man-page.html |url-status=dead |archive-date=2007-07-04 |title=filesystem man page – Solaris 10 11/06 Man Pages |access-date=2011-10-15 }}

=Release history=

class="wikitable"
Version ! Release date ! Notes
{{Version\|o\|1.0}} \| 1994-02-14 \| FSSTND{{cite web \|url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/fsstnd-1.0/ \|title=Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.0/ \|publisher=Ibiblio.org \|access-date=2012-10-16}}
{{Version\|o\|1.1}} \| 1994-10-09 \| FSSTND{{cite web \|url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/fsstnd-1.1/ \|title=Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.1/ \|publisher=Ibiblio.org \|access-date=2012-10-16}}
{{Version\|o\|1.2}} \| 1995-03-28 \| FSSTND{{cite web \|url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/ \|title=Index of /pub/Linux/docs/fsstnd/old/ \|publisher=Ibiblio.org \|access-date=2012-10-16}}
{{Version\|o\|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.{{cite web\|url=http://www.pathname.com/fhs/announce-2.0.html \|title=FHS 2.0 Announcement \|publisher=Pathname.com \|access-date=2012-10-16}}{{citation \|url=http://www.informatica.co.cr/linux/research/1997/1117.htm \|title=FHS 2.0 Announcement \|first=Daniel \|last=Quinlan \|work=BSD, Linux, Unix and The Internet – Research by Kenneth R. Saborio \|date=14 March 2012 \|orig-year=1997 \|publisher=Kenneth R. Saborio \|location=San Jose, Costa Rica \|access-date=18 February 2016 \|archive-url=https://web.archive.org/web/20160305100804/http://www.informatica.co.cr/linux/research/1997/1117.htm \|archive-date=5 March 2016 \|url-status=dead }}.{{cite web \|url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/ \|title=Index of /pub/Linux/docs/fsstnd/ \|publisher=Ibiblio.org \|access-date=2012-10-16}}
{{Version\|o\|2.1}} \| 2000-04-12 \| FHS{{cite web \|url=http://www.pathname.com/fhs/announce-2.1.html \|title=FHS 2.1 Announcement \|publisher=Pathname.com \|access-date=2012-10-16}}{{cite web \|url=http://lists.debian.org/lsb-spec/2000/04/msg00005.html \|title=FHS 2.1 is released \|publisher=Lists.debian.org \|date=2000-04-13 \|access-date=2012-10-16}}{{cite web \|url=http://cs.acadiau.ca/~jdiamond/Acadia-Linux-template-tutorial/resources/fhs-2.1.pdf \|title=Filesystem Hierarchy Standard – Version 2.1, Filesystem Hierarchy Standard Group \|first=Daniel \|last=Quinlan \|work=Acadia Linux Tutorials \|publisher=Jodrey School of Computer Science, Acadia University \|location=Wolfville, Nova Scotia, Canada \|date=12 April 2000 \|access-date=18 October 2012 \|archive-url=https://web.archive.org/web/20120327075156/http://cs.acadiau.ca/~jdiamond/Acadia-Linux-template-tutorial/resources/fhs-2.1.pdf \|archive-date=27 March 2012}}
{{Version\|o\|2.2}} \| 2001-05-23 \| FHS{{cite web \|url=http://www.pathname.com/fhs/pub/fhs-2.2.pdf \|title=Filesystem Hierarchy Standard – Version 2.2 final Filesystem Hierarchy Standard Group \|editor1-first=Rusty \|editor1-last=Russell \|editor1-link=Rusty Russell \|editor2-first=Daniel \|editor2-last=Quinlan \|work=Filesystem Hierarchy Standard \|date=23 May 2001 \|access-date=18 February 2016 }}
{{Version\|o\|2.3}} \| 2004-01-29 \| FHS{{cite web \|url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.pdf \|title=Filesystem Hierarchy Standard - Filesystem Hierarchy Standard Group \|editor1-first=Rusty \|editor1-last=Russell \|editor1-link=Rusty Russell \|editor2-first=Daniel \|editor2-last=Quinlan \|editor3-first=Christopher \|editor3-last=Yeoh \|date=28 January 2004 \|access-date=2014-11-29}}
{{Version\|c\|3.0}} \| 2015-05-18 \| FHS{{cite web \|url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf \|title=Filesystem Hierarchy Standard \|editor1-first=Christopher \|editor1-last=Yeoh \|editor2-first=Rusty \|editor2-last=Russell \|editor3-first=Daniel \|editor3-last=Quinlan \|publisher=The Linux Foundation \|date=19 March 2015 \|access-date=2015-05-20}}
colspan="3" \| {{Version \|l \|show=110100}}

class="wikitable"

Version

! Release date

! Notes

| 1994-02-14

| FSSTND{{cite web |url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/fsstnd-1.0/ |title=Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.0/ |publisher=Ibiblio.org |access-date=2012-10-16}}

| 1994-10-09

| FSSTND{{cite web |url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/fsstnd-1.1/ |title=Index of /pub/Linux/docs/fsstnd/old/fsstnd-1.1/ |publisher=Ibiblio.org |access-date=2012-10-16}}

| 1995-03-28

| FSSTND{{cite web |url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/old/ |title=Index of /pub/Linux/docs/fsstnd/old/ |publisher=Ibiblio.org |access-date=2012-10-16}}

| 1997-10-26

| FHS 2.0 is the direct successor for FSSTND 1.2. Name of the standard was changed to Filesystem Hierarchy Standard.{{cite web|url=http://www.pathname.com/fhs/announce-2.0.html |title=FHS 2.0 Announcement |publisher=Pathname.com |access-date=2012-10-16}}{{citation |url=http://www.informatica.co.cr/linux/research/1997/1117.htm |title=FHS 2.0 Announcement |first=Daniel |last=Quinlan |work=BSD, Linux, Unix and The Internet – Research by Kenneth R. Saborio |date=14 March 2012 |orig-year=1997 |publisher=Kenneth R. Saborio |location=San Jose, Costa Rica |access-date=18 February 2016 |archive-url=https://web.archive.org/web/20160305100804/http://www.informatica.co.cr/linux/research/1997/1117.htm |archive-date=5 March 2016 |url-status=dead }}.{{cite web |url=http://www.ibiblio.org/pub/Linux/docs/fsstnd/ |title=Index of /pub/Linux/docs/fsstnd/ |publisher=Ibiblio.org |access-date=2012-10-16}}

| 2000-04-12

| FHS{{cite web |url=http://www.pathname.com/fhs/announce-2.1.html |title=FHS 2.1 Announcement |publisher=Pathname.com |access-date=2012-10-16}}{{cite web |url=http://lists.debian.org/lsb-spec/2000/04/msg00005.html |title=FHS 2.1 is released |publisher=Lists.debian.org |date=2000-04-13 |access-date=2012-10-16}}{{cite web |url=http://cs.acadiau.ca/~jdiamond/Acadia-Linux-template-tutorial/resources/fhs-2.1.pdf |title=Filesystem Hierarchy Standard – Version 2.1, Filesystem Hierarchy Standard Group |first=Daniel |last=Quinlan |work=Acadia Linux Tutorials |publisher=Jodrey School of Computer Science, Acadia University |location=Wolfville, Nova Scotia, Canada |date=12 April 2000 |access-date=18 October 2012 |archive-url=https://web.archive.org/web/20120327075156/http://cs.acadiau.ca/~jdiamond/Acadia-Linux-template-tutorial/resources/fhs-2.1.pdf |archive-date=27 March 2012}}

| 2001-05-23

| FHS{{cite web |url=http://www.pathname.com/fhs/pub/fhs-2.2.pdf |title=Filesystem Hierarchy Standard – Version 2.2 final Filesystem Hierarchy Standard Group |editor1-first=Rusty |editor1-last=Russell |editor1-link=Rusty Russell |editor2-first=Daniel |editor2-last=Quinlan |work=Filesystem Hierarchy Standard |date=23 May 2001 |access-date=18 February 2016 }}

| 2004-01-29

| FHS{{cite web |url=https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.pdf |title=Filesystem Hierarchy Standard - Filesystem Hierarchy Standard Group |editor1-first=Rusty |editor1-last=Russell |editor1-link=Rusty Russell |editor2-first=Daniel |editor2-last=Quinlan |editor3-first=Christopher |editor3-last=Yeoh |date=28 January 2004 |access-date=2014-11-29}}

| 2015-05-18

| FHS{{cite web |url=https://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.pdf |title=Filesystem Hierarchy Standard |editor1-first=Christopher |editor1-last=Yeoh |editor2-first=Rusty |editor2-last=Russell |editor3-first=Daniel |editor3-last=Quinlan |publisher=The Linux Foundation |date=19 March 2015 |access-date=2015-05-20}}

colspan="3" | {{Version |l |show=110100}}

Notes

References

External links

{{Official website|https://wiki.linuxfoundation.org/lsb/fhs|Official Home of the Filesystem Hierarchy Standard (FHS) at The Linux Foundation}}
[https://refspecs.linuxfoundation.org/fhs.shtml Full specification texts]
[http://objectroot.org/ 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) ([https://web.archive.org/web/20050508015157/http://ftp.gwdg.de/pub/cLIeNUX/descriptive/DSFH.html mirror])
{{man|7|hier|Linux}}

Category:Computer standards

Category:Linux

Category:System administration

Category:Unix file system technology