Changes in / [d8c9a43f:b92cf89]

4 edited


  • chapter08/grub.xml

    rd8c9a43f rb92cf89  
    168168        <term><command>grub-glue-efi</command></term>
    169169        <listitem>
    170           <para>Processes ia32 and amd64 EFI images and glues them
    171           according to Apple format.</para>
     170          <para>Glue 32-bit and 64-bit binary into Apple universal one.</para>
    172171          <indexterm zone="ch-system-grub grub-glue-efi">
    173172            <primary sortas="b-grub-glue-efi">grub-glue-efi</primary>
  • chapter08/python.xml

    rd8c9a43f rb92cf89  
    103103    of this recommendation is for avoiding a conflict with the system
    104104    package manager (<command>dpkg</command> for example), but LFS does not
    105     have a system-wide package manager so this is not a problem.  If desired,
    106     suppress this warning by running the following commands:</para>
     105    have a system-wide package manager so this is not a problem.  And,
     106    <command>pip3</command> will attempt to check for a new version of
     107    itself whenever it's run.  As domain name resolving is not configured
     108    yet in LFS chroot environment, it will fail to check for a new version
     109    and produce a warning.  Once we boot the LFS system and set up network
     110    connection, it will then produce a warning telling the user to update it
     111    from a pre-built wheel on PyPI if any new version is available.  But LFS
     112    consider <command>pip3</command> a part of Python 3 so it should not be
     113    updated separately, and an update from a pre-built wheel will deviate
     114    from our purpose to build a Linux system from source code.  So the
     115    warning for a new <command>pip3</command> version should be ignored as
     116    well. If desired, suppress these warnings by running the following
     117    commands:</para>
    108119 <screen><userinput remap="install">cat &gt; /etc/pip.conf &lt;&lt; EOF
    110121root-user-action = ignore
     122disable-pip-version-check = true
  • chapter10/grub.xml

    rd8c9a43f rb92cf89  
    156156    </para></note>
     158    <note>
     159      <para>The GRUB designator for a partition may change if you added or
     160      removed some disks (including removable disks like USB thumb devices).
     161      The change may cause boot failure because
     162      <filename>grub.cfg</filename> refers to some <quote>old</quote>
     163      designators.  If you wish to avoid such a problem, you may use
     164      the UUID of partition and filesystem instead of GRUB designator to
     165      specify a partition.
     166      Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show
     167      the UUID of your filesystems (in <literal>UUID</literal> column) and
     168      partitions (in <literal>PARTUUID</literal> column).  Then replace
     169      <literal>set root=(hdx,y)</literal> with
     170      <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem where the kernel is installed&gt;</replaceable></literal>, and replace
     171      <literal>root=/dev/sda2</literal> with
     172      <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS is built&gt;</replaceable></literal>.</para>
     173      <para>Note that the UUID of a partition and the UUID of the filesystem
     174      in this partition is completely different.  Some online resources may
     175      instruct you to use
     176      <literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal>
     177      instead of
     178      <literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
     179      but doing so will require an initramfs which is beyond the scope of
     180      LFS.</para>
     181      <para>The name of the device node for a partition in
     182      <filename class='directory'>/dev</filename> may also change (more
     183      unlikely than GRUB designator change though).  You can also replace
     184      paths to device nodes like <literal>/dev/sda1</literal> with
     185      <literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
     186      in <filename>/etc/fstab</filename>, to avoid a potential boot failure
     187      in case the device node name has changed.</para>
     188    </note>
    158190    <para>GRUB is an extremely powerful program and it provides a tremendous
    159191    number of options for booting from a wide variety of devices, operating
  • chapter11/reboot.xml

    rd8c9a43f rb92cf89  
    6262    </para></listitem>
     64    <listitem><para>Install <ulink
     65    url='&blfs-book;postlfs/firmware.html'>firmwares</ulink> if the kernel
     66    driver for your hardware require some firmware to function properly.
     67    </para></listitem>
    6469    <listitem><para>Finally, a review of the following configuration files
    6570    is also appropriate at this point.</para>
Note: See TracChangeset for help on using the changeset viewer.