administrator.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1299"
HREF="#AEN1299"
><SPAN
CLASS="footnote"
>[21]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Examples of such configuration files include
<TT
CLASS="FILENAME"
>Xconfig</TT
>, <TT
CLASS="FILENAME"
>XF86Config</TT
>, or
<TT
CLASS="FILENAME"
>system.twmrc</TT
>)</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1389"
HREF="#AEN1389"
><SPAN
CLASS="footnote"
>[22]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
> Miscellaneous
architecture-independent application-specific static files and
subdirectories must be placed in <TT
CLASS="FILENAME"
>/usr/share</TT
>.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1394"
HREF="#AEN1394"
><SPAN
CLASS="footnote"
>[23]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
> For example, the <TT
CLASS="FILENAME"
>perl5</TT
> subdirectory for
Perl 5 modules and libraries.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1402"
HREF="#AEN1402"
><SPAN
CLASS="footnote"
>[24]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Some executable commands such as <B
CLASS="COMMAND"
>makewhatis</B
> and
<B
CLASS="COMMAND"
>sendmail</B
> have also been traditionally placed in
<TT
CLASS="FILENAME"
>/usr/lib</TT
>. <B
CLASS="COMMAND"
>makewhatis</B
> is an
internal binary and must be placed in a binary directory; users access
only <B
CLASS="COMMAND"
>catman</B
>. Newer <B
CLASS="COMMAND"
>sendmail</B
>
binaries are now placed by default in <TT
CLASS="FILENAME"
>/usr/sbin</TT
>.
Additionally, systems using a <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>sendmail</I
></SPAN
>-compatible
mail transfer agent must provide
<B
CLASS="COMMAND"
>/usr/sbin/sendmail</B
> as a symbolic link to the
appropriate executable. </P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1418"
HREF="#AEN1418"
><SPAN
CLASS="footnote"
>[25]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Host-specific data for the X Window System must not be stored in
<TT
CLASS="FILENAME"
>/usr/lib/X11</TT
>. Host-specific configuration files
such as <TT
CLASS="FILENAME"
>Xconfig</TT
> or
<TT
CLASS="FILENAME"
>XF86Config</TT
> must be stored in
<TT
CLASS="FILENAME"
>/etc/X11</TT
>. This includes configuration data such
as <TT
CLASS="FILENAME"
>system.twmrc</TT
> even if it is only made a
symbolic link to a more global configuration file (probably in
<TT
CLASS="FILENAME"
>/usr/X11R6/lib/X11</TT
>).</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1435"
HREF="#AEN1435"
><SPAN
CLASS="footnote"
>[26]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>The case where <TT
CLASS="FILENAME"
>/usr/lib</TT
> and <TT
CLASS="FILENAME"
>/usr/lib<qual></TT
> are the
same (one is a symbolic link to the other) these files and the
per-application subdirectories will exist.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1450"
HREF="#AEN1450"
><SPAN
CLASS="footnote"
>[27]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Software placed in <TT
CLASS="FILENAME"
>/</TT
> or
<TT
CLASS="FILENAME"
>/usr</TT
> may be overwritten by system upgrades
(though we recommend that distributions do not overwrite data in
<TT
CLASS="FILENAME"
>/etc</TT
> under these circumstances). For this
reason, local software must not be placed outside of
<TT
CLASS="FILENAME"
>/usr/local</TT
> without good reason.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1530"
HREF="#AEN1530"
><SPAN
CLASS="footnote"
>[28]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
><TT
CLASS="FILENAME"
>/usr/local/man</TT
> may be deprecated in future FHS
releases, so if all else is equal, making that one a symlink seems
sensible.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1540"
HREF="#AEN1540"
><SPAN
CLASS="footnote"
>[29]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Locally installed system administration programs should be placed in
<TT
CLASS="FILENAME"
>/usr/local/sbin</TT
>.</P
><P
></P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1550"
HREF="#AEN1550"
><SPAN
CLASS="footnote"
>[30]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Much of this data originally lived in <TT
CLASS="FILENAME"
>/usr</TT
>
(<TT
CLASS="FILENAME"
>man</TT
>, <TT
CLASS="FILENAME"
>doc</TT
>) or
<TT
CLASS="FILENAME"
>/usr/lib</TT
> (<TT
CLASS="FILENAME"
>dict</TT
>,
<TT
CLASS="FILENAME"
>terminfo</TT
>, <TT
CLASS="FILENAME"
>zoneinfo</TT
>).</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1701"
HREF="#AEN1701"
><SPAN
CLASS="footnote"
>[31]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Obviously, there are no manual pages in <TT
CLASS="FILENAME"
>/</TT
>
because they are not required at boot time nor are they required in
emergencies. Really.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1741"
HREF="#AEN1741"
><SPAN
CLASS="footnote"
>[32]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>For example, if <TT
CLASS="FILENAME"
>/usr/local/man</TT
>
has no manual pages in section 4 (Devices), then
<TT
CLASS="FILENAME"
>/usr/local/man/man4</TT
> may be omitted.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1797"
HREF="#AEN1797"
><SPAN
CLASS="footnote"
>[33]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
> A major exception to this rule is the
United Kingdom, which is `GB' in the ISO 3166, but `UK' for most email
addresses.</P
></TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="5%"
><A
NAME="FTN.AEN1944"
HREF="#AEN1944"
><SPAN
CLASS="footnote"
>[34]</SPAN
></A
></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
WIDTH="95%"
><P
>Some such files include:
<TT
CLASS="FILENAME"
>airport</TT
>, <TT
CLASS="FILENAME"
> birthtoken</TT
>, <TT
CLASS="FILENAME"
>eqnchar</TT
>, <TT
CLASS="FILENAME"
> getopt</TT