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

Everything works! :-)

This commit is contained in:
binh 2003-09-14 11:47:21 +00:00
parent 71dd7d2ffa
commit 8de6f7bf91
12 changed files with 1175 additions and 722 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
LDP/guide/docbook/Linux-Filesystem-Hierarchy/Contributors.xml
View File

@ -3,10 +3,9 @@
<title>Contributors</title>
<para>
The author would like to thank a group of members (who
wish to remain anonymous) from MLUG www.mlug.org.au for having
the time and patience to help proof read this document
before going to publication.
The author would like to thank a group of members (who wish to remain anonymous) from MLUG
<ulink url="http://www.mlug.org.au">http://www.mlug.org.au</ulink> for having the time
and patience to help proof read this document before going to publication.
</para>
</appendix>

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

@ -33,8 +33,8 @@
<bookinfo>
<title>Linux Filesystem Hierarchy</title>
<subtitle>Version 0.51</subtitle>
<pubdate>2003-08-14</pubdate>
<subtitle>Version 0.61</subtitle>
<pubdate>2003-09-14</pubdate>
<author>
<firstname>Binh</firstname>
@ -48,7 +48,7 @@
<abstract>
<para>
This document outlines the set of requirements and guidelines for file and directory placement under the Linux operating system according to those of the FSSTND v2.2 final (May 23, 2001) and also its actual implementation on an arbitrary system. It is meant to be accessible to all members of the Linux community, be distribution independent and is intended discuss the impact of the FSSTND and how it has managed to increase the efficiency of support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems.
This document outlines the set of requirements and guidelines for file and directory placement under the Linux operating system according to those of the FSSTND v2.2 final (May 23, 2001) and also its actual implementation on an arbitrary system. It is meant to be accessible to all members of the Linux community, be distribution independent and is intended discuss the impact of the FSSTND and how it has managed to increase the efficiency of support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. The next revision of this document will occur when FSSTND 2.3 final is complete.
</para>
</abstract>
@ -67,7 +67,7 @@ the section entitled "GNU Free Documentation License".</para>
<para>The source code and other machine readable formats
of this book can be found on the Internet at the
Linux Documentation Project home page <ulink
url="http://www.tldp.org/">http://www.tldp.org/</ulink>
url="http://www.tldp.org">http://www.tldp.org</ulink>
</para>
</preface>

4
LDP/guide/docbook/Linux-Filesystem-Hierarchy/Sources.xml
View File

@ -1,4 +1,4 @@
<bibliography id="Sources">
<appendix id="Sources">
<title>Sources</title>
@ -272,4 +272,4 @@
</listitem>
</itemizedlist>
</bibliography>
</appendix>

4
LDP/guide/docbook/Linux-Filesystem-Hierarchy/The-Root-Directory.xml
View File

@ -139,7 +139,7 @@
</listitem>
<listitem>
<para>Mandrake 9.0 on /dev/hda7</para>
<para>Mandrake 9.1 on /dev/hda7</para>
</listitem>
<listitem>
@ -165,7 +165,7 @@
<para>
<emphasis>bin/ dev/ home/ lost+found/ proc/ sbin/ usr/ cdrom/ opt/ vmlinuz
boot/ etc/ lib/ mnt/ root/ tmp/ var/ cdrom1/ floppy/ initrd/ /tftpboot
boot/ etc/ lib/ mnt/ root/ tmp/ var/ dvd/ floppy/ initrd/ /tftpboot
</emphasis>
</para>

115
LDP/guide/docbook/Linux-Filesystem-Hierarchy/boot.xml
View File

