How many of you do really understand what is file is all about?. Or why we even need a file system. Well, thats another topic which is out of scope for the current blog. But I must recommed you to visit the website `http://www.pathname.com/fhs/` to get the clean understanding on the file system hierarchy and the standard implementations along with the deviations.
This blog is a loose attemt to through light on the FHS and the Linux directory tree structure standards.
/usr filesystem contains all commands, libraries, manual pages, and other unchanging files/usr should be specific for any given machine, nor/usr). It can make administration easier (only the master /usr needs to be changed when updating an application, not each machine separately) to have /usr network mounted. Even if the filesystem is on a local disk, it could be mounted read−only, to lessen the chance of filesystem corruption during a crash.
This blog is a loose attemt to through light on the FHS and the Linux directory tree structure standards.
Such a standard has the advantage that it will be easier to write or port software for Linux, and to administer Linux machines, since everything should be in standardized places.
The
needed during normal operation.
/usr filesystem contains all commands, libraries, manual pages, and other unchanging files No files in should they be modified during normal use. This allows the files to be shared over the network, which can be cost−effective since it saves disk space (there can easily be hundreds of megabytes, increasingly multiple gigabytes in The
The /home filesystem contains the users' home directories, i.e., all the real data on the system.
Separating home directories to their own directory tree or filesystem makes backups easier; the other
parts often do not have to be backed up, or at least not as often as they seldom change. A big /home
might have to be broken across several filesystems, which requires adding an extra naming level
below /home, for example /home/students and /home/staff.
/var filesystem contains files that change, such as spool directories (for mail, news, printers,etc), log files, formatted manual pages, and temporary files. Traditionally everything in been somewhere below /usr , but that made it impossible to mount /usr read−only.Separating home directories to their own directory tree or filesystem makes backups easier; the other
parts often do not have to be backed up, or at least not as often as they seldom change. A big /home
might have to be broken across several filesystems, which requires adding an extra naming level
below /home, for example /home/students and /home/staff.
The root filesystem is specific for each machine (it is generally stored on a local disk, although it
could be a ramdisk or network drive as well) and contains the files that are necessary for booting the
system up, and to bring it up to such a state that the other filesystems may be mounted. The contents
of the root filesystem will therefore be sufficient for the single user state. It will also contain tools for
fixing a broken system, and for recovering lost files from backups.
No comments:
Post a Comment