|
|||
|
|
|
| Home |
| About |
| Hobbies |
| Software |
| Hardware |
| ICT Hotlist |
| Purpose |
React:
ICT-Hotlist Topic
Back to the ICT-Hotlist...fhs
Unix and Linux Filesystem Hierarchy Standard for developers,sysadmins and users. Aims for an open standard to make all Linux and Unix systems more interchangeable. Read the document.Purpose
This standard enables:
-
Software to predict the location of installed files and directories, and
-
Users to predict the location of installed files and directories.
It is done by:
-
Specifying guiding principles for each area of the filesystem,
-
Specifying the minimum files and directories required,
-
Enumerating exceptions to the principles, and
-
Enumerating specific cases where there has been historical conflict.
The FHS document is used by:
-
Independent software suppliers to create applications which are FHS compliant, and work with distributions which are FHS compliant,
-
OS creators to provide systems which are FHS compliant, and
-
Users to understand and maintain the FHS compliance of a system.
The FHS document has a limited scope:
-
Local placement of local files is a local issue, so FHS does not attempt to usurp system administrators.
-
FHS addresses issues where file placements need to be coordinated between multiple parties such as local sites, distributions, applications, documentation, etc.
Scripts and programming examples disclaimer
Unless stated otherwise, the script sources and programming examples provided are copyrighted freeware. You may modify them, as long as a reference to the original code and hyperlink to the source page is included in the modified code and documentation. However, it is not allowed to publish (copies of) scripts and programming examples on your own site, blog, vlog, or distribute them on paper or any other medium, without prior written consent.Many of the techniques used in these scripts, including but not limited to modifying the registry or system files and settings, impose a risk of rendering the Operating System inoperable and loss of data. Make sure you have verified full backups and the associated restore software available before running any script or programming example. Use these scripts and programming examples entirely at your own risk. All liability claims against the author in relation to material or non-material losses caused by the use, misuse or non-use of the information provided, or the use of incorrect or incomplete information, are excluded. All content is subject to change and provided without obligation.
