Static
<B
CLASS="COMMAND"
>sync</B
> is useful in some emergency situations.
Note that these need not be statically linked versions of the standard
<B
CLASS="COMMAND"
>ln</B
> and <B
CLASS="COMMAND"
>sync</B
>, but may
be.</P
><P
>The <B
CLASS="COMMAND"
>ldconfig</B
> binary is optional for
<TT
CLASS="FILENAME"
>/sbin</TT
> since a site may choose to run
<B
CLASS="COMMAND"
>ldconfig</B
> at boot time, rather than only when
upgrading the shared libraries. (It's not clear whether or not it is
advantageous to run <B
CLASS="COMMAND"
>ldconfig</B
> on each boot.) Even
so, some people like <B
CLASS="COMMAND"
>ldconfig</B
> around for the
following (all too common) situation:</P
><P
></P
><OL
TYPE="1"
><LI
STYLE="list-style-type: disc"
><P
>I've just removed <TT
CLASS="FILENAME"
>/lib/<file></TT
>.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>I can't find out the name of the library because <B
CLASS="COMMAND"
>ls</B
> is
dynamically linked, I'm using a shell that doesn't have <B
CLASS="COMMAND"
>ls</B
>
built-in, and I don't know about using "<B
CLASS="COMMAND"
>echo *</B
>" as a
replacement.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
>I have a static <B
CLASS="COMMAND"
>sln</B
>, but I don't know what to call the link.</P
></LI
></OL
></LI
><LI
STYLE="list-style-type: disc"
><P
>Miscellaneous:</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
><B
CLASS="COMMAND"
>ctrlaltdel</B
></P
></LI
><LI
STYLE="list-style-type: disc"
><P
><B
CLASS="COMMAND"
>kbdrate</B
></P
></LI
></UL
><P
>So as to cope with the fact that some keyboards come up with
such a high repeat rate as to be unusable,
<B
CLASS="COMMAND"
>kbdrate</B
> may be installed in
<TT
CLASS="FILENAME"
>/sbin</TT
> on some systems.</P
><P
>Since the default action in the kernel for the Ctrl-Alt-Del key
combination is an instant hard reboot, it is generally advisable to
disable the behavior before mounting the root filesystem in read-write
mode. Some <B
CLASS="COMMAND"
>init</B
> suites are able to disable
Ctrl-Alt-Del, but others may require the
<B
CLASS="COMMAND"
>ctrlaltdel</B
> program, which may be installed in
<TT
CLASS="FILENAME"
>/sbin</TT
> on those systems.</P
></LI
></UL
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="USRINCLUDEHEADERFILESINCLUDEDBYCP"
>/usr/include : Header files included by C programs</A
></H3
><P
>These symbolic links are required if a C or C++ compiler is
installed and only for systems not based on glibc.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
> /usr/include/asm -> /usr/src/linux/include/asm-<arch>
/usr/include/linux -> /usr/src/linux/include/linux</PRE
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="USRSRCSOURCECODE2"
>/usr/src : Source code</A
></H3
><P
>For systems based on glibc, there are no specific guidelines for
this directory. For systems based on Linux libc revisions prior to
glibc, the following guidelines and rationale apply:</P
><P
>The only source code that should be placed in a specific
location is the Linux kernel source code. It is located in
<TT
CLASS="FILENAME"
>/usr/src/linux</TT
>.</P
><P
>If a C or C++ compiler is installed, but the complete Linux
kernel source code is not installed, then the include files from the
kernel source code must be located in these directories:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
> /usr/src/linux/include/asm-<arch>
/usr/src/linux/include/linux</PRE
></TD
></TR
></TABLE
><P
><TT
CLASS="FILENAME"
><arch></TT
> is the name of the system
architecture.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="note.gif"
HSPACE="5"
ALT="Note"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Note</B
></TH
></TR
><TR
><TD
> </TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
> <TT
CLASS="FILENAME"
>/usr/src/linux</TT
>
may be a symbolic link to a kernel source code tree.</P
></TD
></TR
></TABLE
></DIV
><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
>It is important that the kernel include files be located in
<TT
CLASS="FILENAME"
>/usr/src/linux</TT
> and not in
<TT
CLASS="FILENAME"
>/usr/include</TT
> so there are no problems when system
administrators upgrade their kernel version for the first time. </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="VARSPOOLCRONCRONANDATJOBS"
>/var/spool/cron : cron and at jobs</A
></H3
><P
>This directory contains the variable data for the
<B
CLASS="COMMAND"
>cron</B
> and <B
CLASS="COMMAND"
>at</B
> programs.</P
></DIV
></DIV
></DIV
><DIV
CLASS="CHAPTER"
><HR><H1
><A
NAME="APPENDIX"
></A
>Chapter 7. Appendix</H1
><DIV
CLASS="SECTION"
><H2
CLASS="SECTION"
><A
NAME="THEFHSMAILINGLIST"
>The FHS mailing list</A
></H2
><P
>The FHS mailing list is located at
<freestandards-fhs-discuss@lists.sourceforge.net>. You can
subscribe to the mailing list at this page <A
HREF="http://sourceforge.net/projects/freestandards/"
TARGET="_top"
>http://sourceforge.net/projects/freestandards/</A
>.</P
><P
>Thanks to Network Operations at the University of California at
San Diego who allowed us to use their excellent mailing list
server.</P
><P
>As noted in the introduction, please do not send mail to the mailing
list without first contacting the FHS editor or a listed contributor.</P
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="BACKGROUNDOFTHEFHS"
>Background of the FHS</A
></H2
><P
>The process of developing a standard filesystem hierarchy began
in August 1993 with an effort to restructure the file and directory
structure of Linux. The FSSTND, a filesystem hierarchy standard
specific to the Linux operating system, was released on February 14,
1994. Subsequent revisions were released on October 9, 1994 and March
28, 1995.