LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Updated to incorporate changes in FHS 2.3

This commit is contained in:
binh 2004-02-04 00:59:32 +00:00
parent 5ee489276d
commit 065cab2f4b
1 changed files with 39 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
LDP/guide/docbook/Linux-Filesystem-Hierarchy/lib.xml
View File

@ -63,12 +63,16 @@ The /lib directory contains kernel modules and those shared library images (the
<listitem>
<para>is the PCI equivalent of the
/lib/modules/'kernel-version'/isapnpmap.dep file.
It is recommended that apart from autosave and lock files programs should refrain from creating non dot files
or directories in a home directory without user intervention.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>/lib/modules/&apos;kernel-version&apos;/usbmap</term>
It is recommended that apart from autosave and lock files programs should refrain from creating non dot files
or directories in a home directory without user intervention.
<listitem>
<para>is the USB equivalent of the
/lib/modules/'kernel-version'/isapnpmap.dep file.</para>
@ -91,52 +95,54 @@ The /lib directory contains kernel modules and those shared library images (the
<para>PAM library files.</para>
</listitem>
</varlistentry>
It is recommended that apart from autosave and lock files programs should refrain from creating non dot files
or directories in a home directory without user intervention.
</variablelist>
</para>
<para>
<screen>
The FSSTND requires that shared libraries that are only necessary
for binaries in /usr (such as any X Window binaries) must not be
in /lib. Only the shared libraries required to run binaries in /bin
and /sbin may be here. In particular, the library libm.so.* may
also be placed in /usr/lib if it is not required by anything in
/bin or /sbin.
The FSSTND states that the /lib directory contains those shared library
images needed to boot the system and run the commands in the root filesystem,
ie. by binaries in /bin and /sbin.
At least one of each of the following filename patterns are required
(they may be files, or symbolic links):
Shared libraries that are only necessary for binaries in /usr (such as any
X Window binaries) must not be in /lib. Only the shared libraries required
to run binaries in /bin and /sbin may be here. In particular, the library
libm.so.* may also be placed in /usr/lib if it is not required by anything
in /bin or /sbin.
libc.so.* The dynamically-linked C library (optional)
ld* The execution time linker/loader (optional)
At least one of each of the following filename patterns are required (they
may be files, or symbolic links):
If a C preprocessor is installed, /lib/cpp must be a reference
to it, for historical reasons. The usual placement of this binary
is /usr/lib/gcc-lib/&lt;target&gt;/&lt;version&gt;/cpp. /lib/cpp
can either point at this binary, or at any other reference to
this binary which exists in the filesystem. (For example,
/usr/bin/cpp is also often used.)
libc.so.* The dynamically-linked C library (optional)
ld* The execution time linker/loader (optional)
The following directories, or symbolic links to directories, must be in
If a C preprocessor is installed, /lib/cpp must be a reference to it, for
historical reasons. The usual placement of this binary is /usr/bin/cpp.
The following directories, or symbolic links to directories, must be in
/lib, if the corresponding subsystem is installed:
/lib -- essential shared libraries and kernel modules
/lib/modules Loadable kernel modules (optional)
/lib&lt;qual&gt; : Alternate format essential shared libraries
(optional)
There may be one or more variants of the /lib directory on systems
which support more than one binary format requiring separate libraries.
This is commonly used for 64-bit or 32-bit support on systems which
support multiple binary formats, but require libraries of the same name.
In this case, /lib32 and /lib64 might be the library directories, and
/lib a symlink to one of them.
modules Loadable kernel modules (optional)
If one or more of these directories exist, the requirements for
their contents are the same as the normal /lib directory, except
that /lib&lt;qual&gt;/cpp is not required. /lib&lt;qual&gt;/cpp is
still permitted: this allows the case where /lib and /lib&lt;qual&gt;
are the same (one is a symbolic link to the other).
/lib&lt;qual&gt; : Alternate format essential shared libraries (optional)
There may be one or more variants of the /lib directory on systems which
support more than one binary format requiring separate libraries.
This is commonly used for 64-bit or 32-bit support on systems which support
multiple binary formats, but require libraries of the same name. In this
case, /lib32 and /lib64 might be the library directories, and /lib a symlink
to one of them.
If one or more of these directories exist, the requirements for their contents
are the same as the normal /lib directory, except that /lib&lt;qual&gt;/cpp is
not required.
/lib&lt;qual&gt;/cpp is still permitted: this allows the case where /lib and
/lib&lt;qual&gt; are the same (one is a symbolic link to the other).
</screen>
</para>