Changeset fa914e5 for chapter07


Ignore:
Timestamp:
08/29/2001 07:50:53 PM (23 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
2bdc67d
Parents:
2b1174be
Message:

text updates

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1114 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter07
Files:
7 edited

Legend:

Unmodified
Added
Removed

  • chapter07/ethnet.xml

    r2b1174be rfa914e5  
    155155in every file to
    156156match the proper setup. Usually NETMASK and BROADCAST will remain the
    157 same, just the DEVICE IP variables will change per network interface. If
     157same, just the DEVICE and IP variables will change per network interface. If
    158158the ONBOOT variable is set to yes, the ethnet script will bring it up
    159159during boot up of the system. If set to anything else but yes it will be

  • chapter07/hosts.xml

    r2b1174be rfa914e5  
    22<title>Creating the /etc/hosts file</title>
    33
    4 <para>If a network card is to be configured, a user has to decide on the
     4<para>If a network card is to be configured, you have to decide on the
    55IP-address, FQDN and possible aliases for use in the /etc/hosts file. An
    66example is:</para>
    … …  
    88<para><screen>&lt;my-IP&gt; myhost.mydomain.org aliases</screen></para>
    99
    10 <para>It should made sure that the IP-address is in the private network
     10<para>You should made sure that the IP-address is in the private network
    1111IP-address range. Valid ranges are:</para>
    1212
    … …  
    1919be www.linuxfromscratch.org</para>
    2020
    21 <para>If a user is not going to use a network card, he still needs to
     21<para>If you aren't going to use a network card, you still need to
    2222come up with a FQDN. This is necessary for programs like Sendmail to operate
    2323correctly (in fact; Sendmail won't run when it can't determine the FQDN).</para>
    … …  
    4646<userinput>EOF</userinput></screen></para>
    4747
    48 <para>Of course, the 192.168.1.1 and www.mydomain.org have to be changed to the
    49 users
    50 liking (or requirements if assigned an IP-address by a network/system
    51 administrator and this machine is planned to be
    52 connected to that network).</para>
     48<para>Of course, the 192.168.1.1 and www.mydomain.org have to be changed
     49to your liking (or requirements if assigned an IP-address by a network/system
     50administrator and this machine is planned to be connected to that
     51network).</para>
    5352
    5453</sect1>

  • chapter07/loadkeys.xml

    r2b1174be rfa914e5  
    22<title>Creating the loadkeys script</title>
    33
    4 <!--
    54<para>You only need to create this script if you don't have a
    6 default 101 keys US keyboard layout.
    7 
    8 Because we've scrapped the symbolic link for the default, I assume
    9 that everyone will need this script?
    10 -->
     5default 101 keys US keyboard layout.</para>
    116
    127<para>Create the <filename>/etc/init.d/loadkeys</filename> script by

  • chapter07/network.xml

    r2b1174be rfa914e5  
    77<para><screen><userinput>echo "HOSTNAME=lfs" &gt; /etc/sysconfig/network</userinput></screen></para>
    88
    9 <para><quote>lfs</quote> needs to be replaced by the name the computer is
    10 to be called.  A user should not enter the FQDN (Fully Qualified Domain
     9<para><quote>lfs</quote> needs to be replaced with the name the computer is
     10to be called.  You should not enter the FQDN (Fully Qualified Domain
    1111Name) here. That information will be put in the
    1212<filename>/etc/hosts</filename> file later.</para>

  • chapter07/setclock.xml

    r2b1174be rfa914e5  
    77to localtime using the /etc/localtime symbolic link. But if an
    88OS is run that doesn't understand a clock set to GMT (most notable are
    9 Microsoft OS'es) a user might want to set the clock to localtime so that
    10 the time is properly displayed on those OS'es. This script will reset
    11 the kernel time to the hardware clock without converting the time using
     9Microsoft OS'es) you may want to set the clock to localtime so that
     10the time is properly displayed on those OS'es. This script will then
     11set the kernel time to the hardware clock without converting the time using
    1212the /etc/localtime symlink.</para>
    13 
    14 <para>If you want to use this script on your system even if the
    15 hardware clock is set to GMT, then the UTC variable below has to be
    16 changed to the value of <emphasis>1</emphasis>.</para>
    1713
    1814<para>Create the <filename>/etc/init.d/setclock</filename> script by running
    … …  
    6359<title>Creating the /etc/sysconfig/clock file</title>
    6460
     61<para>If you want to use this script on your system even if the
     62hardware clock is set to GMT, then the UTC variable below has to be
     63changed to the value of <emphasis>1</emphasis>.</para>
     64
    6565<para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
    6666the following:</para>
    … …  
    6969# Begin /etc/sysconfig/clock
    7070
    71 UTC=1
     71UTC=0
    7272
    7373# End /etc/sysconfig/clock
    7474<userinput>EOF</userinput></screen></para>
    75 
    76 <para>If the hardware clock (also known as BIOS or CMOS clock) is not set to
    77 GMT time, then the UTC variable in the /etc/sysconfig/clock file needs to be
    78 set to the value <emphasis>0</emphasis> (zero).</para>
    7975
    8076<para>Now, you may want to take a look at a very good hint explaining how we

  • chapter07/symperm.xml

    r2b1174be rfa914e5  
    44<para>These files get the proper permissions and the necessary symlinks
    55are created by running the following commands. If you didn't create the loadkeys
    6 and setclock scripts, make sure not to type them in the commands below.</para>
     6and/or setclock scripts, make sure not to type them in the commands
     7below.</para>
    78
    89<para>A note of caution: all the symlinks (that start with an S or K) have to

  • chapter07/usage.xml

    r2b1174be rfa914e5  
    3636
    3737<para>There are a number of directories under /etc that look like like rc?.d
    38 where ? is the number of the runlevel and rcS.d. A user might take a look
    39 at one of
    40 them (after this chapter is finished, right now there's nothing
    41 there yet). There are a number of symbolic links. Some begin with an K,
    42 the others begin with an S, and all of them have three numbers following
    43 the initial letter. The K means to stop (kill) a service, and the S means
    44 to start a service. The numbers determine the order in which the scripts
    45 are run, from 000 to 999; the lower the number the sooner it gets
    46 executed. When init switches to another runlevel, the appropriate
    47 services get killed and others get started.</para>
     38where ? is the number of the runlevel and rcS.d which contain a number of s
     39ymbolic links. Some begin with an K, the others begin with an S, and all
     40of them have three numbers following the initial letter. The K means to
     41stop (kill) a service, and the S means to start a service. The numbers
     42determine the order in which the scripts are run, from 000 to 999; the
     43lower the number the sooner it gets executed. When init switches to
     44another runlevel, the appropriate services get killed and others get
     45started.</para>
    4846
    4947<para>The real scripts are in /etc/init.d. They do all the work, and the
    50 symlinks all point to them. Killing links and starting
    51 links point to the same script in /etc/init.d. That's because the scripts
    52 can be called with different parameters like start, stop, restart, reload,
     48symlinks all point to them. Killing links and starting links point to
     49the same script in /etc/init.d. That's because the scripts can be
     50called with different parameters like start, stop, restart, reload,
    5351status. When a K link is encountered, the appropriate script is run with
    5452the stop argument. When a S link is encountered, the appropriate script
    5553is run with the start argument.</para>
     54
     55<para>There is one exception. Links that start with an S in the
     56rc0.d and rc6.d directories will not cause anything to be started. They
     57will be called with the paramater <emphasis>stop</emphasis> to stop
     58something. The logic behind it is that when you are going to reboot or
     59halt the system, you don't want to start anything, only stop the
     60system.</para>
    5661
    5762<para>These are descriptions of what the arguments make the
Note: See TracChangeset for help on using the changeset viewer.