@ -14,7 +14,9 @@
linked at /).</para>
<para><variablelist><varlistentry><term>/boot/boot.0300</term><listitem><para>Backup
master boot record.</para></listitem></varlistentry><varlistentry><term>/boot/boot.b</term><listitem><para>This
master boot record.</para></listitem></varlistentry>
<varlistentry><term>/boot/boot.b</term><listitem><para>This
is installed as the basic boot sector. In the case of most modern
distributions it is actually a symobolic link to one of four files
/boot/boot-bmp.b, /boot/boot-menu.b, /boot/boot-text.b, /boot/boot-compat.b
@ -23,60 +25,83 @@
ensure compatibility respectively. In each case re-installation of lilo is
necessary in order to complete the changes. To change the actual
&#39;boot-logo&#39; you can either use utilites such as fblogo or the more
refined bootsplash.</para></listitem></varlistentry><varlistentry><term>/boot/chain.b</term><listitem><para>Used
to boot non-Linux operating systems.</para></listitem></varlistentry><varlistentry><term>/boot/config-kernel-version</term><listitem><para>Installed
refined bootsplash.</para></listitem></varlistentry>
<varlistentry><term>/boot/chain.b</term><listitem><para>Used
to boot non-Linux operating systems.</para></listitem></varlistentry>
<varlistentry><term>/boot/config-kernel-version</term><listitem><para>Installed
kernel configuration. This file is most useful when compiling kernels on
other systems or device modules. Below is a small sample of what the
contents of the file looks like.</para><para><screen>
CONFIG_X86=y
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_SCSI_DEBUG=m
CONFIG_I2O=m
CONFIG_ARCNET_ETH=y
CONFIG_FMV18X=m
CONFIG_HPLAN_PLUS=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_HISAX_HFC_PCI=y
CONFIG_ISDN_DRV_AVMB1_C4=m
CONFIG_USB_RIO500=m
CONFIG_QUOTA=y
CONFIG_AUTOFS_FS=m
CONFIG_ADFS_FS=m
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=m
CONFIG_FBCON_VGA=m
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=m
CONFIG_SOUND_CMPCI=m
CONFIG_AEDSP16=m
</screen></para><para>As you can see, its rather
contents of the file looks like.</para>
<para><screen>
CONFIG_X86=y
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_SCSI_DEBUG=m
CONFIG_I2O=m
CONFIG_ARCNET_ETH=y
CONFIG_FMV18X=m
CONFIG_HPLAN_PLUS=m
CONFIG_ETH16I=m
CONFIG_NE2000=m
CONFIG_HISAX_HFC_PCI=y
CONFIG_ISDN_DRV_AVMB1_C4=m
CONFIG_USB_RIO500=m
CONFIG_QUOTA=y
CONFIG_AUTOFS_FS=m
CONFIG_ADFS_FS=m
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=m
CONFIG_FBCON_VGA=m
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=m
CONFIG_SOUND_CMPCI=m
CONFIG_AEDSP16=m
</screen></para>
<para>As you can see, its rather
simplistic. The line begins with the configuration option and whether its
configured as part of the kernel, as a module or not at all. Lines beginning
with a # symbol are comments and are not interpreted during processing.</para></listitem></varlistentry><varlistentry><term>/boot/os2_d.b</term><listitem><para>Used
to boot to the 0S/2 operating system.</para></listitem></varlistentry><varlistentry><term>/boot/map</term><listitem><para>Contains
the location of the kernel.</para></listitem></varlistentry><varlistentry><term>/boot/vmlinuz,
/boot/vmlinuz-kernel-version</term><listitem><para>Normally the kernel or
symbolic link to the kernel.</para></listitem></varlistentry><varlistentry><term>/boot/grub</term><listitem><para>This
with a # symbol are comments and are not interpreted during processing.</para></listitem></varlistentry>
<varlistentry><term>/boot/os2_d.b</term><listitem><para>Used
to boot to the 0S/2 operating system.</para></listitem></varlistentry>
<varlistentry><term>/boot/map</term><listitem><para>Contains
the location of the kernel.</para></listitem></varlistentry>
<varlistentry><term>/boot/vmlinuz, /boot/vmlinuz-kernel-version</term><listitem><para>Normally the kernel or
symbolic link to the kernel.</para></listitem></varlistentry>
<varlistentry><term>/boot/grub</term><listitem><para>This
subdirectory contains the GRUB configuration files including boot-up images
and sounds. GRUB is the GNU GRand Unified Bootloader, a project which
intends to solve all bootup problems once and for all. One of the most
interesting features, is that you don&#39;t have to install a new partition
or kernel, you can change all parameters at boot time via the GRUB Console,
since it knows about the filesystems.</para></listitem></varlistentry><varlistentry><term>/boot/grub/device.map</term><listitem><para>Maps
since it knows about the filesystems.</para></listitem></varlistentry>
<varlistentry><term>/boot/grub/device.map</term><listitem><para>Maps
devices in /dev to those used by grub. For example, (/dev/fd0) is
represented by /dev/fd0 and (hd0, 4) is referenced by /dev/hda5.</para></listitem></varlistentry><varlistentry><term>/boot/grub/grub.conf,
/boot/grub/menu.lst</term><listitem><para>Grub configuration file.</para></listitem></varlistentry><varlistentry><term>/boot/grub/messages</term><listitem><para>Grub
boot-up welcome message.</para></listitem></varlistentry><varlistentry><term>/boot/grub/splash.xpm.gz</term><listitem><para>Grub
represented by /dev/fd0 and (hd0, 4) is referenced by /dev/hda5.</para></listitem>
</varlistentry><varlistentry><term>/boot/grub/grub.conf,
/boot/grub/menu.lst</term><listitem><para>Grub configuration file.</para></listitem></varlistentry>
<varlistentry><term>/boot/grub/messages</term><listitem><para>Grub
boot-up welcome message.</para></listitem></varlistentry>
<varlistentry><term>/boot/grub/splash.xpm.gz</term><listitem><para>Grub
boot-up background image.</para></listitem></varlistentry></variablelist></para>
</sect1>

1478
LDP/guide/docbook/Linux-Filesystem-Hierarchy/etc.xml
View File

File diff suppressed because it is too large Load Diff

1
LDP/guide/docbook/Linux-Filesystem-Hierarchy/initrd.xml
View File

@ -104,5 +104,4 @@ from the CD-ROM, and loading the RAM disk from CD without need of floppies.
</screen>
</para>
</sect1>

48
LDP/guide/docbook/Linux-Filesystem-Hierarchy/lostfound.xml
View File

