Changeset 137bd50


Ignore:
Timestamp:
03/18/2001 08:39:49 PM (23 years ago)
Author:
Thomas Balu Walter <tw@…>
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:
53b5ccf
Parents:
72033583
Message:

You's

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

Files:
13 edited

Legend:

Unmodified
Added
Removed

  • chapter05/kernel-inst.xml

    r72033583 r137bd50  
    1111
    1212<para>
    13 Create the kernel configuration file by running the following command:
     13The kernel configuration file is created by running the following command:
    1414</para>
    1515

  • chapter05/proc.xml

    r72033583 r137bd50  
    1111
    1212<para>
    13 Mount the proc file system under $LFS/proc by running the following command:
     13The proc file system is mounted under $LFS/proc by running the following command:
    1414</para>
    1515

  • chapter05/pwdgroup.xml

    r72033583 r137bd50  
    88packages. The groups with their GID's below aren't part of any standard.
    99The LSB only recommends besides a group root a group bin to be present
    10 with GID 1. Other group names and GID's can be chosen by yourself. Well
     10with GID 1. Other group names and GID's can be chosen by the user. Well
    1111written packages don't depend on GID numbers but just use the group
    1212name, it doesn't matter all that much what GID a group has. Since there

  • chapter05/tar-inst.xml

    r72033583 r137bd50  
    33
    44<para>
    5 If you want to be able to directly use bzip2 files with tar, use the tar
     5To be able to directly use bzip2 files with tar, use the tar
    66patch avaiable from the LFS FTP site. This patch will add the -y option
    7 to tar which works the same as the -z option to tar (which you can use
     7to tar which works the same as the -z option to tar (which can be used
    88for gzip files).
    99</para>

  • chapter06/netkitbase.xml

    r72033583 r137bd50  
    1919There are other files in the <filename
    2020class="directory">etc.sample</filename> directory which might be of
    21 interest to you.
     21interest to the user.
    2222</para>
    2323

  • chapter06/nettools.xml

    r72033583 r137bd50  
    33
    44<para>
    5 Edit the <filename>Makefile</filename> file and edit the CFLAGS variable
    6 if you want to add compiler optimzations.
     5The <filename>Makefile</filename> file CFLAGS variable has to be edited
     6if compiler optimzations should be added.
    77</para>
    88

  • chapter07/ethnet-symperm.xml

    r72033583 r137bd50  
    33
    44<para>
    5 Set the proper file permissions and create the necessary symlink by
     5The proper file permissions and the necessary symlinks are set or created by
    66running the following commands:
    77</para>

  • chapter07/ethnet.xml

    r72033583 r137bd50  
    33
    44<para>
    5 This section only applies if you are going to configure a network card.
    6 If you're not, skip this section.
     5This section only applies if a user is going to configure a network card.
     6If not, this section can be skipped.
    77</para>
    88
    99<para>
    10 Create a new file <filename>/etc/init.d/ethnet</filename> containing the
     10A new file <filename>/etc/init.d/ethnet</filename> is created containing the
    1111following:
    1212</para>
    … …  
    120120
    121121<para>
    122 If you require a default gateway to be setup, run the following command:
     122If a default gateway is required to be setup, the following command does that:
    123123</para>
    124124
    … …  
    132132
    133133<para>
    134 Change GATEWAY to match your network setup.
     134GATEWAY needs to be changed to match the network setup.
    135135</para>
    136136
    … …  
    144144the files in the /etc/sysconfig/network-scripts directory. This
    145145directory should contain files in the form of ifcfg-x where x is an
    146 identification number (or whatever you choose to name it).
     146identification number (or whatever a user named it).
    147147</para>
    148148
    149149<para>
    150 First create the network-scripts directory by running:
     150First the network-scripts directory is created by running:
    151151</para>
    152152
    … …  
    159159<para>
    160160
    161 Now, create new files in that directory containing the following.
    162 The following creates a sample file ifcfg-eth0:
     161Now, new files are created in that directory containing the following.
     162This creates a sample file ifcfg-eth0:
    163163</para>
    164164
    … …  
    177177
    178178<para>
    179 Of course, change the values of those four variables in every file to
     179Of course, the values of those four variables have to be changed
     180in every file to
    180181match the proper setup. Usually NETMASK and BROADCAST will remain the
    181182same, just the DEVICE IP variables will change per network interface. If

  • chapter07/hosts.xml

    r72033583 r137bd50  
    33
    44<para>
    5 If you want to configure a network card, you have to decide on the
     5If a network card is to be configured, a user has to decide on the
    66IP-address, FQDN and possible aliases for use in the /etc/hosts file. An
    77example is:
    … …  
    1515
    1616<para>
    17 Make sure the IP-address is in the private network IP-address range.
    18 Valid ranges are:
     17It should made sure that the IP-address is in the private network
     18IP-address range. Valid ranges are:
    1919</para>
    2020
    … …  
    3434
    3535<para>
    36 If you're not going to use a network card, you still need to come up with a
     36If a user is not going to use a network card, he still needs to come up with a
    3737FQDN. This is necessary for programs like Sendmail to operate correctly (in
    3838fact; Sendmail won't run when it can't determine the FQDN).
    … …  
    4040
    4141<para>
    42 If you don't configure a network card, create a new file
    43 <filename>/etc/hosts</filename> by running:
     42If a network card is not going to be configured, a new file
     43<filename>/etc/hosts</filename> is created by running:
    4444</para>
    4545
    … …  
    5757
    5858<para>
    59 If you do configure a network card, create a new file
    60 <filename>/etc/hosts</filename> containing:
     59If a network card is to be configured, a new file
     60<filename>/etc/hosts</filename> is created containing:
    6161</para>
    6262
    … …  
    7575
    7676<para>
    77 Of course, change the 192.168.1.1 and www.mydomain.org to your own
    78 liking (or requirements if you are assigned an IP-address by a network/system
    79 administrator and you plan on connecting this machine to that network).
     77Of course, the 192.168.1.1 and www.mydomain.org have to be changed to the
     78users
     79liking (or requirements if assigned an IP-address by a network/system
     80administrator and this machine is planned to be connected to that network).
    8081</para>
    8182

  • chapter07/introduction.xml

    r72033583 r137bd50  
    33
    44<para>
    5 This chapter will setup basic networking. Although you might not be
     5This chapter will setup basic networking. Although the system might not be
    66connected to a network, Linux software uses network functions anyway.
    77We'll be installing at least the local loopback device and a network

  • chapter07/localnet-symperm.xml

    r72033583 r137bd50  
    33
    44<para>
    5 Set the proper file permissions and create the necessary symlink by
     5The proper file permissions and the necessary symlink are set or created by
    66running the following commands:
    77</para>

  • chapter07/localnet.xml

    r72033583 r137bd50  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/localnet</filename> containing
     5A new file <filename>/etc/init.d/localnet</filename> is created containing
    66the following:
    77</para>

  • chapter07/network.xml

    r72033583 r137bd50  
    33
    44<para>
    5 Create a new file <filename>/etc/sysconfig/network</filename> and put the
    6 hostname in it by running:
     5A new file <filename>/etc/sysconfig/network</filename> is created and the
     6hostname is put in it by running:
    77</para>
    88
    … …  
    1414
    1515<para>
    16 Replace <quote>lfs</quote> by the name you wish to call your computer.
    17 Please not that you should not enter the FQDN (Fully Qualified Domain
     16<quote>lfs</quote> needs to be replaced by the name the computer is to be
     17called.
     18A user should not enter the FQDN (Fully Qualified Domain
    1819Name) here. That information will be put in the
    1920<filename>/etc/hosts</filename> file later.
Note: See TracChangeset for help on using the changeset viewer.