mirror of https://github.com/tLDP/LDP
Typos which can be located by the Find command:
hierarchal -> hierarchical symobolic -> symbolic utilites -> utilities equivalencies -> equivalents ramdisc -> ramdisk progamming -> programming wich -> which kB -> KB perfomance -> performance deallocated -> unallocated firewallsblock -> firewalls block trafic -> traffic acknowledgments -> acknowledgements interoperatibility -> interoperability Appletalk.It shows (spaces after period) .../proc/tty.You'll find entries for drivers... (spaces after period) digestable -> digestible sytem -> system (a few places) symbollic -> symbolic workeable -> workable redering -> rendering utlitiy's -> utility's tunnneling -> tunnelling tby -> by ...'xinit' is a configuration method os starting up... #Change "os" to "of". dissallowed -> disallowed specfic -> specific ...see inetd(8) for further informations. #Change "informations" to "information". ...so it is OK to start it early in the bootprocess. #Change "bootprocess" to "boot process". anymore -> any more ctrlaltdel -> ctrl-alt-del spearated -> separated startupfiles -> startup files dialing -> dialling seperate -> separate (a couple of places) utliise -> utilise bookeeping -> bookkeeping ...Three commands can be used to access the contents of this file dump-acct, sa... #Change "dump-acct" to "dump - acct" (put spaces around dash) or "dump: acct". accouting -> accounting userful -> useful Organiztion -> Organization prorgams -> programs woul dhappen -> would happen unlikt -> unlike ...or a violation of the operating systems or hardwares protection mechanisms... #Change "systems" to "system's" and "hardwares" to "hardware's" symolic -> symbolic progams -> programs Unlilke -> Unlike Commentry -> Commentary Progamming -> Programming english -> English vietnamese -> Vietnamese french -> French chinese -> Chinese italian -> Italian buddhist -> Buddhist catholic -> Catholic christian -> Christian Geoff Farrell, gfarrell(at)netspeed(dot)com(dot)au
This commit is contained in:
parent
55adb9e7a5
commit
567cf77fb9
|
@ -21,13 +21,13 @@
|
|||
pondering whether he should complete his musical studies to obtain a
|
||||
diploma so that he can teach. In high school, he was a member of the
|
||||
athletics, basketball, football, cricket and swimming squads. He speaks
|
||||
english predominately but is also able to communicate in vietnamese and
|
||||
french. When younger he also possessed the ability to communicate in
|
||||
chinese and italian.
|
||||
English predominately but is also able to communicate in Vietnamese and
|
||||
French. When younger he also possessed the ability to communicate in
|
||||
Chinese and Italian.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Although brought up as a buddhist and studying at catholic/christian
|
||||
Although brought up as a Buddhist and studying at Catholic/Christian
|
||||
schools all his life as well as studying scripture during his final year of
|
||||
high school he considers himself an atheist.
|
||||
</para>
|
||||
|
@ -50,7 +50,7 @@
|
|||
<para>
|
||||
He has published articles at linux.com, linmagau.org, desktoplinux.com,
|
||||
newsforge.com, linuxtoday.com, linux.org, pclinuxonline.com,
|
||||
tuxreports.com, etc.... and has a keen interest in the latest innovations
|
||||
tuxreports.com, etc.... and has a keen interest in the latest innovations
|
||||
in science and technology.
|
||||
</para>
|
||||
|
||||
|
|
|
@ -76,5 +76,12 @@
|
|||
<para>Emma Jane Hogbin.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Geoff Farrell.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
||||
</appendix>
|
||||
|
|
|
@ -21,13 +21,13 @@
|
|||
pondering whether he should complete his musical studies to obtain a
|
||||
diploma so that he can teach. In high school, he was a member of the
|
||||
athletics, basketball, football, cricket and swimming squads. He speaks
|
||||
english predominately but is also able to communicate in vietnamese and
|
||||
french. When younger he also possessed the ability to communicate in
|
||||
chinese and italian.
|
||||
English predominately but is also able to communicate in Vietnamese and
|
||||
French. When younger he also possessed the ability to communicate in
|
||||
Chinese and Italian.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Although brought up as a buddhist and studying at catholic/christian
|
||||
Although brought up as a Buddhist and studying at Catholic/Christian
|
||||
schools all his life as well as studying scripture during his final year of
|
||||
high school he considers himself an atheist.
|
||||
</para>
|
||||
|
|
|
@ -19,5 +19,11 @@
|
|||
<para>Clyde Forrester.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Geoff Farrell.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</appendix>
|
||||
|
|
|
@ -23,7 +23,7 @@ data structures need to be written to the disk. This process is called <emphasis
|
|||
</para>
|
||||
|
||||
<para>
|
||||
Like UNIX, Linux chooses to have a single hierarchal directory structure. Everything starts from the root directory, represented by /, and then expands into sub-directories instead of having so-called 'drives'. In
|
||||
Like UNIX, Linux chooses to have a single hierarchical directory structure. Everything starts from the root directory, represented by /, and then expands into sub-directories instead of having so-called 'drives'. In
|
||||
the Windows environment, one may put one's files almost anywhere: on C drive, D drive, E drive etc. Such a file system is called a hierarchical structure and is managed by the programs themselves (program directories), not by the operating system. On the other hand, Linux sorts directories descending from the root directory / according to their importance to the boot process.
|
||||
</para>
|
||||
|
||||
|
|
|
@ -117,7 +117,7 @@ MTA
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
Mail Transfer Agents. Alongside the web, mail is the top reason for the popularity of the Internet. E-mail is an inexpensive and fast method of time-shifted messaging which, much like the Web, is actually based around sending and receiving plain text files. The protocol used is called the Simple Mail Transfer Protocol (SMTP). The server prorgams that implement SMTP to move mail from one server to another are called MTAs. Once upon a time users would have to Telnet into an SMTP server and use a command line mail program like 'mutt' or 'pine' to check their mail. Now, GUI based e-mail clients like Mozilla, Kmail and Outlook allow users to check their email off of a local SMTP sever. Additional protocols like POP3 and IMAP4 are used between the SMTP server and desktop mail client to allow clients to manipulate files on, and download from, their local mail server. The programs that implement POP3 and IMAP4 are called Mail Delivery Agents (MDAs). They are generally seperate from MTAs.
|
||||
Mail Transfer Agents. Alongside the web, mail is the top reason for the popularity of the Internet. E-mail is an inexpensive and fast method of time-shifted messaging which, much like the Web, is actually based around sending and receiving plain text files. The protocol used is called the Simple Mail Transfer Protocol (SMTP). The server programs that implement SMTP to move mail from one server to another are called MTAs. Once upon a time users would have to Telnet into an SMTP server and use a command line mail program like 'mutt' or 'pine' to check their mail. Now, GUI based e-mail clients like Mozilla, Kmail and Outlook allow users to check their email off of a local SMTP sever. Additional protocols like POP3 and IMAP4 are used between the SMTP server and desktop mail client to allow clients to manipulate files on, and download from, their local mail server. The programs that implement POP3 and IMAP4 are called Mail Delivery Agents (MDAs). They are generally separate from MTAs.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -150,7 +150,7 @@ PATH
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
The shell looks for commands and programs in a list of file paths stored in the PATH environment variable. An environment variable stores information in a place where other programs and commands can access it. Environment variables store information such as the shell that you are using, your login name, and your current working directory. To see a list of all the environment variables currently defined; type 'set' at the prompt. When you type a command at the shell prompt, the shell will look for that command's program file in each directory listed in the PATH variable, in order. The first program found matching the command you typed will be run. If the command's program file is not in a directory listed in you PATH environment variable, the shell returns a "commands not found" error. By default, the shell does not look in your current working directory or your home directory for commands This is really a security mechanism so that you don't execute programs by accident. What if a malicious user put a harmful program called ls in your home directory? If you typed ls and the shell looked for the fake program in your home directory before the real program in the /bin directory, what do you think woul dhappen? If you thought bad things, you are on the right track. Since your PATH doesn't have the current directory as one of its search locations, programs in your current directory must be called with an absolute path of a relative path specified as './program-name'. To see what directories are part of your PATH enter this command: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
|
||||
The shell looks for commands and programs in a list of file paths stored in the PATH environment variable. An environment variable stores information in a place where other programs and commands can access it. Environment variables store information such as the shell that you are using, your login name, and your current working directory. To see a list of all the environment variables currently defined; type 'set' at the prompt. When you type a command at the shell prompt, the shell will look for that command's program file in each directory listed in the PATH variable, in order. The first program found matching the command you typed will be run. If the command's program file is not in a directory listed in you PATH environment variable, the shell returns a "commands not found" error. By default, the shell does not look in your current working directory or your home directory for commands This is really a security mechanism so that you don't execute programs by accident. What if a malicious user put a harmful program called ls in your home directory? If you typed ls and the shell looked for the fake program in your home directory before the real program in the /bin directory, what do you think would happen? If you thought bad things, you are on the right track. Since your PATH doesn't have the current directory as one of its search locations, programs in your current directory must be called with an absolute path of a relative path specified as './program-name'. To see what directories are part of your PATH enter this command: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -161,7 +161,7 @@ SSH
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
The Secure Shell, or SSH, provides a way of running command line and graphical applications, and transferring files, over an encrypted connection, all that will be seen is junk. It is both a protocol and a suite of small command line applications, which can be used for various functions. SSH replaces the old Telnet application, and can be used for secure remote administration of machines across the Internet. However, it also has other features. SSH increases the ease of running applications remotely by setting up X permissions automatically. If you can log into a machine, it allows you to run a graphical application on it, unlikt Telnet, which requires users to have an understanding of the X authentication mechanisms that are manipulated through the xauth and xhost commands. SSH also has inbuilt compression, which allows your graphic applications to run much faster over the network. SCP (Secure Copy) and SFTP (Secure FTP) allow transfer of files over the remote link, either via SSH's own command line utilities or graphical tools like Gnome's GFTP. Like Telnet, SSH is cross-platform. You can find SSH server and clients for Linux, Unix and all flavours of Windows, BeOS, PalmOS, Java and embedded Oses used in routers.
|
||||
The Secure Shell, or SSH, provides a way of running command line and graphical applications, and transferring files, over an encrypted connection, all that will be seen is junk. It is both a protocol and a suite of small command line applications, which can be used for various functions. SSH replaces the old Telnet application, and can be used for secure remote administration of machines across the Internet. However, it also has other features. SSH increases the ease of running applications remotely by setting up X permissions automatically. If you can log into a machine, it allows you to run a graphical application on it, unlike Telnet, which requires users to have an understanding of the X authentication mechanisms that are manipulated through the xauth and xhost commands. SSH also has inbuilt compression, which allows your graphic applications to run much faster over the network. SCP (Secure Copy) and SFTP (Secure FTP) allow transfer of files over the remote link, either via SSH's own command line utilities or graphical tools like Gnome's GFTP. Like Telnet, SSH is cross-platform. You can find SSH server and clients for Linux, Unix and all flavours of Windows, BeOS, PalmOS, Java and embedded Oses used in routers.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -216,7 +216,7 @@ core
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
A core file is created when a program terminates unexpectedly, due to a bug, or a violation of the operating systems or hardwares protection mechanisms. The operating system kills the program and creates a core file that programmers can use to figure out what went wrong. It contains a detailed description of the state that the program was in when it died. If would like to determine what program a core file came from, use the file command, like this: $ file core That will tell you the name of the program that produced the core dump. You may want to write the maintainer(s) of the program, telling them that their program dumped core. To Enable or Disable Core Dumps you must use the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. This setting affects all programs run from the shell (directly or indirectly), not the whole system. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in /usr/include/linux/sched.h. Refer to definition of INIT_TASK, and look also in /usr/include/linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed. In some distributions this parameter is configurable in the /etc/security/limits.conf file. For more information, refer to the Linux Administrator's Security Guide.
|
||||
A core file is created when a program terminates unexpectedly, due to a bug, or a violation of the operating system's or hardware's protection mechanisms. The operating system kills the program and creates a core file that programmers can use to figure out what went wrong. It contains a detailed description of the state that the program was in when it died. If would like to determine what program a core file came from, use the file command, like this: $ file core That will tell you the name of the program that produced the core dump. You may want to write the maintainer(s) of the program, telling them that their program dumped core. To Enable or Disable Core Dumps you must use the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. This setting affects all programs run from the shell (directly or indirectly), not the whole system. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in /usr/include/linux/sched.h. Refer to definition of INIT_TASK, and look also in /usr/include/linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed. In some distributions this parameter is configurable in the /etc/security/limits.conf file. For more information, refer to the Linux Administrator's Security Guide.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -315,7 +315,7 @@ link
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
A symolic link (alias in MacOS and shortcut under Windows) is a file that points to another file; this is a commonly used tool. A hard-link rarely created by the user, is a filename that points to a block of data that has several other filenames as well.
|
||||
A symbolic link (alias in MacOS and shortcut under Windows) is a file that points to another file; this is a commonly used tool. A hard-link rarely created by the user, is a filename that points to a block of data that has several other filenames as well.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -370,7 +370,7 @@ rpc
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
Remote Procedure Calls. It enables a system to make calls to progams such as NFS across the network transparently, enabling each system to interpret the calls as if they were local. In this case, it would make exported filesystems appear as thought they were local.
|
||||
Remote Procedure Calls. It enables a system to make calls to programs such as NFS across the network transparently, enabling each system to interpret the calls as if they were local. In this case, it would make exported filesystems appear as thought they were local.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
@ -414,7 +414,7 @@ symbolic link or soft link
|
|||
</glossterm>
|
||||
<glossdef>
|
||||
<para>
|
||||
A special filetype, which is a small pointer file, allowing multiple names for the same file. Unlilke hard links, symbolic links can be made for directories and can be made across filesystems. Commands that access the file being pointed to are said to follow the symbolic link. Commands that access the link itself do not follow the symbolic link.
|
||||
A special filetype, which is a small pointer file, allowing multiple names for the same file. Unlike hard links, symbolic links can be made for directories and can be made across filesystems. Commands that access the file being pointed to are said to follow the symbolic link. Commands that access the link itself do not follow the symbolic link.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
|
|
@ -58,7 +58,7 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Lions' Commentry on UNIX 6th Edition with Source Code, John Lions, Peer-to-Peer Communications Incorporated, USA, 1996.</para>
|
||||
<para>Lions' Commentary on UNIX 6th Edition with Source Code, John Lions, Peer-to-Peer Communications Incorporated, USA, 1996.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
@ -70,7 +70,7 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>SAMS Teach Yourself Shell Progamming in 24 Hours, Sriranga Veerararaghavan, SAMS Publishing, USA, 1999.</para>
|
||||
<para>SAMS Teach Yourself Shell Programming in 24 Hours, Sriranga Veerararaghavan, SAMS Publishing, USA, 1999.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
|
@ -18,13 +18,13 @@
|
|||
|
||||
<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
|
||||
distributions it is actually a symbolic link to one of four files
|
||||
/boot/boot-bmp.b, /boot/boot-menu.b, /boot/boot-text.b, /boot/boot-compat.b
|
||||
which allow a user to change the boot-up schema so that it utilises a splash
|
||||
screen, a simple menu, a text based interface or a minimal boot loader to
|
||||
ensure compatibility respectively. In each case re-installation of lilo is
|
||||
necessary in order to complete the changes. To change the actual
|
||||
'boot-logo' you can either use utilites such as fblogo or the more
|
||||
'boot-logo' you can either use utilities such as fblogo or the more
|
||||
refined bootsplash.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/boot/chain.b</term><listitem><para>Used
|
||||
|
|
|
@ -121,7 +121,7 @@ crw-rw-rw- 1 root root 1, 5 Sep 28 18:06 zero
|
|||
</screen>
|
||||
</para>
|
||||
|
||||
<para>Some common devices files as well as their equivalencies under Windows that you may wish to remember are:</para>
|
||||
<para>Some common device files as well as their equivalent counterparts under Windows that you may wish to remember are:</para>
|
||||
|
||||
<para><variablelist>
|
||||
|
||||
|
|
|
@ -11,7 +11,7 @@
|
|||
<para><variablelist><varlistentry><term>/etc/X11/</term><listitem><para>This
|
||||
directory tree contains all the configuration files for the X Window System.
|
||||
Users should note that many of the files located in this directory are
|
||||
actually symbollic links to the /usr/X11R6 directory tree. Thus, the
|
||||
actually symbolic links to the /usr/X11R6 directory tree. Thus, the
|
||||
presence of these files in these locations can not be certain.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/X11/XF86Config,
|
||||
|
@ -22,7 +22,7 @@
|
|||
sufficient knowledge about your system. It would be considered prudent not
|
||||
to attempt to type out a file from beginning to end. Rather, use common
|
||||
configuration utilities such as xf86config, XF86Setup and xf86cfg to create
|
||||
a workeable template. Then, using suitable documentation commence
|
||||
a workable template. Then, using suitable documentation commence
|
||||
optimization through intuition and/or trial and error. Options that can be
|
||||
configured via this file include X modules to be loaded on startup,
|
||||
keyboard, mouse, monitor and graphic chipset type. Often, commercial
|
||||
|
@ -177,7 +177,7 @@ EndSection
|
|||
locations of the various font files for X (note - X will not start if you do
|
||||
not specify a valid font), next is the "Modules" section. It details
|
||||
what modules are to be loaded upon startup. The most well known extensions
|
||||
are probably GLX (required for 3D redering of graphics and games) and
|
||||
are probably GLX (required for 3D rendering of graphics and games) and
|
||||
Xinerama which allows users to expand their desktop over several monitors.
|
||||
Next are the various "Device" sections which describe the type of
|
||||
hardware you have. Improper configuration of these subsections can lead to
|
||||
|
@ -196,7 +196,7 @@ EndSection
|
|||
general your default keyboard mapping comes from your X server setup. If
|
||||
this setup is insufficient and you are unwilling to go through the process
|
||||
of reconfiguration and/or you are not the superuser you'll need to use
|
||||
the xmodmap program. This is the utlitiy's global configuration file.</para></listitem></varlistentry>
|
||||
the xmodmap program. This is the utility's global configuration file.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/X11/xkb/</term><listitem><para>The
|
||||
various symbols, types, geometries of keymaps that the X server supports can
|
||||
|
@ -215,7 +215,7 @@ EndSection
|
|||
load and thus increase overall network latency. A competing project called
|
||||
DXPC (Differential X Protocol Compression) has been found to be more
|
||||
efficient at this task. Studies have shown though that in almost all cases
|
||||
ssh tunnneling of X will produce far better results than through any of
|
||||
ssh tunneling of X will produce far better results than through any of
|
||||
these specialised pieces of software.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/X11/proxymngr/</term><listitem><para>X
|
||||
|
@ -254,7 +254,7 @@ EndSection
|
|||
is the primary configuration file for GDM. Through it, users can specify
|
||||
whether they would like their system to automatically login as a certain
|
||||
user, background startup image and also if they would like to run their
|
||||
machine as somewhat of a terminal server tby using the XDMCP protocol.</para></listitem></varlistentry>
|
||||
machine as somewhat of a terminal server by using the XDMCP protocol.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/X11/fonts</term><listitem><para>Home
|
||||
of xfs fonts.</para></listitem></varlistentry>
|
||||
|
@ -310,7 +310,7 @@ cache-balance = 70
|
|||
of configuration files for twm. The original Tabbed Window Manager.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/X11/xinit/</term><listitem><para>xinit
|
||||
configuration files. 'xinit' is a configuration method os starting
|
||||
configuration files. 'xinit' is a configuration method of starting
|
||||
up an X session that is designed to used as part of a script. Normally, this
|
||||
is used at larger sites as part of a tailored login process.</para></listitem></varlistentry>
|
||||
|
||||
|
@ -643,7 +643,7 @@ language dictionary databases.
|
|||
of ftp users that need to be chrooted.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/ftpuser</term><listitem><para>List
|
||||
of dissallowed ftp users.</para></listitem></varlistentry>
|
||||
of disallowed ftp users.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/gateways</term><listitem><para>Lists
|
||||
gateways for 'routed'.</para></listitem></varlistentry>
|
||||
|
@ -697,7 +697,7 @@ language dictionary databases.
|
|||
|
||||
<varlistentry><term>/etc/hosts.allow</term><listitem><para>Part
|
||||
of the tcp-wrappers system to control access to your machine's services.
|
||||
It lists hosts that are allowed to access the system and specfic daemons.</para>
|
||||
It lists hosts that are allowed to access the system and specific daemons.</para>
|
||||
<para><screen>
|
||||
# /etc/hosts.allow: list of hosts that are allowed to access the
|
||||
# system.
|
||||
|
@ -837,7 +837,7 @@ language dictionary databases.
|
|||
/etc/xinet.conf for further details.</para>
|
||||
|
||||
<para><screen>
|
||||
# /etc/inetd.conf: see inetd(8) for further informations.
|
||||
# /etc/inetd.conf: see inetd(8) for further information.
|
||||
#
|
||||
# Internet server configuration database
|
||||
#
|
||||
|
@ -925,7 +925,7 @@ Order of scripts run in /etc/rc?.d
|
|||
state are to be run. The rcS.d directory is NOT meant to replace rc.local.
|
||||
One should not start daemons in this runlevel unless absolutely
|
||||
necessary. Eg, NFS might need the portmapper, so it is OK to start it
|
||||
early in the bootprocess. But this is not the time to start the
|
||||
early in the boot process. But this is not the time to start the
|
||||
squid proxy server.
|
||||
|
||||
2. Going multiuser.
|
||||
|
@ -987,7 +987,7 @@ Order of scripts run in /etc/rc?.d
|
|||
|
||||
Then the /etc/rc6.d/SXXxxxx scripts will be executed alphabetically
|
||||
with "stop" as the first argument as well. The reason is that there
|
||||
is nothing to start anymore at this point - all scripts that are
|
||||
is nothing to start any more at this point - all scripts that are
|
||||
run are meant to bring the system down.
|
||||
|
||||
In the future, the /etc/rc6.d/SXXxxxx scripts MIGHT be moved to
|
||||
|
@ -1092,7 +1092,7 @@ Order of scripts run in /etc/rc?.d
|
|||
The appropriate getty is put on the line until the first call is received.
|
||||
When the caller terminates the connection, the getty drops because, by
|
||||
definition, on demand will not respawn. The other two letters, S and Q, are
|
||||
special. S brings you sytem to maintenance mode and is the same as changing
|
||||
special. S brings you system to maintenance mode and is the same as changing
|
||||
state to runlevel 1. The Q is used to tell init to reread inittab. The
|
||||
/etc/inittab file can be changed as often as required, but will only be read
|
||||
under certain circumstances: -One of its processes dies (do you need to
|
||||
|
@ -1169,7 +1169,7 @@ Order of scripts run in /etc/rc?.d
|
|||
|
||||
<varlistentry><term></term><listitem>
|
||||
<para>/etc/ld.so.conf is a file
|
||||
containing a list of colon, space, tab, newline, or comma spearated
|
||||
containing a list of colon, space, tab, newline, or comma separated
|
||||
directories in which to search for libraries. /etc/ld.so.cache containing an
|
||||
ordered list of libraries found in the directories specified in
|
||||
/etc/ld.so.conf. This file is not in human readable format, and is not
|
||||
|
@ -1401,7 +1401,7 @@ Order of scripts run in /etc/rc?.d
|
|||
menu tree, will supply a menu-method script in /etc/menu-methods/. This
|
||||
menu-method then knows how to generate the startup-file for that window
|
||||
manager. To facilitate this task for the window-manager maintainers, menu
|
||||
provides a install-menu program. This program can generate the startupfiles
|
||||
provides a install-menu program. This program can generate the startup files
|
||||
for just about every window manager.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/mgetty+sendfax</term><listitem><para>Configuration
|
||||
|
@ -1421,8 +1421,8 @@ Order of scripts run in /etc/rc?.d
|
|||
<varlistentry><term>/etc/minicom</term><listitem><para>'minicom'
|
||||
configuration files. 'minicom' is a communication program which
|
||||
somewhat resembles the shareware program TELIX but is free with source code
|
||||
and runs under most unices. Features include dialing directory with
|
||||
auto-redial, support for UUCP-style lock files on serial devices, a seperate
|
||||
and runs under most unices. Features include dialling directory with
|
||||
auto-redial, support for UUCP-style lock files on serial devices, a separate
|
||||
script language interpreter, capture to file, multiple users with individual
|
||||
configurations, and more.</para></listitem></varlistentry>
|
||||
|
||||
|
@ -1613,7 +1613,7 @@ Order of scripts run in /etc/rc?.d
|
|||
of networks that the system is currently located on. For example,
|
||||
192.168.0.0.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/nsswitch.conf</term><listitem><para>Sytem
|
||||
<varlistentry><term>/etc/nsswitch.conf</term><listitem><para>System
|
||||
Database/Name Service Switch configuration file.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/oss.conf</term><listitem><para>OSS
|
||||
|
@ -1890,7 +1890,7 @@ dummy:x:1001:1001:,,,:/home/dummy:/bin/bash
|
|||
hardware states via motherboard sensor chips. Useful statistics such as core
|
||||
voltages, CPU temperature can be determined through third party utilities
|
||||
that make user of these libraries such as 'gkrellm'. If you do not
|
||||
wish to install these packages you may also utliise the /proc filesystem
|
||||
wish to install these packages you may also utilise the /proc filesystem
|
||||
real-time nature.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/etc/sudoers</term><listitem><para>Sudoers
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
<title>/lib</title>
|
||||
|
||||
<para>
|
||||
The /lib directory contains kernel modules and those shared library images (the C progamming code library) needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin. Libraries are readily identifiable through their filename extension of *.so. Windows equivalent to a shared library would be a DLL (dynamically linked library) file. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/'kernel-version'. To ensure proper module compilation you should ensure that /lib/modules/'kernel-version'/kernel/build points to /usr/src/'kernel-version' or ensure that the Makefile knows where the kernel source itself are located.
|
||||
The /lib directory contains kernel modules and those shared library images (the C programming code library) needed to boot the system and run the commands in the root filesystem, ie. by binaries in /bin and /sbin. Libraries are readily identifiable through their filename extension of *.so. Windows equivalent to a shared library would be a DLL (dynamically linked library) file. They are essential for basic system functionality. Kernel modules (drivers) are in the subdirectory /lib/modules/'kernel-version'. To ensure proper module compilation you should ensure that /lib/modules/'kernel-version'/kernel/build points to /usr/src/'kernel-version' or ensure that the Makefile knows where the kernel source itself are located.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
|
@ -129,7 +129,7 @@ lrwxrwxrwx 1 root root 0 Jan 19 15:02 root -> /
|
|||
|
||||
<varlistentry><term>/proc/PID/cmdline</term><listitem><para>Command
|
||||
line arguments.</para></listitem></varlistentry><varlistentry><term>/proc/PID/cpu</term><listitem><para>Current
|
||||
and last cpu in wich it was executed.</para></listitem></varlistentry><varlistentry><term>/proc/PID/cwd</term><listitem><para>Link
|
||||
and last cpu in which it was executed.</para></listitem></varlistentry><varlistentry><term>/proc/PID/cwd</term><listitem><para>Link
|
||||
to the current working directory.</para></listitem></varlistentry><varlistentry><term>/proc/PID/environ</term><listitem><para>Values
|
||||
of environment variables.</para></listitem></varlistentry><varlistentry><term>/proc/PID/exe</term><listitem><para>Link
|
||||
to the executable of this process.</para></listitem></varlistentry><varlistentry><term>/proc/PID/fd</term><listitem><para>Directory,
|
||||
|
@ -243,7 +243,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
|
||||
<varlistentry><term>/proc/cpuinfo</term><listitem><para>
|
||||
Information about the processor, such as its type, make, model, and
|
||||
perfomance.</para></listitem></varlistentry>
|
||||
performance.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/proc/devices</term><listitem><para>
|
||||
List of device drivers configured into the currently running kernel (block
|
||||
|
@ -405,7 +405,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
</screen>
|
||||
</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term></term><listitem><para>It's a bitmask, in which you can specify wich CPUs can handle
|
||||
<varlistentry><term></term><listitem><para>It's a bitmask, in which you can specify which CPUs can handle
|
||||
the IRQ, you can set it by doing:</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term></term><listitem><para><screen># echo 1 > /proc/irq/prof_cpu_mask</screen></para></listitem></varlistentry>
|
||||
|
@ -1159,16 +1159,16 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
<varlistentry><term>/proc/sys/net/core</term><listitem><para>
|
||||
Network core options</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>rmem_default</term><listitem><para> The default setting
|
||||
<varlistentry><term>rmem_default</term><listitem><para>The default setting
|
||||
of the socket receive buffer in bytes.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>rmem_max</term><listitem><para> The maximum receive
|
||||
<varlistentry><term>rmem_max</term><listitem><para>The maximum receive
|
||||
socket buffer size in bytes.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>wmem_default</term><listitem><para> The default setting
|
||||
<varlistentry><term>wmem_default</term><listitem><para>The default setting
|
||||
(in bytes) of the socket send buffer.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>wmem_max</term><listitem><para> The maximum send socket
|
||||
<varlistentry><term>wmem_max</term><listitem><para>The maximum send socket
|
||||
buffer size in bytes.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>message_burst and message_cost</term><listitem><para>
|
||||
|
@ -1183,7 +1183,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
Maximum number of packets, queued on the INPUT side, when the interface
|
||||
receives packets faster than kernel can process them.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>optmem_max</term><listitem><para> Maximum ancillary
|
||||
<varlistentry><term>optmem_max</term><listitem><para>Maximum ancillary
|
||||
buffer size allowed per socket. Ancillary data is a sequence of struct
|
||||
cmsghdr structures with appended data.</para></listitem></varlistentry>
|
||||
|
||||
|
@ -1209,7 +1209,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry><term>/proc/sys/net/ipv4</term><listitem><para> IPV4 settings.
|
||||
<varlistentry><term>/proc/sys/net/ipv4</term><listitem><para>IPV4 settings.
|
||||
IP version 4 is still the most used protocol in Unix networking. It will be
|
||||
replaced by IP version 6 in the next couple of years, but for the moment
|
||||
it's the de facto standard for the internet and is used in most
|
||||
|
@ -1227,7 +1227,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry><term>icmp_echo_ignore_all and icmp_echo_ignore_broadcasts</term><listitem><para> Turn on (1) or off (0), if the kernel should ignore all ICMP ECHO requests, or just those to
|
||||
<varlistentry><term>icmp_echo_ignore_all and icmp_echo_ignore_broadcasts</term><listitem><para>Turn on (1) or off (0), if the kernel should ignore all ICMP ECHO requests, or just those to
|
||||
broadcast and multicast addresses.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term></term><listitem><para>Please note that if you accept ICMP echo requests with a
|
||||
|
@ -1254,7 +1254,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
the number one if the host received its IP configuration by RARP, BOOTP,
|
||||
DHCP or a similar mechanism. Otherwise it is zero.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>ip_default_ttl</term><listitem><para> TTL (Time To Live)
|
||||
<varlistentry><term>ip_default_ttl</term><listitem><para>TTL (Time To Live)
|
||||
for IPv4 interfaces. This is simply the maximum number of hops a packet may
|
||||
travel.</para></listitem></varlistentry>
|
||||
|
||||
|
@ -1262,12 +1262,12 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
Enable dynamic socket address rewriting on interface address change. This is
|
||||
useful for dialup interface with changing IP addresses.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>ip_forward</term><listitem><para> Enable or disable
|
||||
<varlistentry><term>ip_forward</term><listitem><para>Enable or disable
|
||||
forwarding of IP packages between interfaces. Changing this value resets all
|
||||
other parameters to their default values. They differ if the kernel is
|
||||
configured as host or router.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>ip_local_port_range</term><listitem><para> Range of
|
||||
<varlistentry><term>ip_local_port_range</term><listitem><para>Range of
|
||||
ports used by TCP and UDP to choose the local port. Contains two numbers,
|
||||
the first number is the lowest port, the second number the highest local
|
||||
port. Default is 1024-4999. Should be changed to 32768-61000 for high-usage
|
||||
|
@ -1305,69 +1305,69 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
<varlistentry><term>tcp_ecn</term><listitem><para>
|
||||
This file controls the use of the ECN bit in the IPv4 headers, this is a new
|
||||
feature about Explicit Congestion Notification, but some routers and
|
||||
firewallsblock trafic that has this bit set, so it could be necessary to
|
||||
firewalls block traffic that has this bit set, so it could be necessary to
|
||||
echo 0 to /proc/sys/net/ipv4/tcp_ecn, if you want to talk to this sites. For
|
||||
more info you could read RFC2481.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_retrans_collapse</term><listitem><para> Bug-to-bug
|
||||
<varlistentry><term>tcp_retrans_collapse</term><listitem><para>Bug-to-bug
|
||||
compatibility with some broken printers. On retransmit, try to send larger
|
||||
packets to work around bugs in certain TCP stacks. Can be turned off by
|
||||
setting it to zero.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_keepalive_probes</term><listitem><para> Number of
|
||||
<varlistentry><term>tcp_keepalive_probes</term><listitem><para>Number of
|
||||
keep alive probes TCP sends out, until it decides that the connection is
|
||||
broken.</para></listitem></varlistentry> <varlistentry><term>tcp_keepalive_time</term><listitem><para>
|
||||
How often TCP sends out keep alive messages, when keep alive is enabled. The
|
||||
default is 2 hours.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_syn_retries</term><listitem><para> Number of times
|
||||
<varlistentry><term>tcp_syn_retries</term><listitem><para>Number of times
|
||||
initial SYNs for a TCP connection attempt will be retransmitted. Should not
|
||||
be higher than 255. This is only the timeout for outgoing connections, for
|
||||
incoming connections the number of retransmits is defined by tcp_retries1.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_sack</term><listitem><para> Enable select
|
||||
<varlistentry><term>tcp_sack</term><listitem><para>Enable select
|
||||
acknowledgments after RFC2018.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_timestamps</term><listitem><para> Enable timestamps
|
||||
<varlistentry><term>tcp_timestamps</term><listitem><para>Enable timestamps
|
||||
as defined in RFC1323.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_stdurg</term><listitem><para> Enable the strict
|
||||
<varlistentry><term>tcp_stdurg</term><listitem><para>Enable the strict
|
||||
RFC793 interpretation of the TCP urgent pointer field. The default is to use
|
||||
the BSD compatible interpretation of the urgent pointer pointing to the
|
||||
first byte after the urgent data. The RFC793 interpretation is to have it
|
||||
point to the last byte of urgent data. Enabling this option may lead to
|
||||
interoperatibility problems. Disabled by default.</para></listitem></varlistentry>
|
||||
interoperability problems. Disabled by default.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_syncookies</term><listitem><para> Only valid when
|
||||
<varlistentry><term>tcp_syncookies</term><listitem><para>Only valid when
|
||||
the kernel was compiled with CONFIG_SYNCOOKIES. Send out syncookies when the
|
||||
syn backlog queue of a socket overflows. This is to ward off the common
|
||||
'syn flood attack'. Disabled by default. Note that the concept of a
|
||||
socket backlog is abandoned. This means the peer may not receive reliable
|
||||
error messages from an over loaded server with syncookies enabled.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_window_scaling</term><listitem><para> Enable window
|
||||
<varlistentry><term>tcp_window_scaling</term><listitem><para>Enable window
|
||||
scaling as defined in RFC1323.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_fin_timeout</term><listitem><para> The length of
|
||||
<varlistentry><term>tcp_fin_timeout</term><listitem><para>The length of
|
||||
time in seconds it takes to receive a final FIN before the socket is always
|
||||
closed. This is strictly a violation of the TCP specification, but required
|
||||
to prevent denial-of-service attacks.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_max_ka_probes</term><listitem><para> Indicates how
|
||||
<varlistentry><term>tcp_max_ka_probes</term><listitem><para>Indicates how
|
||||
many keep alive probes are sent per slow timer run. Should not be set too
|
||||
high to prevent bursts.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_max_syn_backlog</term><listitem><para> Length of the
|
||||
<varlistentry><term>tcp_max_syn_backlog</term><listitem><para>Length of the
|
||||
per socket backlog queue. Since Linux 2.2 the backlog specified in listen(2)
|
||||
only specifies the length of the backlog queue of already established
|
||||
sockets. When more connection requests arrive Linux starts to drop packets.
|
||||
When syncookies are enabled the packets are still answered and the maximum
|
||||
queue is effectively ignored.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_retries1</term><listitem><para> Defines how often an
|
||||
<varlistentry><term>tcp_retries1</term><listitem><para>Defines how often an
|
||||
answer to a TCP connection request is retransmitted before giving up.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>tcp_retries2</term><listitem><para> Defines how often a
|
||||
<varlistentry><term>tcp_retries2</term><listitem><para>Defines how often a
|
||||
TCP packet is retransmitted before giving up.</para></listitem></varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
@ -1443,10 +1443,10 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
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
|
||||
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
|
||||
<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>
|
||||
|
@ -1507,10 +1507,10 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
<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
|
||||
<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
|
||||
<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
|
||||
machine). When ucast_solicit is greater than 0 it first tries to send an ARP
|
||||
|
@ -1549,7 +1549,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
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
|
||||
the interfaces configured for appletalk.It shows the name of the interface,
|
||||
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>
|
||||
|
||||
|
@ -1591,9 +1591,9 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
<varlistentry><term>/proc/sysvipc</term><listitem><para>Info of SysVIPC
|
||||
Resources (msg, sem, shm) (2.4)</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/proc/tty</term><listitem><para> Information about the
|
||||
<varlistentry><term>/proc/tty</term><listitem><para>Information about the
|
||||
available and actually used tty's can be found in the directory
|
||||
/proc/tty.You'll find entries for drivers and line disciplines in this
|
||||
/proc/tty. You'll find entries for drivers and line disciplines in this
|
||||
directory.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/proc/tty/drivers</term><listitem><para>
|
||||
|
@ -1643,7 +1643,7 @@ irq 8: 3 rtc irq 15: 83 ide1
|
|||
|
||||
<varlistentry><term></term><listitem><para>Note that while the above files tend to be
|
||||
easily readable text files, they can sometimes be formatted in a way that is
|
||||
not easily digestable. There are many commands that do little more than read
|
||||
not easily digestible. There are many commands that do little more than read
|
||||
the above files and format them for easier understanding. For example, the
|
||||
free program reads /proc/meminfo and converts the amounts given in bytes to
|
||||
kilobytes (and adds a little more information, as well). </para></listitem></varlistentry>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<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 system will attempt to look in for commands).</para>
|
||||
|
||||
<para>
|
||||
FSSTND compliance requires that the following commands, or symbolic links to commands,
|
||||
|
|
|
@ -81,7 +81,7 @@ This directory contains programs for administering a system, meant to be run by
|
|||
This directory contains 'shareable', architecture-independent files (docs, icons, fonts etc). Note, however, that '/usr/share' is generally not intended to be shared by different operating systems or by different releases of the same operating system. Any program or package which contains or requires data that doesn't need to be modified should store that data in '/usr/share' (or '/usr/local/share', if installed locally). It is recommended that a subdirectory be used in /usr/share for this purpose."</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/usr/share/doc</term><listitem><para>
|
||||
Location of package specific documentation files. These directories often contain userful information that might not be in the man pages. They may also contain templates and configuration files for certain utilities making configuration that much easier.</para></listitem></varlistentry>
|
||||
Location of package specific documentation files. These directories often contain useful information that might not be in the man pages. They may also contain templates and configuration files for certain utilities making configuration that much easier.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/usr/share/info</term><listitem><para>
|
||||
Location of 'info' pages. This style of documentation seems to be largely ignored now. Manual pages are in far greater favour.</para></listitem></varlistentry>
|
||||
|
@ -138,7 +138,7 @@ these programs are also occasionally useful for normal users.
|
|||
The 'linux' sub-directory holds the Linux kernel sources, header-files and documentation.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/usr/src/RPM</term><listitem><para>
|
||||
RPM provides a substructure for building RPMs from SRPMs. Organiztion of this branch is fairly logical with packages being organised according to a package's architecture.</para></listitem></varlistentry>
|
||||
RPM provides a substructure for building RPMs from SRPMs. Organisation of this branch is fairly logical with packages being organised according to a package's architecture.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/usr/src/RPM/BUILD</term><listitem><para>
|
||||
A temporary store for RPM binary files that are being built from source code.</para></listitem></varlistentry>
|
||||
|
|
|
@ -146,9 +146,9 @@
|
|||
logs.</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/var/log/pacct</term><listitem><para>Process
|
||||
accounting is the bookeeping of process activity. The raw data of process
|
||||
accounting is the bookkeeping of process activity. The raw data of process
|
||||
activity is maintained here. Three commands can be used to access the
|
||||
contents of this file dump-acct, sa (summary of process accouting) and
|
||||
contents of this file dump-acct, sa (summary of process accounting) and
|
||||
lastcomm (list the commands executed on the system).</para></listitem></varlistentry>
|
||||
|
||||
<varlistentry><term>/var/log/utmp</term><listitem><para>Active
|
||||
|
|
Loading…
Reference in New Issue