@ -24,29 +24,29 @@
These files were not able to be recovered.
</para>
<para>
<screen>
total 368
-rw-r--r-- 1 root root 110891 Oct 5 14:14 #388200
-rw-r--r-- 1 root root 215 Oct 5 14:14 #388201
-rw-r--r-- 1 root root 110303 Oct 6 23:09 #388813
-rw-r--r-- 1 root root 141 Oct 6 23:09 #388814
-rw-r--r-- 1 root root 110604 Oct 6 23:09 #388815a
-rw-r--r-- 1 root root 194 Oct 6 23:09 #388816
srwxr-xr-x 1 root root 0 Oct 6 13:00 #51430
srwxr-xr-x 1 root root 0 Oct 6 00:23 #51433
-rw------- 1 root root 63 Oct 6 00:23 #51434
srwxr-xr-x 1 root root 0 Oct 6 13:00 #51436
srwxrwxrwx 1 root root 0 Oct 6 00:23 #51437
srwx------ 1 root root 0 Oct 6 00:23 #51438
-rw------- 1 root root 63 Oct 6 13:00 #51439
srwxrwxrwx 1 root root 0 Oct 6 13:00 #51440
srwx------ 1 root root 0 Oct 6 13:00 #51442
-rw------- 1 root root 63 Oct 6 23:09 #51443
srwx------ 1 root root 0 Oct 6 10:40 #51445
srwxrwxrwx 1 root root 0 Oct 6 23:09 #51446
srwx------ 1 root root 0 Oct 6 23:09 #51448
</screen>
</para>
<para>
<screen>
total 368
-rw-r--r-- 1 root root 110891 Oct 5 14:14 #388200
-rw-r--r-- 1 root root 215 Oct 5 14:14 #388201
-rw-r--r-- 1 root root 110303 Oct 6 23:09 #388813
-rw-r--r-- 1 root root 141 Oct 6 23:09 #388814
-rw-r--r-- 1 root root 110604 Oct 6 23:09 #388815a
-rw-r--r-- 1 root root 194 Oct 6 23:09 #388816
srwxr-xr-x 1 root root 0 Oct 6 13:00 #51430
srwxr-xr-x 1 root root 0 Oct 6 00:23 #51433
-rw------- 1 root root 63 Oct 6 00:23 #51434
srwxr-xr-x 1 root root 0 Oct 6 13:00 #51436
srwxrwxrwx 1 root root 0 Oct 6 00:23 #51437
srwx------ 1 root root 0 Oct 6 00:23 #51438
-rw------- 1 root root 63 Oct 6 13:00 #51439
srwxrwxrwx 1 root root 0 Oct 6 13:00 #51440
srwx------ 1 root root 0 Oct 6 13:00 #51442
-rw------- 1 root root 63 Oct 6 23:09 #51443
srwx------ 1 root root 0 Oct 6 10:40 #51445
srwxrwxrwx 1 root root 0 Oct 6 23:09 #51446
srwx------ 1 root root 0 Oct 6 23:09 #51448
</screen>
</para>
</sect1>

8
LDP/guide/docbook/Linux-Filesystem-Hierarchy/mnt.xml
View File

@ -20,8 +20,8 @@
the mount operation will make it look like the contents of the new
filesystem are the contents of an existing subdirectory in some already
mounted filesystem.</para> <para>The mounts could be done as in the
following example: <screen> <prompt>$</prompt> <userinput>mount /dev/hda2
/home</userinput> <prompt> $</prompt> <userinput>mount /dev/hda3 /usr</userinput>
following example: <screen> <prompt>$</prompt> <userinput>mount /dev/hda2 /home</userinput>
<prompt>$</prompt> <userinput>mount /dev/hda3 /usr</userinput>
<prompt>$</prompt> </screen>The <command>mount</command> command takes two
arguments. The first one is the device file corresponding to the disk or
partition containing the filesystem. The second one is the directory below
@ -95,7 +95,8 @@
either the device file or the mount point. For example, to unmount the
directories of the previous example, one could use the commands</para>
<screen> <prompt>$</prompt> <userinput>umount /dev/hda2</userinput><prompt>
$</prompt> <userinput>umount /usr</userinput><prompt> $</prompt> </screen>
$</prompt> <userinput>umount /usr</userinput>
<prompt>$</prompt> </screen>
<para>See the man page for further instructions on how to use the command.
It is imperative that you always unmount a mounted floppy.
<emphasis>Don&#39;t just pop the floppy out of the drive!</emphasis> Because
@ -153,4 +154,5 @@
<command>mount</command> manual page. If you aren&#39;t careful, mounting an
MS-DOS filesystem gives everyone at least read access to the files in it,
which is not a good idea.</para></sect2>
</sect1>

164
LDP/guide/docbook/Linux-Filesystem-Hierarchy/proc.xml
View File

@ -358,7 +358,8 @@ irq 8: 3 rtc irq 15: 83 ide1
13: 0 0 XT-PIC fpu 14: 22491 24012 IO-APIC-edge ide0
15: 2183 2415 IO-APIC-edge ide1
17: 30564 30414 IO-APIC-level eth0
18: 177 164 IO-APIC-level bttv NMI: 2457961 2457959 LOC: 2457882 2457881 ERR: 2155
18: 177 164 IO-APIC-level bttv NMI: 2457961 2457959
LOC: 2457882 2457881 ERR: 2155
</screen>
</para></listitem></varlistentry>
@ -480,7 +481,7 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term>/proc/net</term><listitem><para> Status information
about network protocols.</para></listitem></varlistentry>
<varlistentry><term>IPv6 information</term><listitem><para>
<varlistentry><term><emphasis>IPv6 information</emphasis></term><listitem><para>
<variablelist>
@ -513,7 +514,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>General Network information</term><listitem><para>
<varlistentry><term><emphasis>General Network information</emphasis></term><listitem><para>
<variablelist>
@ -714,9 +715,12 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term></term><listitem>
<para><screen>
# cat
/proc/sys/fs/file-max 4096 # echo 8192 &#62; /proc/sys/fs/file-max # cat
/proc/sys/fs/file-max 8192 </screen></para></listitem></varlistentry>
# cat /proc/sys/fs/file-max
4096
# echo 8192 &#62; /proc/sys/fs/file-max
# cat /proc/sys/fs/file-max
8192
</screen></para></listitem></varlistentry>
<varlistentry><term></term><listitem>
<para>This method of revision is useful for all customizable parameters
@ -1121,7 +1125,7 @@ irq 8: 3 rtc irq 15: 83 ide1
1 1 Can read MCN: 1 1 Reports media changed: 1 1 Can play audio: 1 1 You see
two drives, sr0 and hdb, along with a list of their features.</para></listitem></varlistentry>
<varlistentry><term>SUNRPC</term><listitem><para>
<varlistentry><term><emphasis>SUNRPC</emphasis></term><listitem><para>
<variablelist>
@ -1148,7 +1152,7 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term>GENERAL PARAMETERS</term><listitem><para>
<varlistentry><term><emphasis>GENERAL PARAMETERS</emphasis></term><listitem><para>
<variablelist>
@ -1187,7 +1191,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>UNIX DOMAIN SOCKETS</term><listitem><para>
<varlistentry><term><emphasis>UNIX DOMAIN SOCKETS</emphasis></term><listitem><para>
<variablelist>
@ -1201,7 +1205,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>IPv4</term><listitem><para>
<varlistentry><term><emphasis>IPv4</emphasis></term><listitem><para>
<variablelist>
@ -1219,7 +1223,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>ICMP settings</term><listitem><para>
<varlistentry><term><emphasis>ICMP settings</emphasis></term><listitem><para>
<variablelist>
@ -1242,7 +1246,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>IP settings</term><listitem><para>
<varlistentry><term><emphasis>IP settings</emphasis></term><listitem><para>
<variablelist>
@ -1280,7 +1284,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>IP fragmentation settings</term><listitem><para>
<varlistentry><term><emphasis>IP fragmentation settings</emphasis></term><listitem><para>
<variablelist>
@ -1294,7 +1298,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>TCP settings</term><listitem><para>
<varlistentry><term><emphasis>TCP settings</emphasis></term><listitem><para>
<variablelist>
@ -1380,65 +1384,83 @@ irq 8: 3 rtc irq 15: 83 ide1
interfaces, whereas changes in the other subdirectories affect only one
interface. All directories have the same entries:</para></listitem></varlistentry>
<varlistentry><term>accept_redirects</term><listitem><para> This switch
<varlistentry><term>accept_redirects</term><listitem><para>This switch
decides if the kernel accepts ICMP redirect messages or not. The default is
&#39;yes&#39; if the kernel is configured for a regular host and
&#39;no&#39; for a router configuration.</para></listitem></varlistentry>
<varlistentry><term>accept_source_route</term><listitem><para> Should source
<varlistentry><term>accept_source_route</term><listitem><para>Should source
routed packages be accepted or declined. The default is dependent on the
kernel configuration. It&#39;s &#39;yes&#39; for routers and &#39;no&#39;
for hosts.</para></listitem></varlistentry> <varlistentry><term>bootp_relay</term><listitem><para>
for hosts.</para></listitem></varlistentry>
<varlistentry><term>bootp_relay</term><listitem><para>
Accept packets with source address 0.b.c.d with destinations not to this
host as local ones. It is supposed that a BOOTP relay daemon will catch and
forward such packets. The default is 0.</para></listitem></varlistentry>
<varlistentry><term>forwarding</term><listitem><para> Enable or disable IP
<varlistentry><term>forwarding</term><listitem><para>Enable or disable IP
forwarding on this interface.</para></listitem></varlistentry>
<varlistentry><term>log_martians</term><listitem><para> Log packets with
<varlistentry><term>log_martians</term><listitem><para>Log packets with
source addresses with no known route to kernel log.</para></listitem></varlistentry>
<varlistentry><term>mc_forwarding</term><listitem><para> Do multicast
<varlistentry><term>mc_forwarding</term><listitem><para>Do multicast
routing. The kernel needs to be compiled with CONFIG_MROUTE and a multicast
routing daemon is required.</para></listitem></varlistentry>
<varlistentry><term>proxy_arp</term><listitem><para> Does (1) or does not
<varlistentry><term>proxy_arp</term><listitem><para>Does (1) or does not
(0) perform proxy ARP.</para></listitem></varlistentry>
<varlistentry><term>rp_filter</term><listitem><para> Integer value
<varlistentry><term>rp_filter</term><listitem><para>Integer value
determines if a source validation should be made. 1 means yes, 0 means no.
Disabled by default, but local/broadcast address spoofing is always on. If
you set this to 1 on a router that is the only connection for a network to
the net, it will prevent spoofing attacks against your internal networks
(external addresses can still be spoofed), without the need for additional
firewall rules.</para></listitem></varlistentry>
<varlistentry><term>secure_redirects</term><listitem><para> Accept ICMP
<varlistentry><term>secure_redirects</term><listitem><para>Accept ICMP
redirect messages only for gateways, listed in default gateway list. Enabled
by default.</para></listitem></varlistentry> <varlistentry><term>shared_media</term><listitem><para>
by default.</para></listitem></varlistentry>
<varlistentry><term>shared_media</term><listitem><para>
If it is not set the kernel does not assume that different subnets on this
device can communicate directly. Default setting is &#39;yes&#39;.</para></listitem></varlistentry>
<varlistentry><term>send_redirects</term><listitem><para> Determines whether
<varlistentry><term>send_redirects</term><listitem><para>Determines whether
to send ICMP redirects to other hosts.</para></listitem></varlistentry>
<varlistentry><term>Routing settings</term><listitem><para> The directory
<varlistentry><term>Routing settings</term><listitem><para>The directory
/proc/sys/net/ipv4/route contains several file to control routing issues.</para></listitem></varlistentry>
<varlistentry><term>error_burst and error_cost</term><listitem><para> These
<varlistentry><term>error_burst and error_cost</term><listitem><para>These
parameters are used to limit the warning messages written to the kernel log
from the routing code. The higher the error_cost factor is, the fewer
messages will be written. Error_burst controls when messages will be
dropped. The default settings limit warning messages to one every five
seconds.</para></listitem></varlistentry> <varlistentry><term>flush</term><listitem><para>
Writing to this file results in a flush of the routing cache.</para></listitem></varlistentry>
<varlistentry><term>gc_elastic, gc_interval, gc_min_interval, gc_tresh,
gc_timeout</term><listitem><para> Values to control the frequency and
behavior of the garbage collection algorithm for the routing cache.</para></listitem></varlistentry>
<varlistentry><term>max_size</term><listitem><para> Maximum size of the
routing cache. Old entries will be purged once the cache reached has this
size.</para></listitem></varlistentry> <varlistentry><term>max_delay,
min_delay</term><listitem><para> Delays for flushing the routing cache.</para></listitem></varlistentry>
<varlistentry><term>redirect_load, redirect_number</term><listitem><para>
Factors which determine if more ICPM redirects should be sent to a specific
host. No redirects will be sent once the load limit or the maximum number of
redirects has been reached.</para></listitem></varlistentry>
<varlistentry><term>redirect_silence</term><listitem><para> Timeout for
<varlistentry><term>redirect_silence</term><listitem><para>Timeout for
redirects. After this period redirects will be sent again, even if this has
been stopped, because the load or number limit has been reached. </para></listitem></varlistentry>
<varlistentry><term>/proc/sys/net/ipv4/neigh</term><listitem><para> Network
<varlistentry><term>/proc/sys/net/ipv4/neigh</term><listitem><para>Network
Neighbor handling. It contains settings about how to handle connections with
direct neighbors (nodes attached to the same link). As we saw it in the conf
directory, there is a default subdirectory which holds the default values,
@ -1448,33 +1470,46 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term></term><listitem><para>In the interface directories you&#39;ll find the following entries:</para></listitem></varlistentry>
<varlistentry><term>base_reachable_time</term><listitem><para> A base value
<varlistentry><term>base_reachable_time</term><listitem><para>A base value
used for computing the random reachable time value as specified in RFC2461.</para></listitem></varlistentry>
<varlistentry><term>retrans_time</term><listitem><para> The time, expressed
<varlistentry><term>retrans_time</term><listitem><para>The time, expressed
in jiffies (1/100 sec), between retransmitted Neighbor Solicitation
messages. Used for address resolution and to determine if a neighbor is
unreachable.</para></listitem></varlistentry> <varlistentry><term>unres_qlen</term><listitem><para>
unreachable.</para></listitem></varlistentry>
<varlistentry><term>unres_qlen</term><listitem><para>
Maximum queue length for a pending arp request - the number of packets which
are accepted from other layers while the ARP address is still resolved.</para></listitem></varlistentry>
<varlistentry><term>anycast_delay</term><listitem><para> Maximum for random
<varlistentry><term>anycast_delay</term><listitem><para>Maximum for random
delay of answers to neighbor solicitation messages in jiffies (1/100 sec).
Not yet implemented (Linux does not have anycast support yet).</para></listitem></varlistentry>
<varlistentry><term>ucast_solicit</term><listitem><para> Maximum number of
<varlistentry><term>ucast_solicit</term><listitem><para>Maximum number of
retries for unicast solicitation.</para></listitem></varlistentry>
<varlistentry><term>mcast_solicit</term><listitem><para> Maximum number of
<varlistentry><term>mcast_solicit</term><listitem><para>Maximum number of
retries for multicast solicitation.</para></listitem></varlistentry>
<varlistentry><term>delay_first_probe_time</term><listitem><para> Delay for
<varlistentry><term>delay_first_probe_time</term><listitem><para>Delay for
the first time probe if the neighbor is reachable. (see gc_stale_time)</para></listitem></varlistentry>
<varlistentry><term>locktime</term><listitem><para> An ARP/neighbor entry is
<varlistentry><term>locktime</term><listitem><para>An ARP/neighbor entry is
only replaced with a new one if the old is at least locktime old. This
prevents ARP cache thrashing.</para></listitem></varlistentry>
<varlistentry><term>proxy_delay</term><listitem><para> Maximum time (real
<varlistentry><term>proxy_delay</term><listitem><para>Maximum time (real
time is random [0..proxytime]) before answering to an ARP request for which
we have an proxy ARP entry. In some cases, this is used to prevent network
flooding.</para></listitem></varlistentry> <varlistentry><term>proxy_qlen</term><listitem><para>
flooding.</para></listitem></varlistentry>
<varlistentry><term>proxy_qlen</term><listitem><para>
Maximum queue length of the delayed proxy arp timer. (see proxy_delay).</para></listitem></varlistentry>
<varlistentry><term>app_solcit</term><listitem><para> Determines the number
of requests to send to the user level ARP daemon. Use 0 to turn off.</para></listitem></varlistentry>
<varlistentry><term>gc_stale_time</term><listitem><para> Determines how
often to check for stale ARP entries. After an ARP entry is stale it will be
resolved again (which is useful when an IP address migrates to another
@ -1486,7 +1521,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>APPLETALK</term><listitem><para>
<varlistentry><term><emphasis>APPLETALK</emphasis></term><listitem><para>
<variablelist>
@ -1507,16 +1542,18 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term>aarp-tick-time</term><listitem><para>
Controls the rate at which expires are checked.</para></listitem></varlistentry>
<varlistentry><term>/proc/net/appletalk</term><listitem><para> Holds the
<varlistentry><term>/proc/net/appletalk</term><listitem><para>Holds the
list of active Appletalk sockets on a machine. The fields indicate the DDP
type, the local address (in network:node format) the remote address, the
size of the transmit pending queue, the size of the received queue (bytes
waiting for applications to read) the state and the uid owning the socket.</para></listitem></varlistentry>
<varlistentry><term>/proc/net/atalk_iface</term><listitem><para> lists all
<varlistentry><term>/proc/net/atalk_iface</term><listitem><para>lists all
the interfaces configured for appletalk.It shows the name of the interface,
its Appletalk address, the network range on that address (or network number
for phase 1 networks), and the status of the interface.</para></listitem></varlistentry>
<varlistentry><term>/proc/net/atalk_route</term><listitem><para> lists each
<varlistentry><term>/proc/net/atalk_route</term><listitem><para>lists each
known network route. It lists the target (network) that the route leads to,
the router (may be directly connected), the route flags, and the device the
route is using.</para></listitem></varlistentry>
@ -1525,7 +1562,7 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>IPX</term><listitem><para>
<varlistentry><term><emphasis>IPX</emphasis></term><listitem><para>
<variablelist>
@ -1562,7 +1599,7 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term>/proc/tty/drivers</term><listitem><para>
list of drivers and their usage.</para></listitem></varlistentry>
<varlistentry><term>/proc/tty/ldiscs</term><listitem><para> registered line
<varlistentry><term>/proc/tty/ldiscs</term><listitem><para>registered line
disciplines.</para></listitem></varlistentry>
<varlistentry><term>/proc/tty/driver/serial</term><listitem><para>
@ -1576,13 +1613,32 @@ irq 8: 3 rtc irq 15: 83 ide1
<varlistentry><term></term><listitem>
<para> <screen>
# cat /proc/tty/drivers pty_slave /dev/pts 136 0-255
pty:slave pty_master /dev/ptm 128 0-255 pty:master pty_slave /dev/ttyp 3
0-255 pty:slave pty_master /dev/pty 2 0-255 pty:master serial /dev/cua 5
64-67 serial:callout serial /dev/ttyS 4 64-67 serial /dev/tty0 /dev/tty0 4 0
system:vtmaster /dev/ptmx /dev/ptmx 5 2 system /dev/console /dev/console 5 1
system:console /dev/tty /dev/tty 5 0 system:/dev/tty unknown /dev/tty 4 1-63
console
# cat /proc/tty/drivers
serial /dev/cua 5 64-127 serial:callout
serial /dev/ttyS 4 64-127 serial
pty_slave /dev/pts 143 0-255 pty:slave
pty_master /dev/ptm 135 0-255 pty:master
pty_slave /dev/pts 142 0-255 pty:slave
pty_master /dev/ptm 134 0-255 pty:master
pty_slave /dev/pts 141 0-255 pty:slave
pty_master /dev/ptm 133 0-255 pty:master
pty_slave /dev/pts 140 0-255 pty:slave
pty_master /dev/ptm 132 0-255 pty:master
pty_slave /dev/pts 139 0-255 pty:slave
pty_master /dev/ptm 131 0-255 pty:master
pty_slave /dev/pts 138 0-255 pty:slave
pty_master /dev/ptm 130 0-255 pty:master
pty_slave /dev/pts 137 0-255 pty:slave
pty_master /dev/ptm 129 0-255 pty:master
pty_slave /dev/pts 136 0-255 pty:slave
pty_master /dev/ptm 128 0-255 pty:master
pty_slave /dev/ttyp 3 0-255 pty:slave
pty_master /dev/pty 2 0-255 pty:master
/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
/dev/ptmx /dev/ptmx 5 2 system
/dev/console /dev/console 5 1 system:console
/dev/tty /dev/tty 5 0 system:/dev/tty
unknown /dev/vc/%d 4 1-63 console
</screen></para></listitem></varlistentry>
<varlistentry><term></term><listitem><para>Note that while the above files tend to be
@ -1596,13 +1652,13 @@ irq 8: 3 rtc irq 15: 83 ide1
</para></listitem></varlistentry>
<varlistentry><term>/proc/uptime</term><listitem><para> The time the system
<varlistentry><term>/proc/uptime</term><listitem><para>The time the system
has been up.</para></listitem></varlistentry>
<varlistentry><term>/proc/version</term><listitem><para>
The kernel version.</para></listitem></varlistentry>
<varlistentry><term>/proc/video</term><listitem><para> BTTV info of video
<varlistentry><term>/proc/video</term><listitem><para>BTTV info of video
resources.</para></listitem></varlistentry>
</variablelist></para>

13
LDP/guide/docbook/Linux-Filesystem-Hierarchy/sbin.xml
View File

@ -1,17 +1,20 @@
<sect1 id="sbin">
<title>/sbin</title>
<para>Linux discriminates between 'normal' executables and those used for system maintenance or administrative tasks. The latter reside either here or - the less important ones - in /usr/sbin. Locally installed system administration programs should be placed into /usr/local/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. This directory contains all the binaries that are essential to the working of the system. These include system administration as well as maintenance and hardware configuration programs. You may find lilo, fdisk, init, ifconfig, etc here. These are the essential programs that are required by all the users. Another directory that contains system binaries is /usr/sbin. This directory contains other binaries of use to the system administrator. This is where you will find the network daemons for your system along with other binaries that only the system administrator has access to, but which are not required for system maintenance and repair. For obvious security reasons, these directories are never part of normal user's $PATHs, only of roots (PATH is an environment variable that controls the sequence of locations that the sytem will attempt to look in for commands).
</para>
<para>Linux discriminates between 'normal' executables and those used for system maintenance or administrative tasks. The latter reside either here or - the less important ones - in /usr/sbin. Locally installed system administration programs should be placed into /usr/local/sbin. Programs executed after /usr is known to be mounted (when there are no problems) are generally placed into /usr/sbin. This directory contains all the binaries that are essential to the working of the system. These include system administration as well as maintenance and hardware configuration programs. You may find lilo, fdisk, init, ifconfig, etc here. These are the essential programs that are required by all the users. Another directory that contains system binaries is /usr/sbin. This directory contains other binaries of use to the system administrator. This is where you will find the network daemons for your system along with other binaries that only the system administrator has access to, but which are not required for system maintenance and repair. For obvious security reasons, these directories are never part of normal user's $PATHs, only of roots (PATH is an environment variable that controls the sequence of locations that the sytem will attempt to look in for commands).</para>
<para>
FSSTND compliance requires that the following commands, or symbolic links to commands,
are required in /sbin.
</para>
<para><screen>shutdown Command to bring the system down.</screen></para>
<para>
<screen>
shutdown Command to bring the system down.
</screen>
</para>
<para>The following files, or symbolic links to files, must be in /sbin if the corresponding subsystem is installed:
</para>
<para>The following files, or symbolic links to files, must be in /sbin if the corresponding subsystem is installed:</para>
<para>
<screen>

47
LDP/guide/docbook/Linux-Filesystem-Hierarchy/usr.xml
View File

@ -16,9 +16,9 @@ Another large subdirectory structure begins here, containing libraries, executab
This hierarchy is reserved for the X Window System, version 11 release 6, and related files. To simplify matters and make XFree86 more compatible with the X Window System on other systems, the following symbolic links must be present if /usr/X11R6 exists:</para></listitem></varlistentry>
<varlistentry><term></term><listitem><para><screen>
/usr/bin/X11 -> /usr/X11R6/bin
/usr/lib/X11 -> /usr/X11R6/lib/X11
/usr/include/X11 -> /usr/X11R6/include/X11
/usr/bin/X11 -> /usr/X11R6/bin
/usr/lib/X11 -> /usr/X11R6/lib/X11
/usr/include/X11 -> /usr/X11R6/include/X11
</screen></para></listitem></varlistentry>
<varlistentry><term></term><listitem><para>
@ -94,26 +94,40 @@ Manual pages. They are organised into 8 sections, which are explained below.</pa
<varlistentry><term></term><listitem><para>
<screen>
man1: User programs
Manual pages that describe publicly accessible commands are contained in this chapter. Most program documentation that a user will need to use is located here.
Manual pages that describe publicly accessible commands are contained
in this chapter. Most program documentation that a user will need to
use is located here.
man2: System calls
This section describes all of the system calls (requests for the kernel to perform operations).
This section describes all of the system calls (requests for the kernel
to perform operations).
man3: Library functions and subroutines
Section 3 describes program library routines that are not direct calls to kernel services. This and chapter 2 are only really of interest to programmers.
Section 3 describes program library routines that are not direct calls
to kernel services. This and chapter 2 are only really of interest to
programmers.
man4: Special files
Section 4 describes the special files, related driver functions, and networking support available in the system. Typically, this includes the device files found in /dev and the kernel interface to networking protocol support.
Section 4 describes the special files, related driver functions, and
networking support available in the system. Typically, this includes
the device files found in /dev and the kernel interface to networking
protocol support.
man5: File formats
The formats for many data files are documented in the section 5. This includes various include files, program output files, and system files.
The formats for many data files are documented in the section 5. This
includes various include files, program output files, and system files.
man6: Games
This chapter documents games, demos, and generally trivial programs. Different people have various notions about how essential this is.
This chapter documents games, demos, and generally trivial programs.
Different people have various notions about how essential this is.
man7: Miscellaneous Manual pages that are difficult to classify are designated as being section 7. The troff and other text processing macro packages are found here.
man7: Miscellaneous Manual pages that are difficult to classify are
designated as being section 7. The troff and other text processing
macro packages are found here.
man8: System administration Programs used by system administrators for system operation and maintenance are documented here. Some of these programs are also occasionally useful for normal users.
man8: System administration Programs used by system administrators
for system operation and maintenance are documented here. Some of
these programs are also occasionally useful for normal users.
</screen>
</para></listitem></varlistentry>
</variablelist>
@ -130,7 +144,9 @@ RPM/ provides a substructure for building RPMs from SRPMs. Organiztion of this b
<varlistentry><term>/usr/src/RPM/BUILD</term><listitem><para>
Houses RPM binary files that have een built from RPM source files.</para></listitem></varlistentry>
<varlistentry><term>/usr/src/RPM/RPMS/athlon, /usr/src/RPM/RPMS/i386, /usr/src/RPM/RPMS/i486, /usr/src/RPM/RPMS/i586, /usr/src/RPM/RPMS/i686, /usr/src/RPM/RPMS/noarch</term><listitem><para></para></listitem></varlistentry>
<varlistentry><term>/usr/src/RPM/RPMS/athlon, /usr/src/RPM/RPMS/i386, /usr/src/RPM/RPMS/i486, /usr/src/RPM/RPMS/i586, /usr/src/RPM/RPMS/i686, /usr/src/RPM/RPMS/noarch</term><listitem><para>
These directories contain architecture dependant RPM source files.
</para></listitem></varlistentry>
<varlistentry><term>/usr/src/RPM/SOURCES</term><listitem><para>
RPM source files.</para></listitem></varlistentry>
@ -168,15 +184,16 @@ These are the release notes for Linux version 2.4. Read them carefully, as they
<varlistentry><term>/usr/src/linux/REPORTING-BUGS</term><listitem><para>
A suggested procedure for reporting Linux bugs. You aren't obliged to use the bug reporting format, it is provided as a guide to the kind of information that can be useful to developers - no more.</para></listitem></varlistentry>
<varlistentry><term>/usr/src/linux/Rules.make</term><listitem><para></para></listitem></varlistentry>
<varlistentry><term>/usr/src/linux/Rules.make</term><listitem><para>
This file contains rules which are shared between multiple Makefiles.
</para></listitem></varlistentry>
<varlistentry><term>/usr/src/linux/Documentation</term><listitem><para>
Contains documentation that may be necessary in order to re-compile a kernel. However, it also provides quite a lot of information about your Linux system in general as well. For those who wish to seek further information on the contents of this directory you may consult the /usr/src/linux/Documentation/00-INDEX file.</para></listitem></varlistentry>
Contains documentation that may be necessary in order to re-compile a kernel. However, it also provides quite a lot of information about your Linux system in general as well. For those who wish to seek further information on the contents of this directory you may consult the /usr/src/linux/Documentation/00-INDEX file. Further, more detailed documentation may be found in /usr/src/linux/Documentation/Docbook. Of course, the contents of this directory is written in Docbook but may be converted to pdf, ps or html using the make targets of 'pdfdocs', 'psdocs' and 'htmldocs' respectively.</para></listitem></varlistentry>
<varlistentry><term>/usr/tmp</term><listitem><para>
User space temporary files. This directory is not found on modern distributions at all and was most likely created as a consequence of Linux's UNIX heritage.</para></listitem></varlistentry>
</variablelist></para>
</sect1>