| Newsgroups |
gmane.linux.lfs.book |
| Message-ID |
<[email protected]> |
This is an automated email from the git hooks/post-receive script.
git pushed a commit to branch xry111/arm64
in repository lfs.
commit 6a86cb10528a8f8397cdcf1821d28e0e2c2e8161
Merge: c6c122eb6 613790d1f
Author: Xi Ruoyao <[email protected]>
AuthorDate: Tue Feb 18 20:56:06 2025 +0800
Merge remote-tracking branch 'origin/trunk' into xry111/arm64
appendices/dependencies.xml | 12 +-
chapter01/changelog.xml | 427 ++++++++++++++++++++++++++++++++++++++
chapter01/whatsnew.xml | 121 +++++------
chapter02/aboutlfs.xml | 55 +++--
chapter02/hostreqs.xml | 2 +-
chapter02/mounting.xml | 9 +
chapter02/stages.xml | 3 +-
chapter03/introduction.xml | 5 +-
chapter03/patches.xml | 6 +-
chapter04/addinguser.xml | 10 +-
chapter04/settingenviron.xml | 7 +-
chapter05/glibc.xml | 4 +-
chapter06/bash.xml | 3 +-
chapter06/binutils-pass2.xml | 2 +-
chapter07/changingowner.xml | 2 +-
chapter07/createfiles.xml | 4 +-
chapter08/acl.xml | 11 +-
chapter08/bash.xml | 1 -
chapter08/binutils.xml | 29 +--
chapter08/coreutils.xml | 29 ++-
chapter08/dbus.xml | 56 ++---
chapter08/e2fsprogs.xml | 2 +-
chapter08/flit-core.xml | 4 +-
chapter08/gawk.xml | 3 +-
chapter08/gettext.xml | 8 +
chapter08/glibc.xml | 17 +-
chapter08/grub.xml | 2 +-
chapter08/iproute2.xml | 5 +-
chapter08/jinja2.xml | 4 +-
chapter08/libtool.xml | 8 +-
chapter08/markupsafe.xml | 2 +-
chapter08/ninja.xml | 14 +-
chapter08/perl.xml | 5 -
chapter08/procps.xml | 19 +-
chapter08/python.xml | 17 +-
chapter08/readline.xml | 6 +-
chapter08/setuptools.xml | 2 +-
chapter08/shadow.xml | 37 ++--
chapter08/sysklogd.xml | 3 +-
chapter08/systemd.xml | 5 +-
chapter08/tcl.xml | 4 +-
chapter08/udev.xml | 10 +-
chapter08/util-linux.xml | 5 +
chapter08/vim.xml | 6 +-
chapter08/wheel.xml | 2 +-
chapter10/grub.xml | 9 +
chapter10/kernel.xml | 102 +++++++--
chapter10/kernel/kernel.version | 2 +-
chapter10/kernel/systemd.toml | 16 +-
chapter10/kernel/systemd.xml | 14 +-
chapter10/kernel/sysv.toml | 16 +-
chapter10/kernel/sysv.xml | 15 +-
chapter11/afterlfs.xml | 4 +-
chapter11/theend.xml | 1 +
general.ent | 13 +-
lfs-latest-git.php | 36 ++--
packages.ent | 411 ++++++++++++++++++------------------
part3intro/toolchaintechnotes.xml | 2 +-
patches.ent | 11 +-
prologue/standards.xml | 4 +-
60 files changed, 1112 insertions(+), 532 deletions(-)
diff --cc chapter04/addinguser.xml
index eed85c569,e1d130b95..92ae1a881
--- a/chapter04/addinguser.xml
+++ b/chapter04/addinguser.xml
@@@ -80,7 -80,10 +80,7 @@@ useradd -s /bin/bash -g &lfs-groupname
all the directories under <filename class="directory">$LFS</filename> by making
<systemitem class="username">lfs</systemitem> the owner:</para>
- <screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}</userinput></screen>
-<screen><userinput>chown -v &lfs-username; $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}
-case $(uname -m) in
- x86_64) chown -v &lfs-username; $LFS/lib64 ;;
-esac</userinput></screen>
++<screen><userinput>chown -v &lfs-username; $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}</userinput></screen>
<note><para>In some host systems, the following <command>su</command> command does not complete
properly and suspends the login for the &lfs-user; user to the background.
diff --cc chapter07/changingowner.xml
index 66cb25b72,178c7836e..1e1a0ea1e
--- a/chapter07/changingowner.xml
+++ b/chapter07/changingowner.xml
@@@ -33,6 -33,9 +33,6 @@@
user <systemitem class="username">root</systemitem> by running the following
command:</para>
- <screen><userinput>chown -R --from lfs root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}</userinput></screen>
-<screen><userinput>chown --from &lfs-username; -R root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}
-case $(uname -m) in
- x86_64) chown --from &lfs-username; -R root:root $LFS/lib64 ;;
-esac</userinput></screen>
++<screen><userinput>chown -R --from &lfs-username; root:root $LFS/{usr,lib,var,etc,bin,sbin,tools}</userinput></screen>
</sect1>
diff --cc chapter10/grub.xml
index ee708d3f0,00be1d6c0..186dbae8e
--- a/chapter10/grub.xml
+++ b/chapter10/grub.xml
@@@ -186,9 -135,8 +186,10 @@@ set timeout=
insmod part_gpt
insmod ext2
set root=(hd0,2)
+ set gfxpayload=1024x768x32
+insmod efi_gop
+
menuentry "GNU/Linux, Linux &linux-version;-lfs-&version;" {
linux /boot/vmlinuz-&linux-version;-lfs-&version; root=/dev/sda2 ro
}</literal>
diff --cc chapter10/kernel.xml
index f368f1b66,327e3de60..856efa75c
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@@ -255,15 -272,71 +255,80 @@@
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><parameter>Enable the generic EFI decompressor</parameter></term>
+ <listitem>
+ <para>Create the bootable image as an EFI application that carries
+ the actual kernel image in compressed form. It can make the
+ bootable image 50% smaller.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <parameter>
+ Display a user-friendly message when a kernel panic occurs
+ </parameter>
+ </term>
+ <listitem>
+ <para>This will make the kernel correctly display the message
+ in case a kernel panic happens and a running DRM driver
+ supports to do so. Without this, it would be more
+ difficult to diagnose a panic: if no DRM driver is running,
+ we'd be on the VGA console which can only hold 24 lines and
+ the relevant kernel message is often flushed away; if a DRM
+ driver is running, the display is often completely messed up
+ on panic. As of Linux-6.12, none of the dedicated drivers for
+ mainstream GPU models really supports this, but it's supported by
+ the <quote>Simple framebuffer driver</quote> which runs on the
+ VESA (or EFI) framebuffer before the dedicated GPU driver is
+ loaded. If the dedicated GPU driver is built as a module
+ (instead of a part of the kernel image) and no initramfs is
+ used, this functionality will work just fine before the root
+ file system is mounted and it's already enough for providing
+ information about most LFS configuration errors causing a
+ panic (for example, an incorrect <parameter>root=</parameter>
+ setting in <xref linkend='ch-bootable-grub'/>).</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <parameter>
+ Panic screen formatter
+ </parameter>
+ </term>
+ <listitem>
+ <para>Set this <literal>kmsg</literal> to make sure the last
+ kernel messages lines are displayed when a kernel panic happens.
+ The default, <literal>user</literal>, would make the kernel show
+ only a <quote>user friendly</quote> panic message which is not
+ helpful on diagnostic. The third choice,
+ <literal>qr_code</literal>, would make the kernel to compress
+ the last kernel message lines into a QR code and display it.
+ The QR code can hold more message lines than plain text and it
+ can be decoded with an external device (like a smart phone).
+ But it requires a Rust compiler that LFS does not provide.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
+ <parameter>
+ Mark VGA/VBE/EFI FB as generic system framebuffer
+ </parameter> and
+ <parameter>Simple framebuffer driver</parameter>
+ </term>
+ <listitem>
+ <para>These allow to use the VESA framebuffer (or the EFI
+ framebuffer if booting the LFS system via UEFI) as a DRM device.
+ The VESA framebuffer will be set up by GRUB (or the EFI
+ framebuffer will be set up by the UEFI firmware), so the DRM panic
+ handler can function before the GPU-specific DRM driver is
+ loaded.</para>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term>
<parameter>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
--
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page