197 lines
4.5 KiB
HTML
197 lines
4.5 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>Red Hat, About the Filesystem Structure</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="Designing Integrated High Quality Linux Applications"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Starting Your Software Automatically on Boot"
|
|
HREF="boot.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="About this Document"
|
|
HREF="about.html"></HEAD
|
|
><BODY
|
|
CLASS="appendix"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
SUMMARY="Header navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Designing Integrated High Quality Linux Applications</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="boot.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="about.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="appendix"
|
|
><H1
|
|
CLASS="appendix"
|
|
><A
|
|
NAME="redhat">A. Red Hat, About the Filesystem Structure</H1
|
|
><P
|
|
>This text was taken from <A
|
|
HREF="http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/ref-guide/ch-filesystem.html"
|
|
TARGET="_top"
|
|
>The Official Red Hat Linux Reference Guide</A
|
|
></P
|
|
><H1
|
|
CLASS="BRIDGEHEAD"
|
|
><A
|
|
NAME="AEN1016">Why Share a Common Structure?</H1
|
|
><P
|
|
>An operating system's filesystem structure is its most basic level of organization. Almost all of the ways an operating system interacts with its users, applications, and security model are dependent upon the way it stores its files on a primary storage device (normally a hard disk drive). It is crucial for a variety of reasons that users, as well as programs at the time of installation and beyond, be able to refer to a common guideline to know where to read and write their <A
|
|
HREF="software.html#software.body"
|
|
>binary</A
|
|
>, <A
|
|
HREF="software.html#software.soul"
|
|
>configuration</A
|
|
>, <A
|
|
HREF="software.html#software.logs"
|
|
>log</A
|
|
>, and other necessary files.</P
|
|
><P
|
|
>A filesystem can be seen in terms of two different logical categories of files:</P
|
|
><P
|
|
></P
|
|
><OL
|
|
TYPE="1"
|
|
><LI
|
|
><P
|
|
>Shareable vs. unsharable files</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>Variable vs. static files</P
|
|
></LI
|
|
></OL
|
|
><P
|
|
>Shareable files are those that can be accessed by various hosts; unsharable files are not available to any other hosts. Variable files can change at any time without system administrator intervention (whether active or passive); static files, such as <A
|
|
HREF="software.html#software.body"
|
|
>documentation and binaries</A
|
|
>, do not change without an action from the system administrator or an agent that the system administrator has placed in motion to accomplish that task.</P
|
|
><P
|
|
>The reason for looking at files in this way has to do with the type of permissions given to the directory that holds them. The way in which the operating system and its users need to utilize the files determines the directory where those files should be placed, whether the directory is mounted read-only or read-write, and the level of access allowed on each file. The top level of this organization (<EM
|
|
>/ directory</EM
|
|
>)is crucial, as the access to the underlying directories can be restricted or <A
|
|
HREF="security.html"
|
|
>security</A
|
|
> problems may manifest themselves if the top level is left disorganized (<A
|
|
HREF="security.html"
|
|
>security=organization</A
|
|
>) or without a <A
|
|
HREF="fhs.html"
|
|
>widely-utilized structure</A
|
|
>.</P
|
|
><P
|
|
>However, simply having a structure does not mean very much unless it is a <A
|
|
HREF="fhs.html"
|
|
>standard</A
|
|
>. Competing structures can actually cause more problems than they fix. Because of this, Red Hat has chosen <A
|
|
HREF="fhs.html"
|
|
>the most widely-used filesystem structure</A
|
|
> and extended it only slightly to accommodate special files used within Red Hat Linux.</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
SUMMARY="Footer navigation table"
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="boot.html"
|
|
ACCESSKEY="P"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
ACCESSKEY="H"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="about.html"
|
|
ACCESSKEY="N"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Starting Your Software Automatically on Boot</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>About this Document</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |