Changeset 313e0960


Ignore:
Timestamp:
10/11/2003 12:02:35 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, 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/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
f27835d
Parents:
1668d8e
Message:

Correcting the working dir, readding a lost paragraph, and alphabetizing.

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

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • appendixa/e2fsprogs-shortdesc.xml

    r1668d8e r313e0960  
    77 support.</para>
    88
    9 <para><emphasis>Installed programs</emphasis>: badblocks, chattr, compile_et,
    10 debugfs, dumpe2fs, e2fsck, e2image, e2label, fsck, fsck.ext2, fsck.ext3,
    11 lsattr, mk_cmds, mke2fs, mkfs.ext2, mkfs.ext3, mklost+found, resize2fs,
    12 tune2fs, uuidgen, blkid, findfs and logsave.</para>
     9<para><emphasis>Installed programs</emphasis>: badblocks, blkid, chattr,
     10compile_et, debugfs, dumpe2fs, e2fsck, e2image, e2label, findfs, fsck,
     11fsck.ext2, fsck.ext3, logsave, lsattr, mk_cmds, mke2fs, mkfs.ext2, mkfs.ext3,
     12mklost+found, resize2fs, tune2fs and uuidgen.</para>
    1313
    14 <para><emphasis>Installed libraries</emphasis>: libcom_err.[a,so],
    15 libe2p.[a,so], libext2fs.[a,so], libss.[a,so], libuuid.[a,so] and libblkid.[a,so]</para>
     14<para><emphasis>Installed libraries</emphasis>: libblkid.[a,so],
     15libcom_err.[a,so], libe2p.[a,so], libext2fs.[a,so], libss.[a,so] and
     16libuuid.[a,so]</para>
    1617
    1718</sect2>

  • chapter01/changelog.xml

    r1668d8e r313e0960  
    9797</listitem>
    9898
     99<listitem><para>October 11h, 2003 [alex]: Adapted the required disk space
     100values, as posted by Bruce Dubbs.</para></listitem>
     101 
     102<listitem><para>October 11h, 2003 [alex]: Chapter 5 - Toolchain technical
     103notes: Added and changed some markup.</para></listitem>
     104 
    99105<listitem><para>October 9th, 2003 [gerard]: Upgraded to
    100106lfs-bootscripts-1.12.</para></listitem>

  • chapter04/chapter04.xml

    r1668d8e r313e0960  
    3333that is conveniently available throughout the entire build. You'll also need a
    3434working directory in which to unpack the sources and build them. A scheme that
    35 works well is to use <filename>$LFS/usr/src/packages</filename> for all the
    36 downloaded files and <filename>$LFS/usr/src</filename> as the working
    37 directory. In this way, everything will be on the LFS partition and available
    38 during all stages of the building process.</para>
    39 
    40 <!--
    41 <para>So you may want to execute the following command:</para>
    42 
    43 <screen><userinput>mkdir -p $LFS/usr/src/packages</userinput></screen>
    44 -->
     35works well is to use <filename>$LFS/tools/sources/packages</filename> for the
     36tarballs, and <filename>$LFS/tools/sources</filename> as the working directory
     37<emphasis>and</emphasis> as the place to store the patches. In this way,
     38everything will be on the LFS partition and available during all stages of the
     39building process.</para>
     40
     41<para>So you may want to execute the following command before starting
     42your download session:</para>
     43
     44<screen><userinput>mkdir -p $LFS/tools/sources/packages</userinput></screen>
    4545
    4646<!--

  • chapter05/binutils-pass2-inst.xml

    r1668d8e r313e0960  
    3030<screen><userinput>make </userinput></screen>
    3131
     32<note><para>It's worth pointing out that running the Binutils test suite here
     33is considered not as important running it in Chapter 6.</para></note>
     34
    3235<para>Test the results (there should be no unexpected failures here, expected
    3336failures are fine):</para>
Note: See TracChangeset for help on using the changeset viewer.