Chapter 2. File System Structure and Maintenance
The file system structure is the most basic level of organization in an operating system. The way an operating system interacts with its users, applications, and security model nearly always depends on how the operating system organizes files on storage devices. Providing a common file system structure ensures users and programs can access and write files.
File systems break files down into two logical categories:
- Shareable versus unshareable files
- Variable versus static files
Shareable files can be accessed locally and by remote hosts; unshareable files are only available locally. Variable files, such as log files, can be changed at any time; static files, such as binaries, do not change without an action from the system administrator.
Categorizing files in this manner helps correlate the function of each file with the permissions assigned to the directories which hold them. How the operating system and its users interact with a file determines the directory in which it is placed, whether that directory is mounted with read-only or read/write permissions, and the level of access each user has to that file. The top level of this organization is crucial; access to the underlying directories can be restricted, otherwise security problems could arise if, from the top level down, access rules do not adhere to a rigid structure.
2.1. Overview of Filesystem Hierarchy Standard (FHS)
Red Hat Enterprise Linux uses the Filesystem Hierarchy Standard (FHS) file system structure, which defines the names, locations, and permissions for many file types and directories.
The FHS document is the authoritative reference to any FHS-compliant file system, but the standard leaves many areas undefined or extensible. This section is an overview of the standard and a description of the parts of the file system not covered by the standard.
The two most important elements of FHS compliance are:
- Compatibility with other FHS-compliant systems
- The ability to mount a
/usr/partition as read-only. This is especially crucial, since
/usr/contains common executables and should not be changed by users. In addition, since
/usr/is mounted as read-only, it should be mountable from the CD-ROM drive or from another machine via a read-only NFS mount.
2.1.1. FHS Organization
The directories and files noted here are a small subset of those specified by the FHS document. Refer to the latest FHS documentation for the most complete information at http://www.pathname.com/fhs/.
126.96.36.199. Gathering File System Information
df command reports the system's disk space usage. Its output looks similar to the following:
df command output
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 11675568 6272120 4810348 57% / /dev/sda1 100691 9281 86211 10% /boot none 322856 0 322856 0% /dev/shm
df shows the partition size in 1 kilobyte blocks and the amount of used and available disk space in kilobytes. To view the information in megabytes and gigabytes, use the command
df -h. The
-h argument stands for "human-readable" format. The output for
df -h looks similar to the following:
df -h command output
Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 12G 6.0G 4.6G 57% / /dev/sda1 99M 9.1M 85M 10% /boot none 316M 0 316M 0% /dev/shm
In the above examples, the mounted partition
/dev/shm represents the system's virtual memory file system.
du command displays the estimated amount of space being used by files in a directory, displaying the disk usage of each subdirectory. The last line in the output of
du shows the total disk usage of the directory; to see only the total disk usage of a directory in human-readable format, use
du -hs. For more options, refer to
To view the system's partitions and disk space usage in a graphical format, use the Gnome System Monitor by clicking on Applications → System Tools → System Monitor or using the command
gnome-system-monitor. Select the File Systems tab to view the system's partitions. The figure below illustrates the File Systems tab.
Figure 2.1. GNOME System Monitor File Systems tab
/boot/ directory contains static files required to boot the system, for example, the Linux kernel. These files are essential for the system to boot properly.
Do not remove the
/boot/ directory. Doing so renders the system unbootable.
/dev/ directory contains device nodes that represent the following device types:
- devices attached to the system;
- virtual devices provided by the kernel.
These device nodes are essential for the system to function properly. The
udevd daemon creates and removes device nodes in
/dev/ as needed.
Devices in the
/dev/ directory and subdirectories are defined as either character (providing only a serial stream of input and output, for example, mouse or keyboard) or block (accessible randomly, for example, a hard drive or a floppy drive). If GNOME or KDE is installed, some storage devices are automatically detected when connected (such as with a USB) or inserted (such as a CD or DVD drive), and a pop-up window displaying the contents appears.
Table 2.1. Examples of common files in the
|The master device on the primary IDE channel.
|The slave device on the primary IDE channel.
|The first virtual console.
|The second virtual console.
|The first device on the primary SCSI or SATA channel.
|The first parallel port.
/etc/ directory is reserved for configuration files that are local to the machine. It should contain no binaries; any binaries should be moved to
For example, the
/etc/skel/ directory stores "skeleton" user files, which are used to populate a home directory when a user is first created. Applications also store their configuration files in this directory and may reference them when executed. The
/etc/exports file controls which file systems export to remote hosts.
/lib/ directory should only contain libraries needed to execute the binaries in
/sbin/. These shared library images are used to boot the system or execute commands within the root file system.
/media/ directory contains subdirectories used as mount points for removable media, such as USB storage media, DVDs, and CD-ROMs.
/mnt/ directory is reserved for temporarily mounted file systems, such as NFS file system mounts. For all removable storage media, use the
/media/ directory. Automatically detected removable media will be mounted in the
/mnt directory must not be used by installation programs.
/opt/ directory is normally reserved for software and add-on packages that are not part of the default installation. A package that installs to
/opt/ creates a directory bearing its name, for example
/opt/packagename/. In most cases, such packages follow a predictable subdirectory structure; most store their binaries in
/opt/packagename/bin/ and their
man pages in
/proc/ directory contains special files that either extract information from the kernel or send information to it. Examples of such information include system memory, CPU information, and hardware configuration. For more information about
/proc/, refer to Section 2.3, “The /proc Virtual File System”.
/sbin/ directory stores binaries essential for booting, restoring, recovering, or repairing the system. The binaries in
/sbin/ require root privileges to use. In addition,
/sbin/ contains binaries used by the system before the
/usr/ directory is mounted; any system utilities used after
/usr/ is mounted are typically placed in
At a minimum, the following programs should be stored in
/srv/ directory contains site-specific data served by a Red Hat Enterprise Linux system. This directory gives users the location of data files for a particular service, such as FTP, WWW, or CVS. Data that only pertains to a specific user should go in the
The default httpd install uses
/var/www/html for served content.
/sys/ directory utilizes the new
sysfs virtual file system specific to the 2.6 kernel. With the increased support for hot plug hardware devices in the 2.6 kernel, the
/sys/ directory contains information similar to that held by
/proc/, but displays a hierarchical view of device information specific to hot plug devices.
/usr/ directory is for files that can be shared across multiple machines. The
/usr/ directory is often on its own partition and is mounted read-only. The
/usr/ directory usually contains the following subdirectories:
- This directory is used for binaries.
- This directory is used for system-wide configuration files.
- This directory stores games.
- This directory is used for C header files.
- This directory is used for Kerberos-related binaries and files.
- This directory is used for object files and libraries that are not designed to be directly utilized by shell scripts or users. This directory is for 32-bit systems.
- This directory is used for object files and libraries that are not designed to be directly utilized by shell scripts or users. This directory is for 64-bit systems.
- This directory contains small helper programs called by other programs.
- This directory stores system administration binaries that do not belong to
- This directory stores files that are not architecture-specific.
- This directory stores source code.
- This directory stores temporary files.
/usr/ directory should also contain a
/local/ subdirectory. As per the FHS, this subdirectory is used by the system administrator when installing software locally, and should be safe from being overwritten during system updates. The
/usr/local directory has a structure similar to
/usr/, and contains the following subdirectories:
Red Hat Enterprise Linux's usage of
/usr/local/ differs slightly from the FHS. The FHS states that
/usr/local/ should be used to store software that should remain safe from system software upgrades. Since the RPM Package Manager can perform software upgrades safely, it is not necessary to protect files by storing them in
Instead, Red Hat Enterprise Linux uses
/usr/local/ for software local to the machine. For instance, if the
/usr/ directory is mounted as a read-only NFS share from a remote host, it is still possible to install a package or program under the
Since the FHS requires Linux to mount
/usr/ as read-only, any programs that write log files or need
lock/ directories should write them to the
/var/ directory. The FHS states
/var/ is for variable data, which includes spool directories and files, logging data, transient and temporary files.
Below are some of the directories found within the
/var/ directory depending on what is installed on the system:
System log files, such as
lastlog, go in the
/var/log/ directory. The
/var/lib/rpm/ directory contains RPM system databases. Lock files go in the
/var/lock/ directory, usually in directories for the program using the file. The
/var/spool/ directory has subdirectories that store data files for some programs. These subdirectories may include: