Unix filesystem

This is an old revision of this page, as edited by Delt01 (talk | contribs) at 00:10, 11 June 2012 (added info + capitalized beginning of sentences + misc. minor edits). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In Unix and Unix-like operating systems, the Unix directory structure is a convention for filesystem layout.

Several attempts exist to standardize the Unix filesystem layout, such as the "Filesystem Hierarchy Standard,"[1] however, it is targeted primarily at Linux. Also, as part of the "Linux Standards Base", a common filesystem layout is defined, to encourage interoperability among different Linux distributions.[2]

What follows is a generalized overview of common locations of files in a Unix operating system:

Directory or file Description
/ The slash / character alone denotes the root of the filesystem tree.
/bin
Stands for "binaries" and contains certain fundamental utilities, such as ls or cp, which are generally needed by all users.
/sbin
Stands for "system (or superuser) binaries" and contains fundamental utilities, such as init, usually needed to start, maintain and recover the system.
/etc
Contains system-wide configuration files and system databases.
/dev
Stands for "devices". Contains file representations of peripheral devices.
/dev/null
Also known as the "bit bucket" or "black hole", this pseudo-device discards all contents written to it, and is typically used to pipe away unwanted data.
/dev/random
This pseudo-device returns pseudorandom numbers (subject to the limitations of random number generators in computing) when read from. It uses system noise to generate random numbers and blocks if not enough entropy in the noise is available. Random is commonly used by programs such as SSH that absolutely need cryptographically strong random data to generate an encryption key.
/dev/urandom
Similar to /dev/random, except it always returns (cryptographically less strong) pseudorandom numbers, even if there is not enough entropy in the system noise available.
/dev/zero
An endless supply of null's (0x00). Useful for "zeroing" a disk drive (i.e. dd if=/dev/zero of=/dev/... bs=64k)
/home
Contains the home directories for the users.
/mnt
Stands for "mount". Contains filesystem mount points.
/lib
Contains system libraries.
/root
The home directory for the superuser root. This account's home directory is usually on the initial filesystem (and hence not in /home) in case specific maintenance needs to be performed, during which other filesystems are not available. Such a case could occur, for example, if a hard disk drive suffers physical failures and cannot be properly mounted.
/tmp
A place for temporary files. Many Unices clear this directory upon start up.
/usr
Originally the directory holding user home directories, its use has changed. It now holds executables, libraries, and shared resources that are not system critical, like the X Window System, KDE, Perl, etc. (The name "Unix System Resources" is a post hoc backronym[citation needed].) However, on some Unix systems, some user accounts may still have a home directory that is a direct subdirectory of /usr, such as the default as in Minix. (these user accounts are often related to server or system use, and not directly used by a person)
/usr/bin
This directory stores all binary programs distributed with the operating system not residing in /bin, /sbin or (rarely) /etc.
/usr/include
Stores the development headers used throughout the system. Header files are mostly used by the #include directive in C programming language, which is how the name of this directory was chosen.
/usr/lib
Stores the required libraries and data files for programs stored within /usr or elsewhere.
/usr/local
Resembles /usr, except that its subdirectories are used for additions not part of the operating system distribution, such as custom programs or files from a BSD Ports collection. Usually has subdirectories such as /usr/local/lib or /usr/local/bin.
/var
A short for "variable." A place for files that may change often, for example e-mail sent to users on the system, or process-ID lock files.
/var/log
Contains system log files.
/var/mail
The place where all the incoming mails are stored. Users (other than root) can access their own mail only.
/var/spool
Spool directory. Contains print jobs, mail spools and other queued tasks.
/var/tmp
A place for temporary files which should be preserved between system reboots.
/proc
Contains all processing data (process information about a running operating system). Usually, the entire contents of this directory is created on-the-fly by the operating system's kernel when it is read by a process; it does not actually exist on disk. The contents reflects the current and immediate state of the system and all processes running on it. There is normally a special filesystem of type "proc" mounted here (or "none" on some systems) as shown by the "mount" command.
/opt
Contains add-on software. Some large program suites may prefer to be installed here, rather than under /usr.
/media
Default mount point for removable devices, such as USB sticks, media players, etc.
/srv
Server data (data for services provided by system).
/boot
Contains all the important files which are required for successful booting process.
/sys
Contains information related to hardware. See /proc above.

References

  1. ^ "Filesystem Hierarchy Standard". Retrieved 2007-07-25.
  2. ^ "Linux Standards Base". Retrieved 2007-07-25.