Changeset 360e2c4 for chapter06


Ignore:
Timestamp:
10/22/2003 10:26:46 PM (21 years ago)
Author:
Alex Gronenwoud <alex@…>
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, 12.2, 12.2-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, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
e91936a
Parents:
1612f40
Message:

Adding some markup and doing miscellaneous shuffles.

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

Location:
chapter06
Files:
12 edited

Legend:

Unmodified
Added
Removed

  • chapter06/adjustingtoolchain.xml

    r1612f40 r360e2c4  
    4545<screen><userinput>SPECFILE=/tools/lib/gcc-lib/*/*/specs &amp;&amp;
    4646sed -e 's@/tools/lib/ld-linux.so.2@/lib/ld-linux.so.2@g' \
    47 &nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE > newspecfile &amp;&amp;
     47&nbsp;&nbsp;&nbsp;&nbsp;$SPECFILE &gt; newspecfile &amp;&amp;
    4848mv -f newspecfile $SPECFILE &amp;&amp;
    4949unset SPECFILE</userinput></screen>
    … …  
    6666as expected. For this we are going to perform a simple sanity check:</para>
    6767
    68 <screen><userinput>echo 'main(){}' > dummy.c
     68<screen><userinput>echo 'main(){}' &gt; dummy.c
    6969gcc dummy.c
    7070readelf -l a.out | grep ': /lib'</userinput></screen>

  • chapter06/changingowner.xml

    r1612f40 r360e2c4  
    2525<screen><userinput>chown -R 0:0 /tools</userinput></screen>
    2626
    27 <para>The command uses "0:0" instead of "root:root", because chown is unable
    28 to resolve the name "root" until the password file has been created.</para>
     27<para>The command uses "0:0" instead of "root:root", because
     28<userinput>chown</userinput> is unable to resolve the name "root" until the
     29password file has been created.</para>
    2930
    3031</sect1>

  • chapter06/chroot.xml

    r1612f40 r360e2c4  
    2222&nbsp;&nbsp;&nbsp;&nbsp;/tools/bin/bash --login</userinput></screen>
    2323
    24 <screen><userinput>set +h</userinput></screen>
    25 
    2624<para>The <userinput>-i</userinput> option given to the
    2725<userinput>env</userinput> command will clear all variables of the chroot
    … …  
    2927set again. The TERM=$TERM construct will set the TERM variable inside chroot
    3028to the same value as outside chroot; this variable is needed for programs
    31 like vim and less to operate properly. If you need other variables present,
    32 such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para>
    33 
    34 <para>Also note the use of the set +h directive.  This tells bash to not use
    35 its internal path hashing. Without this directive, bash will remember paths
    36 to binaries.  Since as we go thru chapter 6, we want to use our newly compiled
    37 binaries as soon as they are installed, we turn off this function.</para>
     29like <userinput>vim</userinput> and <userinput>less</userinput> to operate
     30properly. If you need other variables present, such as CFLAGS or CXXFLAGS,
     31this is a good place to set them again.</para>
    3832
    3933<para>From this point on there's no need to use the LFS variable anymore,

  • chapter06/config-shadowpwd.xml

    r1612f40 r360e2c4  
    11<sect2><title>&nbsp;</title><para>&nbsp;</para></sect2>
    22
    3 <sect2><title>Configuring Shadow Password Suite</title>
     3<sect2><title>Configuring Shadow</title>
    44
    55<para>This package contains utilities to modify users' passwords, add
    66or delete users and groups, and the like. We're not going to explain what
    7 'password shadowing' means. A full explanation can be found in the doc/HOWTO
    8 file within the unpacked shadow password suite's source tree. There's one
    9 thing to keep in mind if you decide to use shadow support: programs that
     7'password shadowing' means. A full explanation can be found in the
     8<filename>doc/HOWTO</filename>
     9file within the unpacked Shadow source tree. There's one
     10thing to keep in mind if you decide to use Shadow support: programs that
    1011need to verify passwords (for example xdm, ftp daemons, pop3 daemons) need
    1112to be 'shadow-compliant', that is they need to be able to work with

  • chapter06/createfiles.xml

    r1612f40 r360e2c4  
    88we're installing all the software.</para>
    99
    10 <screen><userinput>ln -s /tools/bin/{bash,pwd,cat,stty} /bin
     10<screen><userinput>ln -s /tools/bin/{bash,cat,pwd,stty} /bin
    1111ln -s /tools/bin/perl /usr/bin
    1212ln -s /tools/lib/libgcc_s.so.1 /usr/lib

  • chapter06/creatingdirs.xml

    r1612f40 r360e2c4  
    2424<para>Directories are, by default, created with permission mode 755, but this
    2525isn't desirable for all directories. We will make two changes: one to the home
    26 directory of root, and another to the directories for temporary files.</para>
     26directory of <emphasis>root</emphasis>, and another to the directories for
     27temporary files.</para>
    2728
    2829<screen><userinput>chmod 0750 /root

  • chapter06/gcc-2953-inst.xml

    r1612f40 r360e2c4  
    3131patch -Np1 -i ../&gcc-2953-no-fixinc-patch;
    3232patch -Np1 -i ../&gcc-2953-returntype-fix-patch;
    33 echo timestamp > gcc/cstamp-h.in</userinput></screen>
     33echo timestamp &gt; gcc/cstamp-h.in</userinput></screen>
    3434
    3535<para>The GCC documentation recommends building GCC outside of the source

  • chapter06/makedev-inst.xml

    r1612f40 r360e2c4  
    44<title>Creating devices</title>
    55
    6 <para>Please note that unpacking the MAKEDEV-&makedev-version;.bz2 file
    7 doesn't create a directory for you to <userinput>cd</userinput> into, as
    8 the file only contains a single shell script.</para>
     6<para>Note that unpacking the <filename>MAKEDEV-&makedev-version;.bz2</filename>
     7file doesn't create a directory for you to <userinput>cd</userinput> into, as
     8the file contains only a shell script.</para>
    99
    10 <para>Install the MAKEDEV script:</para>
     10<para>Install the <userinput>MAKEDEV</userinput> script:</para>
    1111
    1212<screen><userinput>bzcat MAKEDEV-&makedev-version;.bz2 &gt; /dev/MAKEDEV
    … …  
    1818./MAKEDEV -v generic-nopty</userinput></screen>
    1919
    20 <para>The meaning of the option:</para>
     20<para>The meaning of the arguments:</para>
    2121
    2222<itemizedlist>
    23 <listitem><para><userinput>-v generic-nopty</userinput>: The
    24 <userinput>-v</userinput> parameter tells the MAKEDEV script to run in verbose
    25 mode. The <userinput>generic-nopty</userinput> parameter instructs MAKEDEV to
    26 create a generic selection of commonly used device special files, except for the
    27 ptyXX and ttyXX range of files. We don't need those files because we are going
    28 to use Unix98 PTYs via the <emphasis>devpts</emphasis> file
    29 system.</para></listitem>
     23<listitem><para><userinput>-v</userinput>: This tells the script to run in
     24verbose mode.</para></listitem>
     25
     26<listitem><para><userinput>generic-nopty</userinput>: This instructs
     27<userinput>MAKEDEV</userinput> to create a generic selection of commonly used
     28device special files, except for the ptyXX and ttyXX range of files. We don't
     29need those files because we are going to use Unix98 PTYs via the
     30<emphasis>devpts</emphasis> file system.</para></listitem>
    3031</itemizedlist>
    3132
    32 <para>If a device you need is missing, try running
    33 <userinput>./MAKEDEV -v &lt;device&gt;</userinput>. Alternatively, you may
    34 create devices via the <emphasis>mknod</emphasis> program. Please refer to
    35 the man and info pages of <emphasis>mknod</emphasis> if you need more
     33<para>If it turns out that some special device <filename>zzz</filename> that
     34you need is missing, try running <userinput>./MAKEDEV -v zzz</userinput>.
     35Alternatively, you may create devices via the <userinput>mknod</userinput>
     36program. Please refer to its man and info pages if you need more
    3637information.</para>
    3738

  • chapter06/mountproc.xml

    r1612f40 r360e2c4  
    66<emphasis>proc</emphasis> and <emphasis>devpts</emphasis> file systems must be
    77available within the chroot environment. A file system can be mounted as many
    8 times and in as many places as you like, thus it's not a problem that the these
     8times and in as many places as you like, thus it's not a problem that these
    99file systems are already mounted on your host system -- especially so because
    1010they are virtual file systems.</para>
    … …  
    4545without support for the devpts file system. You can check which file systems
    4646your kernel supports by peeking into its internals with a command such as
    47 <userinput>cat /proc/filesystems</userinput>. If for some reason, devpts is
     47<userinput>cat /proc/filesystems</userinput>. If for some reason devpts is
    4848listed there but the mount still doesn't work, check instead for a different
    4949file system variety called <emphasis>devfs</emphasis>. If devfs is listed then

  • chapter06/perl-inst.xml

    r1612f40 r360e2c4  
    2323couple of tests to resolve the name <emphasis>localhost</emphasis>:</para>
    2424
    25 <screen><userinput>echo "127.0.0.1 localhost $(hostname)" > /etc/hosts</userinput></screen>
     25<screen><userinput>echo "127.0.0.1 localhost $(hostname)" &gt; /etc/hosts</userinput></screen>
    2626
    2727<para>Now run the tests, if you wish:</para>

  • chapter06/pwdgroup.xml

    r1612f40 r360e2c4  
    5050<screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
    5151
     52<para>Note the use of the <userinput>+h</userinput> directive. This tells
     53<userinput>bash</userinput> not to use its internal path hashing. Without this
     54directive, <userinput>bash</userinput> would remember the paths to binaries it
     55has executed. Since as we go through this chapter, we want to use our newly
     56compiled binaries as soon as they are installed, we turn off this function.</para>
    5257
    5358</sect1>

  • chapter06/shadowpwd-inst.xml

    r1612f40 r360e2c4  
    22
    33<sect2>
    4 <title>Installation of Shadow Password Suite</title>
     4<title>Installation of Shadow</title>
    55
    66<para>The <userinput>login</userinput>, <userinput>getty</userinput> and
    … …  
    99programs, however, don't create these logfiles when they don't exist, so if
    1010you want this logging to occur you will have to create the files yourself.
    11 To let the Shadow package (that is installed next) detect these files in their
    12 proper place, create them now, with their proper permissions:</para>
    13 
    14 <para>Create these files with their proper permissions by running the
    15 following commands:</para>
     11The Shadow package needs to detect these files in their proper place, so we
     12create them now, with their proper permissions:</para>
    1613
    1714<screen><userinput>touch /var/run/utmp /var/log/{btmp,lastlog,wtmp}
    … …  
    3633<screen><userinput>touch /usr/bin/passwd</userinput></screen>
    3734
    38 <para>The current shadow suite has a problem in the newgrp command which causes
    39 it to fail.  The following patch (also appearing in Shadow's CVS code) fixes
    40 this problem.</para>
     35<para>The current Shadow suite has a problem that causes in the
     36<userinput>newgrp</userinput> command to fail.  The following patch (also
     37appearing in Shadow's CVS code) fixes this problem:</para>
    4138
    4239<screen><userinput>patch -Np1 -i ../&shadow-patch;</userinput></screen>
Note: See TracChangeset for help on using the changeset viewer.