Context Navigation

-              r8ad7980
+              rf67f5cf
 <indexterm zone="ch-scripts-bootscripts cleanfs-bootscripts"><primary sortas="d-cleanfs">cleanfs</primary></indexterm>
 <para>removes files that shouldn't be
 preserved between reboots, such as those in <filename>/var/run/</filename> and
 <filename>/var/lock/</filename>. It re-creates <filename>/var/run/utmp</filename>
+preserved between reboots, such as those in <filename class="directory">/var/run/</filename> and
+<filename class="directory">/var/lock/</filename>. It re-creates <filename>/var/run/utmp</filename>
 and removes the possibly present <filename>/etc/nologin</filename>,
 <filename>/fastboot</filename> and <filename>/forcefsck</filename> files.</para>
 …
 <listitem>
 <indexterm zone="ch-scripts-bootscripts mountkernfs-bootscripts"><primary sortas="d-mountkernfs">mountkernfs</primary></indexterm>
 <para>is used to mount kernel-provided file systems, such as /proc.</para>
+<para>is used to mount kernel-provided file systems, such as <systemitem class="filesystem">proc</systemitem>.</para>
 </listitem>
 </varlistentry>

chapter07/console.xml

-              r8ad7980
+              rf67f5cf
 configuration file with the following command:</para>
 <screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"</userinput>
 KEYMAP="<emphasis>arguments for loadkeys</emphasis>"
 FONT="<emphasis>arguments for setfont</emphasis>"
 <userinput>EOF</userinput></screen>
+<screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"
+KEYMAP="<replaceable>[arguments for loadkeys]</replaceable>"
+FONT="<replaceable>[arguments for setfont]</replaceable>"
+EOF</userinput></screen>
 <para>E.g., for Spanish users who also want to use the Euro character
 …
 the following settings are correct:</para>
 <screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"</userinput>
+<screen><userinput>cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"
 KEYMAP="es euro"
 FONT="lat9-16 -u iso01"
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <note><para>The FONT line above is correct only for the ISO-8859-15
 character set. If you prefer ISO-8859-1 and therefore use a pound sign
 instead of Euro, the correct FONT line is:</para>
 <screen><userinput>FONT="lat1-16"</userinput></screen></note>
 …
 <para>In some keymaps, the Backspace and Delete keys send characters
 different form ones in the default keymap built into the kernel.
 This confuses some applications, e.g. <application>Emacs</application>
+This confuses some applications, e.g., <application>Emacs</application>
 displays its help (instead of erasing the character before the cursor)
 when you press Backspace. To check if your keymap is affected (this works
 only for i386 keymaps):</para>
 <screen><userinput>zgrep '\W14\W' /path/to/your/keymap</userinput></screen>
+<screen><userinput>zgrep '\W14\W' <replaceable>[/path/to/your/keymap]</replaceable></userinput></screen>
 <para>If you see that keycode 14 is Backspace and not Delete,
 create the following keymap snippet to fix this issue:</para>
 <screen><userinput>mkdir -p /etc/kbd &amp; &amp; cat &gt;/etc/kbd/bs-sends-del &lt;&lt;"EOF"</userinput>
+<screen><userinput>mkdir -p /etc/kbd &amp; &amp; cat &gt;/etc/kbd/bs-sends-del &lt;&lt;"EOF"
                 keycode 14 =    Delete  Delete          Delete  Delete
         alt     keycode 14 =    Meta_Delete
 …
 control alt     keycode 111 =   Boot
 altgr   control alt keycode 111 = Boot
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>Then tell the <command>console</command> script to load this snippet
 after the main keymap:</para>
 <screen><userinput>cat &gt;&gt;/etc/sysconfig/console &lt;&lt;"EOF"</userinput>
+<screen><userinput>cat &gt;&gt;/etc/sysconfig/console &lt;&lt;"EOF"
 KEYMAP_CORRECTION="/etc/kbd/bs-sends-del"
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>If you decided to

chapter07/hostname.xml

-              r8ad7980
+              rf67f5cf
 <para>Part of the localnet script is setting up the system's hostname. This
 needs to be configured in the /etc/sysconfig/network.</para>
