kernel: adjust the instruction for mounting /boot

LFS and the host may use different /boot configuration, so do not assume
they'll share a /boot partition (two different /boot partition or only one
with separate /boot are possible).
This commit is contained in:
Xi Ruoyao 2022-09-25 15:16:23 +08:00
parent 4d04dc743f
commit f427ba2336
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
2 changed files with 12 additions and 5 deletions

View File

@ -335,12 +335,18 @@ Device Drivers --->
the <filename class="directory">/boot</filename> directory.</para>
<caution>
<para>If the host system has a separate /boot partition, the files copied
below should go there. The easiest way to do that is to bind /boot on the
host (outside chroot) to /mnt/lfs/boot before proceeding. As the
&root; user in the <emphasis>host system</emphasis>:</para>
<para>If you've decided to use a separate &boot-dir; partition for the
LFS system (maybe sharing a &boot-dir; partition with the host
distro) , the files copied below should go there. The easiest way to
do that is to create the entry for &boot-dir; in &fstab; first (read
the previous section for details), then issue the following command
as the &root; user in the
<emphasis>chroot environment</emphasis>:</para>
<screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
<screen role="nodump"><userinput>mount /boot</userinput></screen>
<para>The path to the device node is omitted in the command because
<command>mount</command> can read it from &fstab;.</para>
</caution>
<para>The path to the kernel image may vary depending on the platform being

View File

@ -122,6 +122,7 @@
<!ENTITY root "<systemitem class='username'>root</systemitem>">
<!ENTITY lfs-user "<systemitem class='username'>lfs</systemitem>">
<!ENTITY fstab "<filename>/etc/fstab</filename>">
<!ENTITY boot-dir "<filename class='directory'>/boot</filename>">
<!ENTITY % packages-entities SYSTEM "packages.ent">
%packages-entities;