Changeset f427ba23


Ignore:
Timestamp:
09/25/2022 07:16:23 AM (3 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/pip3, xry111/rust-wip-20221008
Children:
0ea3431, 111194c, 471a32e
Parents:
4d04dc7
Message:

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).

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • chapter10/kernel.xml

    r4d04dc7 rf427ba23  
    336336
    337337    <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>
    344350    </caution>
    345351
  • general.ent

    r4d04dc7 rf427ba23  
    123123<!ENTITY lfs-user        "<systemitem class='username'>lfs</systemitem>">
    124124<!ENTITY fstab           "<filename>/etc/fstab</filename>">
     125<!ENTITY boot-dir        "<filename class='directory'>/boot</filename>">
    125126
    126127<!ENTITY % packages-entities SYSTEM "packages.ent">
Note: See TracChangeset for help on using the changeset viewer.