+needs to be configured in the <filename>/etc/sysconfig/network</filename>.</para>
 <para>Create the /etc/sysconfig/network file and enter a hostname by
+<para>Create the <filename>/etc/sysconfig/network</filename> file and enter a hostname by
 running:</para>
 <screen><userinput>echo "HOSTNAME=lfs" &gt; /etc/sysconfig/network</userinput></screen>
+<screen><userinput>echo "HOSTNAME=<replaceable>[lfs]</replaceable>" &gt; /etc/sysconfig/network</userinput></screen>
 <para><quote>lfs</quote> needs to be replaced with the name the computer is
+<para><replaceable>[lfs]</replaceable> needs to be replaced with the name the computer is
 to be called. You should not enter the FQDN (Fully Qualified Domain
 Name) here. That information will be put in the

chapter07/hosts.xml

-              r8ad7980
+              rf67f5cf
 <para>If a network card is to be configured, you have to decide on the
 IP-address, FQDN and possible aliases for use in the /etc/hosts file. The
+IP-address, FQDN and possible aliases for use in the <filename>/etc/hosts</filename> file. The
 syntax is:</para>
 <screen>&lt;IP address&gt; myhost.example.org aliases</screen>
+<para>Unless your computer is to be visible to the Internet (e.g. you have a registered domain and a valid block of assigned IP addresses - most of us don't have this)you should make sure that the IP-address is in the private network
+<para>Unless your computer is to be visible to the Internet (e.g., you have a
+registered domain and a valid block of assigned IP addresses - most of us don't
+have this) you should make sure that the IP-address is in the private network
 IP-address range. Valid ranges are:</para>
 …
 <para>A valid IP address could be 192.168.1.1. A valid FQDN for this IP could
+be www.linuxfromscratch.org (not recommended as this is a valid registered domain address and could cause your domain name server problems).</para>
+be www.linuxfromscratch.org (not recommended as this is a valid registered domain
+address and could cause your domain name server problems).</para>
 <para>If you aren't going to use a network card, you still need to
 …
 <filename>/etc/hosts</filename> file by running:</para>
 <screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 # Begin /etc/hosts (no network card version)
 .0.0.1 &lt;value of HOSTNAME&gt;.example.org &lt;value of HOSTNAME&gt; localhost
+.0.0.1 <replaceable>[&lt;value of HOSTNAME&gt;.example.org]</replaceable> <replaceable>[value of HOSTNAME]</replaceable> localhost
 # End /etc/hosts (no network card version)
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>If a network card is to be configured, create the
 <filename>/etc/hosts</filename> file by running:</para>
 <screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 # Begin /etc/hosts (network card version)
 .0.0.1 localhost
+.168.1.1 &lt;value of HOSTNAME&gt;.example.org &lt;value of HOSTNAME&gt;
+<replaceable>[192.168.1.1]</replaceable> <replaceable>[&lt;value of HOSTNAME&gt;.example.org]</replaceable> <replaceable>[value of HOSTNAME]</replaceable>
 # End /etc/hosts (network card version)
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>Of course, the 192.168.1.1 and &lt;value of HOSTNAME&gt;.example.org
+<para>Of course, the <replaceable>[192.168.1.1]</replaceable> and <replaceable>[&lt;value of HOSTNAME&gt;.example.org]</replaceable>
 have to be changed to your liking (or requirements if assigned an IP-address
 by a network/system administrator and this machine is planned to be connected

chapter07/inputrc.xml

-              r8ad7980
+              rf67f5cf
 <?dbhtml filename="inputrc.html"?>
+<para><filename>Inputrc</filename> deals with the mapping of the keyboard for
+<indexterm zone="ch-scripts-inputrc"><primary sortas="e-/etc/inputrc">/etc/inputrc</primary></indexterm>
+<para><filename>/etc/inputrc</filename> deals with the mapping of the keyboard for
 certain situations.  This file is the start-up file used by
 <application>readline</application> - the input related library used by
 …
 want your system to use both, or don't want <emphasis>global</emphasis>
 keyboard handling, it is a good idea to place a default
 <filename>.inputrc</filename> into the <filename>/etc/skel</filename>
+<filename>.inputrc</filename> into the <filename class="directory">/etc/skel</filename>
 directory for use with new users.</para>
 …
 <para>If you will create an <filename>.inputrc</filename> in
 <filename>/etc/skel</filename> using the command below, change the
+<filename class="directory">/etc/skel</filename> using the command below, change the
 command's output to <filename>/etc/skel/.inputrc</filename> and be
 sure to check/set permissions afterward. Then you can just copy that
 file to <filename>/etc/inputrc</filename> and the home directory
 of any user already existing in the system, including root, that needs
 a private version of the file.  Be sure to use the <option>-p</option> parameter
+a private version of the file.  Be sure to use the <parameter>-p</parameter> parameter
 of <command>cp</command> to maintain permissions and be sure to change owner and group
 appropriately.
 </para>
 <screen><userinput>cat &gt; /etc/inputrc &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/inputrc &lt;&lt; "EOF"
 # Begin /etc/inputrc
 …
 # End /etc/inputrc
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 </sect1>

chapter07/network.xml

-              r8ad7980
+              rf67f5cf
 <para>If you don't have any network cards, you are most likely not going to
 create any configuration files relating to network cards. If that is the
 case, you must remove the <filename>network</filename> symlinks from all the
+case, you must remove the <filename class="symlink">network</filename> symlinks from all the
 run-level directories
 (<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
 …
 <para>Which interfaces are brought up and down by the network script depends on
 the files in the /etc/sysconfig/network-devices directory. This
 directory should contain files in the form of ifconfig.xyz, where xyz is a
+the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
+directory should contain files in the form of <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
 network interface name (such as eth0 or eth0:1)</para>
 <para>If you decide to rename or move this /etc/sysconfig/network-devices
 directory, make sure you update the /etc/sysconfig/rc file as well and
 update the network_devices by providing it with the new path.</para>
+<para>If you decide to rename or move this <filename class="directory">/etc/sysconfig/network-devices</filename>
+directory, make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
+update the <quote>network_devices</quote> by providing it with the new path.</para>
 <para>Now, new files are created in that directory.
 The following command creates a sample ifconfig.eth0 file:</para>
+The following command creates a sample <filename>ifconfig.eth0</filename> file:</para>
 <screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"
 ONBOOT=yes
 SERVICE=static
 …
 NETMASK=255.255.255.0
 BROADCAST=192.168.1.255
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>Of course, the values of those variables have to be changed
 in every file to match the proper setup. If the ONBOOT variable is set
 to yes, the network script will bring up the equivalent NIC (Network Interface Card)
+to <quote>yes</quote>, the network script will bring up the equivalent NIC (Network Interface Card)
  during the booting of the system.
 If set to anything but yes, the equivalent NIC will be ignored by the network script
+If set to anything but <quote>yes</quote>, the equivalent NIC will be ignored by the network script
 and not brought up.</para>
 <para>The SERVICE entry defines the method of obtaining the IP address.
 The LFS bootscripts have a modular IP assignment format, and by creating
 additional files in /etc/sysconfig/network-devices/services, you can allow
+additional files in <filename class="directory">/etc/sysconfig/network-devices/services</filename>, you can allow
 other IP assignment methods.  This would commonly be used if you need DHCP,
 which is addressed in the BLFS book.</para>
 …
 </sect2>
 <sect2>
+<sect2 id="resolv.conf">
 <title>Creating the /etc/resolv.conf file</title>
+<indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
 <para>If you're going to be connected to the Internet then most likely you'll
 …
 following:</para>
 <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
 # Begin /etc/resolv.conf
 nameserver &lt;IP address of your nameserver&gt;
+nameserver <replaceable>[IP address of your nameserver]</replaceable>
 # End /etc/resolv.conf
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>Of course, replace &lt;IP address of your nameserver&gt; with the IP
+<para>Of course, replace <replaceable>[IP address of your nameserver]</replaceable> with the IP
 address of the DNS most appropriate for your setup. There will often be
 more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>

chapter07/profile.xml

-              r8ad7980
+              rf67f5cf
 <?dbhtml filename="profile.html"?>
+<para>The shell program <filename>/bin/bash</filename> (hereafter
+referred to as just "the shell") uses a collection of startup files to
+<indexterm zone="ch-scripts-profile"><primary sortas="e-/etc/profile">/etc/profile</primary></indexterm>
+<para>The shell program <command>/bin/bash</command> (hereafter
+referred to as just <quote>the shell</quote>) uses a collection of startup files to
 help create an environment to run in.  Each file has a specific use and
 may affect login and interactive environments differently.  The files in
 …
 <para>An interactive login shell is started after a successful login, using
 <filename>/bin/login</filename>, by reading the
+<command>/bin/login</command>, by reading the
 <filename>/etc/passwd</filename> file.  An
 interactive non-login shell is started at the command-line (e.g.
+interactive non-login shell is started at the command-line (e.g.,
 <prompt>[prompt]$</prompt><command>/bin/bash</command>).  A non-interactive
 shell is usually present when a shell script is running.  It is non-interactive
 …
 <para>A base <filename>/etc/profile</filename> created below only sets some
 environment variables necessary for Bash to accept keystrokes properly,
 even in non-English locale. Replace "ll" with the
 two-letter code for your language (e.g. "en") and
 "CC" with the two-letter code for your country
 (e.g. "GB"). Also you may need to specify
+even in non-English locale. Replace <replaceable>[ll]</replaceable> with the
+two-letter code for your language (e.g., <quote>en</quote>) and
+<replaceable>[CC]</replaceable> with the two-letter code for your country
+(e.g., <quote>GB</quote>). Also you may need to specify
 (and this is actually the preferred form) your
 character encoding (e.g. "iso8859-1") after a dot (so that the result
 is "en_GB.iso8859-1").
+character encoding (e.g. <quote>iso8859-1</quote>) after a dot (so that the result
+is <quote>en_GB.iso8859-1</quote>).
 Issue the following command for more information:</para>
 <screen><userinput>man 3 setlocale</userinput></screen>
 <para>The list of all locales supported by glibc can be obtained by running
+<para>The list of all locales supported by Glibc can be obtained by running
 the following command:</para>
 …
 <para>Now, when you are sure about your locale settings, create the
 <filename>/etc/profile</filename> file:</para>
 <screen><userinput>cat &gt; /etc/profile &lt;&lt; "EOF"
 # Begin /etc/profile
 …
 # by Alexander E. Patrakov
 export LC_ALL=ll_CC
 export LANG=ll_CC
+export LC_ALL=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
+export LANG=<replaceable>[ll]</replaceable>_<replaceable>[CC]</replaceable>
 export INPUTRC=/etc/inputrc

chapter07/setclock.xml

-              r8ad7980
+              rf67f5cf
 <secondary>configuring</secondary></indexterm>
 <para>This setclock script reads the time from your hardware clock, also
+<para>This <command>setclock</command> script reads the time from your hardware clock, also
 known as BIOS or CMOS (Complementry Metal-Oxide Semiconductor) clock, and either converts that time to localtime
 using the <filename>/etc/localtime</filename> file (if the hardware clock
 …
 <para>Change the value of the <emphasis>UTC</emphasis> variable below to a
 <emphasis>0</emphasis> (zero) if your hardware clock is not set to GMT
+<parameter>0</parameter> (zero) if your hardware clock is not set to GMT
 time.</para>
 …
 the following:</para>
 <screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
 # Begin /etc/sysconfig/clock
 …
 # End /etc/sysconfig/clock
 <userinput>EOF</userinput></screen>
+EOF</userinput></screen>
 <para>Now, you may want to take a look at a very good hint explaining how we

chapter07/sysklogd.xml

r8ad7980	rf67f5cf
13	13
14	14	<para>The <filename>sysklogd</filename> script invokes the
15		<command>syslogd</command> program with the <~~emphasis>-m 0</emphasis~~> option.
	15	<command>syslogd</command> program with the <parameter>-m 0</parameter> option.
16	16	This option turns off the periodic timestamp mark that
17	17	<command>syslogd</command> writes to the log files every 20 minutes by default.

chapter07/usage.xml

-              r8ad7980
+              rf67f5cf
 using a run-levels scheme. There are 7 (from 0 to 6) run-levels
 (actually, there are more run-levels but they are for special cases and
 generally not used. The init man page describes those details), and each
+generally not used. The <command>init</command> man page describes those details), and each
 one of those corresponds to the things the computer is supposed to do when
 it starts up. The default run-level is 3. Here are the descriptions of the
 …
 <para>The command used to change run-levels is <command>init
 &lt;runlevel&gt;</command> where &lt;runlevel&gt; is the target run-level. For
 example, to reboot the computer, a user would issue the <command>init
 </command> command. The <command>reboot</command> command is just an alias for
+example, to reboot the computer, a user would issue the <userinput>init
+</userinput> command. The <command>reboot</command> command is just an alias for
 it, as is the <command>halt</command> command an alias for <command>init
 </command>.</para>
+<para>There are a number of directories under <filename>/etc/rc.d</filename>
+that look like like rc?.d (where ? is the number of the run-level) and rcsysinit.d
+<para>There are a number of directories under <filename class="directory">/etc/rc.d</filename>
+that look like like <filename class="directory">rc?.d</filename> (where ? is the
+number of the run-level) and <filename class="directory">rcsysinit.d</filename>
 all containing a number of symbolic links. Some begin with a K, the others begin
 with an S, and all of them have two numbers following the initial letter. The K
 …
 appropriate services get killed and others get started.</para>
+<para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the
+symlinks all point to them. Killing links and starting links point to
+the same script in /etc/rc.d/init.d. That's because the scripts can be
+called with different parameters like start, stop, restart, reload,
+status. When a K link is encountered, the appropriate script is run with
+the stop argument. When an S link is encountered, the appropriate script
+is run with the start argument.</para>
+<para>The real scripts are in <filename class="directory">/etc/rc.d/init.d</filename>.
+They do all the work, and the symlinks all point to them. Killing links and starting links
+point to the same script in <filename class="directory">/etc/rc.d/init.d</filename>.
+That's because the scripts can be called with different parameters like
+<parameter>start</parameter>, <parameter>stop</parameter>,
+<parameter>restart</parameter>, <parameter>reload</parameter>,
+<parameter>status</parameter>. When a K link is encountered, the appropriate
+script is run with the <parameter>stop</parameter> argument. When an S link is
+encountered, the appropriate script is run with the <parameter>start</parameter>
+argument.</para>
 <para>There is one exception. Links that start with an S in the
 rc0.d and rc6.d directories will not cause anything to be started. They
 will be called with the parameter <emphasis>stop</emphasis> to stop
+will be called with the parameter <parameter>stop</parameter> to stop
 something. The logic behind it is that when you are going to reboot or
 halt the system, you don't want to start anything, only stop the
 …
 scripts do:</para>
+<itemizedlist>
+<variablelist>
+<varlistentry>
+<term><parameter>start</parameter></term>
+<listitem><para>The service is started.</para></listitem>
+</varlistentry>
+<listitem><para><emphasis>start</emphasis>: The service is
+started.</para></listitem>
+<varlistentry>
+<term><parameter>stop</parameter></term>
+<listitem><para>The service is stopped.</para></listitem>
+</varlistentry>
+<listitem><para><emphasis>stop</emphasis>: The service is
+stopped.</para></listitem>
+<varlistentry>
+<term><parameter>restart</parameter></term>
+<listitem><para>The service is stopped and then started again.</para></listitem>
+</varlistentry>
+<listitem><para><emphasis>restart</emphasis>: The service is
+stopped and then started again.</para></listitem>
+<listitem><para><emphasis>reload</emphasis>: The configuration
+of the service is updated.
+<varlistentry>
+<term><parameter>reload</parameter></term>
+<listitem><para>The configuration of the service is updated.
 This is used after the configuration file of a service was modified, when
 the service doesn't need to be restarted.</para></listitem>
+</varlistentry>
+<listitem><para><emphasis>status</emphasis>: Tells if the service
+is running and with which PIDs.</para></listitem>
+</itemizedlist>
+<varlistentry>
+<term><parameter>status</parameter></term>
+<listitem><para>Tells if the service is running and with which PIDs.</para></listitem>
+</varlistentry>
+</variablelist>
 <para>Feel free to modify the way the boot process works (after all, it's your

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset f67f5cf

Legend:

Download in other formats: