Ignore:
Timestamp:
06/16/2020 11:56:28 AM (4 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, 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:
9a05e45
Parents:
560065f (diff), 1cd5961 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Split Chapter 5 into three separate chapters.
Implement a new method of cross-building the LFS tool chain
and other tools to simplify the method of isolating the
new system from the original host. This will be the start of
LFS-10.0.

Move old trunk/BOOK to branches/old-trunk.

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter02/creatingfilesystem.xml

    r560065f r675606b  
    5353<screen role="nodump"><userinput>mkfs -v -t ext4 /dev/<replaceable>&lt;xxx&gt;</replaceable></userinput></screen>
    5454
    55 <!--
    5655  <para>Replace <replaceable>&lt;xxx&gt;</replaceable> with the name of the LFS
    57   partition (<filename class="devicefile">sda5</filename> in our previous
    58   example).</para>
     56  partition.</para>
    5957
    60   <note>
    61     <para>Some host distributions use custom features in their filesystem
    62     creation tools (E2fsprogs). This can cause problems when booting into your new
    63     LFS in Chapter&nbsp;9, as those features will not be supported by the LFS-installed
    64     E2fsprogs; you will get an error similar to <quote>unsupported filesystem
    65     features, upgrade your e2fsprogs</quote>. To check if your host system
    66     uses custom enhancements, run the following command:</para>
    67 
    68 <screen role="nodump"><userinput>debugfs -R feature /dev/<replaceable>&lt;xxx&gt;</replaceable></userinput></screen>
    69 
    70     <para>If the output contains features other than
    71     <option>has_journal</option>, <option>ext_attr</option>,
    72     <option>resize_inode</option>, <option>dir_index</option>,
    73     <option>filetype</option>, <option>sparse_super</option>,
    74     <option>large_file</option> or <option>needs_recovery</option>, then your
    75     host system may have custom enhancements.  In that case, to avoid later
    76     problems, you should compile the stock E2fsprogs package and use the
    77     resulting binaries to re-create the filesystem on your LFS partition:</para>
    78 
    79 <screen role="nodump"><userinput>cd /tmp
    80 tar -xzvf /path/to/sources/e2fsprogs-&e2fsprogs-version;.tar.gz
    81 cd e2fsprogs-&e2fsprogs-version;
    82 mkdir -v build
    83 cd build
    84 ../configure
    85 make #note that we intentionally don't 'make install' here!
    86 ./misc/mke2fs -jv /dev/<replaceable>&lt;xxx&gt;</replaceable>
    87 cd /tmp
    88 rm -rfv e2fsprogs-&e2fsprogs-version;</userinput></screen>
    89   </note>
    90 -->
    9158  <para>If you are using an existing <systemitem class="filesystem">swap
    9259  </systemitem> partition, there is no need to format it. If a new
Note: See TracChangeset for help on using the changeset viewer.