gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

text updates

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1114 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-08-29 19:50:53 +00:00
parent 2b1174bee6
commit fa914e5962
7 changed files with 39 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter07/ethnet.xml
View File

@ -154,7 +154,7 @@ BROADCAST=192.168.1.255
<para>Of course, the values of those four variables have to be changed <para>Of course, the values of those four variables have to be changed
in every file to in every file to
match the proper setup. Usually NETMASK and BROADCAST will remain the match the proper setup. Usually NETMASK and BROADCAST will remain the
same, just the DEVICE IP variables will change per network interface. If same, just the DEVICE and IP variables will change per network interface. If
the ONBOOT variable is set to yes, the ethnet script will bring it up the ONBOOT variable is set to yes, the ethnet script will bring it up
during boot up of the system. If set to anything else but yes it will be during boot up of the system. If set to anything else but yes it will be
ignored by the ethnet script and thus not brought up.</para> ignored by the ethnet script and thus not brought up.</para>

15
chapter07/hosts.xml
View File

@ -1,13 +1,13 @@
<sect1 id="ch07-hosts"> <sect1 id="ch07-hosts">
<title>Creating the /etc/hosts file</title> <title>Creating the /etc/hosts file</title>
<para>If a network card is to be configured, a user has to decide on the <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. An IP-address, FQDN and possible aliases for use in the /etc/hosts file. An
example is:</para> example is:</para>
<para><screen>&lt;my-IP&gt; myhost.mydomain.org aliases</screen></para> <para><screen>&lt;my-IP&gt; myhost.mydomain.org aliases</screen></para>
<para>It should made sure that the IP-address is in the private network <para>You should made sure that the IP-address is in the private network
IP-address range. Valid ranges are:</para> IP-address range. Valid ranges are:</para>
<para><screen> Class Networks <para><screen> Class Networks
@ -18,7 +18,7 @@ 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 <para>A valid IP address could be 192.168.1.1. A valid FQDN for this IP could
be www.linuxfromscratch.org</para> be www.linuxfromscratch.org</para>
<para>If a user is not going to use a network card, he still needs to <para>If you aren't going to use a network card, you still need to
come up with a FQDN. This is necessary for programs like Sendmail to operate come up with a FQDN. This is necessary for programs like Sendmail to operate
correctly (in fact; Sendmail won't run when it can't determine the FQDN).</para> correctly (in fact; Sendmail won't run when it can't determine the FQDN).</para>
@ -45,11 +45,10 @@ correctly (in fact; Sendmail won't run when it can't determine the FQDN).</para>
# End /etc/hosts (network card version) # End /etc/hosts (network card version)
<userinput>EOF</userinput></screen></para> <userinput>EOF</userinput></screen></para>
<para>Of course, the 192.168.1.1 and www.mydomain.org have to be changed to the <para>Of course, the 192.168.1.1 and www.mydomain.org have to be changed
users to your liking (or requirements if assigned an IP-address by a network/system
liking (or requirements if assigned an IP-address by a network/system administrator and this machine is planned to be connected to that
administrator and this machine is planned to be network).</para>
connected to that network).</para>
</sect1> </sect1>

7
chapter07/loadkeys.xml
View File

@ -1,13 +1,8 @@
<sect1 id="ch07-loadkeys"> <sect1 id="ch07-loadkeys">
<title>Creating the loadkeys script</title> <title>Creating the loadkeys script</title>
<!--
<para>You only need to create this script if you don't have a <para>You only need to create this script if you don't have a
default 101 keys US keyboard layout. default 101 keys US keyboard layout.</para>
Because we've scrapped the symbolic link for the default, I assume
that everyone will need this script?
-->
<para>Create the <filename>/etc/init.d/loadkeys</filename> script by <para>Create the <filename>/etc/init.d/loadkeys</filename> script by
running the following command:</para> running the following command:</para>

4
chapter07/network.xml
View File

@ -6,8 +6,8 @@ hostname is put in it by running:</para>
<para><screen><userinput>echo "HOSTNAME=lfs" &gt; /etc/sysconfig/network</userinput></screen></para> <para><screen><userinput>echo "HOSTNAME=lfs" &gt; /etc/sysconfig/network</userinput></screen></para>
<para><quote>lfs</quote> needs to be replaced by the name the computer is <para><quote>lfs</quote> needs to be replaced with the name the computer is
to be called. A user should not enter the FQDN (Fully Qualified Domain to be called. You should not enter the FQDN (Fully Qualified Domain
Name) here. That information will be put in the Name) here. That information will be put in the
<filename>/etc/hosts</filename> file later.</para> <filename>/etc/hosts</filename> file later.</para>

20
chapter07/setclock.xml
View File

