View Source: FileSystemHierarchy - Waikato Linux Users Group

Edit PageHistory Diff Info LikePages
In [Unix]/[Linux], there is nothing like the registry or some other kind of magic database. It's all just files. Understanding the FileSystem and learning what goes where, roughly, is an important step in finding your way around your system.

The following is a list of the conventional locations for the most common things.

__<tt>/</tt>__:
    The FileSystem root where all of the directory tree "grows out of."

__<tt>/boot</tt>__:
    The [Kernel] goes here. This is often a separate [Partition] at the beginning of the HardDisk.

__<tt>/bin</tt>__:
    System executable files for use by all users.

__<tt>/dev</tt>__:
    Device nodes, ie files that represent your computer's periphery.

__<tt>/etc</tt>__:
    Configuration files.

__<tt>/home</tt>__:
    Every user owns a subdirectory named for his username here. Your own subdirectory is where you store all your personal stuff that has nothing to do with the system. It is aptly called your home. Your mail, your pictures and letters, your music, the videos and your notes, this is where you put them. When you configure a program, it saves the settings here, in so-called DotFile~s.

    Instead of <tt>/home/''yourusername''</tt> you commonly simply say <tt>~~</tt>.

__<tt>/lib</tt>__:
    Libraries needed to run the programs in <tt>/bin</tt> and <tt>/sbin</tt>.

__<tt>/mnt</tt>__:
    MountPoint for temporary FileSystem~s (eg [CDROM], FloppyDisk).

__<tt>/media</tt>__:
    MountPoint for temporary FileSystem~s that FedoraCore uses in latest versions (eg [CDROM], [DVD]).

__<tt>/opt</tt>__:
    Intended for additional, self-contained software packages in subdirectories, such as TarBall~s which contain binaries rather than source. [KDE] is often found in <tt>/opt/kde</tt>, even though it doesn't fit the "self-contained" criterion. Some people install source TarBall~s in here too, especially beta software.

__<tt>/proc</tt>__:
    A virtual FileSystem containing pseudofiles with information about running processes. On [Linux], there are also many files pertaining to the hardware and [Kernel] configuration.

__<tt>/root</tt>__:
    Home directory of <tt>root</tt>, the SuperUser.

__<tt>/sbin</tt>__:
    Executable files only of interest to <tt>root</tt>, the SuperUser.

__<tt>/usr</tt>__:
    The place for files shared by all users of the machine. The party is here.

    You will find duplicates for a number of directories at the root level, such as <tt>/usr/bin</tt>, <tt>/usr/lib</tt>, <tt>/usr/sbin</tt> etc which are analogous to <tt>/bin</tt>, <tt>lib</tt>, <tt>/sbin</tt> etc. The distinction is somewhat arbitrary; it comes from the fact that <tt>/usr</tt> is commonly on a [Partition] by itself, which means the programs and other miscellanea found under it are not available during the early boot process.

    There's also a <tt>/usr/share</tt> which has no counterpart at the root level. It is where program resources are installed; things like icons, helpfiles, sound clips and such end up here.

    Most things you install sprinkle their files over these directories.

__<tt>/usr/local</tt>__:
    Anything shared across the system but not supplied by the system vendor traditionally goes here -- most commonly, [Package]s compiled from TarBall~s.

__<tt>/var</tt>__:
    Variable data files, such as logs, mailboxen, printer spools, cached data, databases and the like. Things that will change, but which need to be remembered across invocations of a program. Scratch space, if you will.

__<tt>/tmp</tt>__:
    The place for temporary files -- that is, ''literally'' temporary files. On some systems this directory is frequently purged, and on machines with modern [Linux] kernels it may be mounted as [Tmpfs] FileSystem that exists only in memory. When VirtualMemory subsystems were not as good as they are today, many userland programs had to explicitly balance memory and disk consumption in <tt>/tmp</tt>, and some still do.

The other part that's important to remember are EnvironmentVariable~s, many of which are dedicated to telling applications where they should look for certain kinds of files. The most notable example would be <tt>PATH</tt>, which specifies which directories programs can be found in.

Note that all of these choices are arbitrary. You could put anything anywhere at all, as long as you have write permissions, and still make things work, though only someone who enjoys headaches would do that. The important lesson in the arbitrariness is that, again, there is nothing magical about any of this. They are social conventions, not mechanical necessities. A [Unix] system is ultimately just a bunch of files and a handful of processes.

See also:
* hier(7)
* [Filesystem hierarchy standard | http://www.pathname.com/fhs/]

----
CategoryBeginners
6 pages link to FileSystemHierarchy:
Last edited on Thursday, October 6, 2005 10:09:01 pm by AristotlePagaltzis
Edit PageHistory Diff Info LikePages