Changeset f427ba23
- Timestamp:
- 09/25/2022 07:16:23 AM (18 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 0ea3431, 111194c, 471a32e
- Parents:
- 4d04dc7
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter10/kernel.xml
r4d04dc7 rf427ba23 336 336 337 337 <caution> 338 <para>If the host system has a separate /boot partition, the files copied 339 below should go there. The easiest way to do that is to bind /boot on the 340 host (outside chroot) to /mnt/lfs/boot before proceeding. As the 341 &root; user in the <emphasis>host system</emphasis>:</para> 342 343 <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> 338 <para>If you've decided to use a separate &boot-dir; partition for the 339 LFS system (maybe sharing a &boot-dir; partition with the host 340 distro) , the files copied below should go there. The easiest way to 341 do that is to create the entry for &boot-dir; in &fstab; first (read 342 the previous section for details), then issue the following command 343 as the &root; user in the 344 <emphasis>chroot environment</emphasis>:</para> 345 346 <screen role="nodump"><userinput>mount /boot</userinput></screen> 347 348 <para>The path to the device node is omitted in the command because 349 <command>mount</command> can read it from &fstab;.</para> 344 350 </caution> 345 351 -
general.ent
r4d04dc7 rf427ba23 123 123 <!ENTITY lfs-user "<systemitem class='username'>lfs</systemitem>"> 124 124 <!ENTITY fstab "<filename>/etc/fstab</filename>"> 125 <!ENTITY boot-dir "<filename class='directory'>/boot</filename>"> 125 126 126 127 <!ENTITY % packages-entities SYSTEM "packages.ent">
Note:
See TracChangeset
for help on using the changeset viewer.