@ -6,15 +6,11 @@ known as BIOS or CMOS clock) isn't set to GMT time. The recommended
setup is setting the hardware clock to GMT and having the time converted setup is setting the hardware clock to GMT and having the time converted
to localtime using the /etc/localtime symbolic link. But if an to localtime using the /etc/localtime symbolic link. But if an
OS is run that doesn't understand a clock set to GMT (most notable are OS is run that doesn't understand a clock set to GMT (most notable are
Microsoft OS'es) a user might want to set the clock to localtime so that Microsoft OS'es) you may want to set the clock to localtime so that
the time is properly displayed on those OS'es. This script will reset the time is properly displayed on those OS'es. This script will then
the kernel time to the hardware clock without converting the time using set the kernel time to the hardware clock without converting the time using
the /etc/localtime symlink.</para> the /etc/localtime symlink.</para>
<para>If you want to use this script on your system even if the
hardware clock is set to GMT, then the UTC variable below has to be
changed to the value of <emphasis>1</emphasis>.</para>
<para>Create the <filename>/etc/init.d/setclock</filename> script by running <para>Create the <filename>/etc/init.d/setclock</filename> script by running
the following command:</para> the following command:</para>
@ -62,21 +58,21 @@ evaluate_retval
<sect2> <sect2>
<title>Creating the /etc/sysconfig/clock file</title> <title>Creating the /etc/sysconfig/clock file</title>
<para>If you want to use this script on your system even if the
hardware clock is set to GMT, then the UTC variable below has to be
changed to the value of <emphasis>1</emphasis>.</para>
<para>Create a new file <filename>/etc/sysconfig/clock</filename> by running <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
the following:</para> the following:</para>
<para><screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"</userinput> <para><screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"</userinput>
# Begin /etc/sysconfig/clock # Begin /etc/sysconfig/clock
UTC=1 UTC=0
# End /etc/sysconfig/clock # End /etc/sysconfig/clock
<userinput>EOF</userinput></screen></para> <userinput>EOF</userinput></screen></para>
<para>If the hardware clock (also known as BIOS or CMOS clock) is not set to
GMT time, then the UTC variable in the /etc/sysconfig/clock file needs to be
set to the value <emphasis>0</emphasis> (zero).</para>
<para>Now, you may want to take a look at a very good hint explaining how we <para>Now, you may want to take a look at a very good hint explaining how we
deal with time on LFS at <ulink deal with time on LFS at <ulink
url="&hint-root;time.txt">&hint-root;time.txt</ulink>. url="&hint-root;time.txt">&hint-root;time.txt</ulink>.

3
chapter07/symperm.xml
View File

@ -3,7 +3,8 @@
<para>These files get the proper permissions and the necessary symlinks <para>These files get the proper permissions and the necessary symlinks
are created by running the following commands. If you didn't create the loadkeys are created by running the following commands. If you didn't create the loadkeys
and setclock scripts, make sure not to type them in the commands below.</para> and/or setclock scripts, make sure not to type them in the commands
below.</para>
<para>A note of caution: all the symlinks (that start with an S or K) have to <para>A note of caution: all the symlinks (that start with an S or K) have to
be of the form Sxxxname where xxx are three digits denoting the order in be of the form Sxxxname where xxx are three digits denoting the order in

31
chapter07/usage.xml
View File

@ -35,25 +35,30 @@ before any runlevel is executed and runs the scripts listed in
/etc/rcS.d</para> /etc/rcS.d</para>
<para>There are a number of directories under /etc that look like like rc?.d <para>There are a number of directories under /etc that look like like rc?.d
where ? is the number of the runlevel and rcS.d. A user might take a look where ? is the number of the runlevel and rcS.d which contain a number of s
at one of ymbolic links. Some begin with an K, the others begin with an S, and all
them (after this chapter is finished, right now there's nothing of them have three numbers following the initial letter. The K means to
there yet). There are a number of symbolic links. Some begin with an K, stop (kill) a service, and the S means to start a service. The numbers
the others begin with an S, and all of them have three numbers following determine the order in which the scripts are run, from 000 to 999; the
the initial letter. The K means to stop (kill) a service, and the S means lower the number the sooner it gets executed. When init switches to
to start a service. The numbers determine the order in which the scripts another runlevel, the appropriate services get killed and others get
are run, from 000 to 999; the lower the number the sooner it gets started.</para>
executed. When init switches to another runlevel, the appropriate
services get killed and others get started.</para>
<para>The real scripts are in /etc/init.d. They do all the work, and the <para>The real scripts are in /etc/init.d. They do all the work, and the
symlinks all point to them. Killing links and starting symlinks all point to them. Killing links and starting links point to
links point to the same script in /etc/init.d. That's because the scripts the same script in /etc/init.d. That's because the scripts can be
can be called with different parameters like start, stop, restart, reload, called with different parameters like start, stop, restart, reload,
status. When a K link is encountered, the appropriate script is run with status. When a K link is encountered, the appropriate script is run with
the stop argument. When a S link is encountered, the appropriate script the stop argument. When a S link is encountered, the appropriate script
is run with the start argument.</para> is run with the start 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 paramater <emphasis>stop</emphasis> 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
system.</para>
<para>These are descriptions of what the arguments make the <para>These are descriptions of what the arguments make the
scripts do:</para> scripts do:</para>