CLASS="FILENAME"
>/usr/local</TT
> hierarchy is for use by the
system administrator when installing software locally. It needs to be
safe from being overwritten when the system software is updated. It
may be used for programs and data that are shareable amongst a group
of hosts, but not found in <TT
CLASS="FILENAME"
>/usr</TT
>.</P
><P
>Locally installed software must be placed within
<TT
CLASS="FILENAME"
>/usr/local</TT
> rather than <TT
CLASS="FILENAME"
>/usr</TT
>
unless it is being installed to replace or upgrade software in
<TT
CLASS="FILENAME"
>/usr</TT
>.
<A
NAME="AEN1450"
HREF="#FTN.AEN1450"
><SPAN
CLASS="footnote"
>[27]</SPAN
></A
></P
></DIV
><DIV
CLASS="SECTION"
><HR><H4
CLASS="SECTION"
><A
NAME="REQUIREMENTS10"
>Requirements</A
></H4
><P
>The following directories, or symbolic links to directories,
must be in <TT
CLASS="FILENAME"
>/usr/local</TT
></P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN1460"
></A
><TABLE
BORDER="0"
FRAME="void"
CLASS="CALSTABLE"
><COL><COL><THEAD
><TR
><TH
>Directory</TH
><TH
>Description</TH
></TR
></THEAD
><TBODY
><TR
><TD
><TT
CLASS="FILENAME"
>bin</TT
></TD
><TD
>Local binaries</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>etc</TT
></TD
><TD
>Host-specific system configuration for local binaries</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>games</TT
></TD
><TD
>Local game binaries</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>include</TT
></TD
><TD
>Local C header files</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>lib</TT
></TD
><TD
>Local libraries</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>man</TT
></TD
><TD
>Local online manuals</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>sbin</TT
></TD
><TD
>Local system binaries</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>share</TT
></TD
><TD
>Local architecture-independent hierarchy</TD
></TR
><TR
><TD
><TT
CLASS="FILENAME"
>src</TT
></TD
><TD
>Local source code</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>No other directories, except those listed below, may be in
<TT
CLASS="FILENAME"
>/usr/local</TT
> after first installing a FHS-compliant
system.</P
></DIV
><DIV
CLASS="SECTION"
><HR><H4
CLASS="SECTION"
><A
NAME="SPECIFICOPTIONS14"
>Specific Options</A
></H4
><P
>If directories <TT
CLASS="FILENAME"
>/lib<qual></TT
> or
<TT
CLASS="FILENAME"
>/usr/lib<qual></TT
> exist, the equivalent
directories must also exist in <TT
CLASS="FILENAME"
>/usr/local</TT
>.</P
><P
><TT
CLASS="FILENAME"
>/usr/local/etc</TT
> may be a symbolic link to
<TT
CLASS="FILENAME"
>/etc/local</TT
>.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Rationale</B
></TH
></TR
><TR
><TD
> </TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The consistency of <TT
CLASS="FILENAME"
>/usr/local/etc</TT
> is
beneficial to installers, and is already used in other systems. As
all of <TT
CLASS="FILENAME"
>/usr/local</TT
> needs to be backed up to
reproduce a system, it introduces no additional maintenance overhead,
but a symlink to <TT
CLASS="FILENAME"
>/etc/local</TT
> is suitable if
systems want alltheir configuration under one hierarchy.</P
><P
>Note that <TT
CLASS="FILENAME"
>/usr/etc</TT
> is still not allowed: programs
in <TT
CLASS="FILENAME"
>/usr</TT
> should place configuration files in
<TT
CLASS="FILENAME"
>/etc</TT
>.</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="USRLOCALSHARE1"
>/usr/local/share</A
></H2
><P
>The requirements for the contents of this directory are the same
as <TT
CLASS="FILENAME"
>/usr/share</TT
>. The only additional constraint is
that <TT
CLASS="FILENAME"
>/usr/local/share/man</TT
> and
<TT
CLASS="FILENAME"
>/usr/local/man</TT
> directories must be synonomous
(usually this means that one of them must be a symbolic link).
<A
NAME="AEN1530"
HREF="#FTN.AEN1530"
><SPAN
CLASS="footnote"
>[28]</SPAN
></A
></P
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="USRSBINNONESSENTIALSTANDARDSYSTEMBI"
>/usr/sbin : Non-essential standard system binaries</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE25"
>Purpose</A
></H3
><P
>This directory contains any non-essential binaries used
exclusively by the system administrator. System administration
programs that are required for system repair, system recovery,
mounting <TT
CLASS="FILENAME"
>/usr</TT
>, or other essential functions must
be placed in <TT
CLASS="FILENAME"
>/sbin</TT
> instead.
<A
NAME="AEN1540"
HREF="#FTN.AEN1540"
><SPAN
CLASS="footnote"
>[29]</SPAN
></A
></P
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="USRSHAREARCHITECTUREINDEPENDENTDATA"
>/usr/share : Architecture-independent data</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE26"
>Purpose</A
></H3
><P
>The <TT
CLASS="FILENAME"
>/usr/share</TT
> hierarchy is for all
read-only architecture independent data files.
<A
NAME="AEN1550"
HREF="#FTN.AEN1550"
><SPAN
CLASS="footnote"
>[30]</SPAN
></A
> </P
><P
>This hierarchy is intended to be shareable among all
architecture platforms of a given OS; thus, for example, a site with
i386, Alpha, and PPC platforms might maintain a single
<TT
CLASS="FILENAME"
>/usr/share</TT
> directory that is centrally-mounted.
Note, however, that <TT
CLASS="FILENAME"
>/usr/share</TT
> is generally not
intended to be shared by different OSes or by different releases of
the same OS.</P
><P
>Any program or package which contains or requires data that
doesn't need to be modified should store that data in
<TT
CLASS="FILENAME"
>/usr/share</TT
> (or
<TT
CLASS="FILENAME"
>/usr/local/share</TT
>, if installed locally). It is
recommended that a subdirectory be used in
<TT
CLASS="FILENAME"
>/usr/share</TT
> for this purpose.</P
><P
>Game data stored in <TT
CLASS="FILENAME"
>/usr/share/games</TT
> must
be purely static data. Any modifiable files, such as score files,
game play logs, and so forth, should be placed in
<TT
CLASS="FILENAME"
>/var/games</TT
>.</P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="REQUIREMENTS11"
>Requirements</A