gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 19:59:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

Browse Source
This commit is contained in:
Xi Ruoyao 2023-01-06 12:57:22 +08:00
commit 0cbb853d3c
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
12 changed files with 233 additions and 170 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

60
appendices/dependencies.xml
View File

@ -1474,37 +1474,37 @@
</segmentedlist> </segmentedlist>
<!-- Begin Jinja2 dependency info --> <!-- Begin Jinja2 dependency info -->
<bridgehead renderas="sect2" id="jinja2-dep">Jinja2</bridgehead> <bridgehead revision='systemd' renderas="sect2" id="jinja2-dep">Jinja2</bridgehead>
<segmentedlist id="jinja2-depends"> <segmentedlist id="jinja2-depends" revision='systemd'>
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
<seglistitem> <seglistitem>
<seg>MarkupSafe and Python</seg> <seg>MarkupSafe and Python</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="jinja2-rundeps"> <segmentedlist id="jinja2-rundeps" revision='systemd'>
<segtitle>&runtime;</segtitle> <segtitle>&runtime;</segtitle>
<seglistitem> <seglistitem>
<seg>MarkupSafe and Python</seg> <seg>MarkupSafe and Python</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="jinja2-testdeps"> <segmentedlist id="jinja2-testdeps" revision='systemd'>
<segtitle>&testsuites;</segtitle> <segtitle>&testsuites;</segtitle>
<seglistitem> <seglistitem>
<seg>No test suite available</seg> <seg>No test suite available</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="jinja2-before"> <segmentedlist id="jinja2-before" revision='systemd'>
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>Systemd</seg> <seg>Systemd</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="jinja2-optdeps"> <segmentedlist id="jinja2-optdeps" revision='systemd'>
<segtitle>&external;</segtitle> <segtitle>&external;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
@ -2071,37 +2071,37 @@
</segmentedlist> </segmentedlist>
<!-- Begin MarkupSafe dependency info --> <!-- Begin MarkupSafe dependency info -->
<bridgehead renderas="sect2" id="markupsafe-dep">MarkupSafe</bridgehead> <bridgehead renderas="sect2" id="markupsafe-dep" revision='systemd'>MarkupSafe</bridgehead>
<segmentedlist id="markupsafe-depends"> <segmentedlist id="markupsafe-depends" revision='systemd'>
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
<seglistitem> <seglistitem>
<seg>Python</seg> <seg>Python</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="markupsafe-rundeps"> <segmentedlist id="markupsafe-rundeps" revision='systemd'>
<segtitle>&runtime;</segtitle> <segtitle>&runtime;</segtitle>
<seglistitem> <seglistitem>
<seg>Python</seg> <seg>Python</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="markupsafe-testdeps"> <segmentedlist id="markupsafe-testdeps" revision='systemd'>
<segtitle>&testsuites;</segtitle> <segtitle>&testsuites;</segtitle>
<seglistitem> <seglistitem>
<seg>No test suite available</seg> <seg>No test suite available</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="markupsafe-before"> <segmentedlist id="markupsafe-before" revision='systemd'>
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>Jinja2</seg> <seg>Jinja2</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="markupsafe-optdeps"> <segmentedlist id="markupsafe-optdeps" revision='systemd'>
<segtitle>&external;</segtitle> <segtitle>&external;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
@ -2135,7 +2135,10 @@
<segmentedlist id="meson-before"> <segmentedlist id="meson-before">
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>Systemd</seg> <seg>
<phrase revision='sysv'>None</phrase>
<phrase revision='systemd'>Systemd</phrase>
</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
@ -2749,9 +2752,9 @@
</segmentedlist> </segmentedlist>
<!-- Begin systemd dependency info --> <!-- Begin systemd dependency info -->
<bridgehead renderas="sect2" id="systemd-dep">Systemd</bridgehead> <bridgehead renderas="sect2" id="systemd-dep" revision='systemd'>Systemd</bridgehead>
<segmentedlist id="systemd-depends"> <segmentedlist id="systemd-depends" revision='systemd'>
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
<seglistitem> <seglistitem>
<seg>Acl, Attr, Bash, Binutils, Coreutils, Diffutils, Expat, Gawk, <seg>Acl, Attr, Bash, Binutils, Coreutils, Diffutils, Expat, Gawk,
@ -2760,28 +2763,28 @@
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="systemd-rundeps"> <segmentedlist id="systemd-rundeps" revision='systemd'>
<segtitle>&runtime;</segtitle> <segtitle>&runtime;</segtitle>
<seglistitem> <seglistitem>
<seg>Acl, Attr, Glibc, Libcap, and Util-linux</seg> <seg>Acl, Attr, Glibc, Libcap, and Util-linux</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="systemd-testdeps"> <segmentedlist id="systemd-testdeps" revision='systemd'>
<segtitle>&testsuites;</segtitle> <segtitle>&testsuites;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="systemd-before"> <segmentedlist id="systemd-before" revision='systemd'>
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="systemd-optdeps"> <segmentedlist id="systemd-optdeps" revision='systemd'>
<segtitle>&external;</segtitle> <segtitle>&external;</segtitle>
<seglistitem> <seglistitem>
<seg> <seg>
@ -2836,37 +2839,37 @@
</segmentedlist> </segmentedlist>
<!-- Begin Sysvinit dependency info --> <!-- Begin Sysvinit dependency info -->
<bridgehead renderas="sect2" id="sysvinit-dep">Sysvinit</bridgehead> <bridgehead renderas="sect2" id="sysvinit-dep" revision='sysv'>Sysvinit</bridgehead>
<segmentedlist id="sysvinit-depends"> <segmentedlist id="sysvinit-depends" revision='sysv'>
<segtitle>&dependencies;</segtitle> <segtitle>&dependencies;</segtitle>
<seglistitem> <seglistitem>
<seg>Binutils, Coreutils, GCC, Glibc, Make, and Sed</seg> <seg>Binutils, Coreutils, GCC, Glibc, Make, and Sed</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="sysvinit-rundeps"> <segmentedlist id="sysvinit-rundeps" revision='sysv'>
<segtitle>&runtime;</segtitle> <segtitle>&runtime;</segtitle>
<seglistitem> <seglistitem>
<seg>Glibc</seg> <seg>Glibc</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="sysvinit-testdeps"> <segmentedlist id="sysvinit-testdeps" revision='sysv'>
<segtitle>&testsuites;</segtitle> <segtitle>&testsuites;</segtitle>
<seglistitem> <seglistitem>
<seg>No test suite available</seg> <seg>No test suite available</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="sysvinit-before"> <segmentedlist id="sysvinit-before" revision='sysv'>
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
<segmentedlist id="sysvinit-optdeps"> <segmentedlist id="sysvinit-optdeps" revision='sysv'>
<segtitle>&external;</segtitle> <segtitle>&external;</segtitle>
<seglistitem> <seglistitem>
<seg>None</seg> <seg>None</seg>
@ -3109,7 +3112,10 @@
<segmentedlist id="wheel-before"> <segmentedlist id="wheel-before">
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>Jinja2</seg> <seg>
<phrase revision='sysv'>None</phrase>
<phrase revision='systemd'>Jinja2</phrase>
</seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>
@ -3262,7 +3268,7 @@
<segmentedlist id="zstd-before"> <segmentedlist id="zstd-before">
<segtitle>&before;</segtitle> <segtitle>&before;</segtitle>
<seglistitem> <seglistitem>
<seg>GCC and Systemd</seg> <seg>GCC <phrase revision='systemd'>and Systemd</phrase></seg>
</seglistitem> </seglistitem>
</segmentedlist> </segmentedlist>

57
chapter01/changelog.xml
View File

@ -39,6 +39,63 @@
<listitem revision="sysv"> or <listitem revision="systemd"> as <listitem revision="sysv"> or <listitem revision="systemd"> as
appropriate for the entry or if needed the entire day's listitem. appropriate for the entry or if needed the entire day's listitem.
--> -->
<listitem>
<para>2023-01-01</para><!-- Happy New Year! -->
<itemizedlist>
<listitem>
<para>[thomas] - Remove an obsolete sed from mpc.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>2022-12-31</para>
<itemizedlist>
<listitem>
<para>[bdubbs] - Update to iana-etc-20221220. Addresses
<ulink url="&lfs-ticket-root;5006">#5006</ulink>.</para>
</listitem>
<listitem revision="sysv">
<para>[bdubbs] - Update to sysvinit-3.06. Fixes
<ulink url="&lfs-ticket-root;5186">#5186</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to mpc-1.3.1. Fixes
<ulink url="&lfs-ticket-root;5185">#5185</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to meson-1.0.0. Fixes
<ulink url="&lfs-ticket-root;5190">#5190</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to man-pages-6.02. Fixes
<ulink url="&lfs-ticket-root;5188">#5188</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to linux-6.1.1. Fixes
<ulink url="&lfs-ticket-root;5179">#5179</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to file-5.44. Fixes
<ulink url="&lfs-ticket-root;5191">#5191</ulink>.</para>
</listitem>
<listitem>
<para>[bdubbs] - Update to bc-6.2.1. Fixes
<ulink url="&lfs-ticket-root;5189">#5189</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem revision="systemd">
<para>2022-12-28</para>
<itemizedlist>
<listitem>
<para>[renodr] - Patch systemd against CVE-2022-4415. Fixes
<ulink url="&lfs-ticket-root;5187">#5187</ulink>.</para>
</listitem>
</itemizedlist>
</listitem>
<listitem> <listitem>
<para>2022-12-15</para> <para>2022-12-15</para>
<itemizedlist> <itemizedlist>

4
chapter01/whatsnew.xml
View File

@ -299,6 +299,10 @@
<listitem> <listitem>
<para>&readline-fixes-patch;</para> <para>&readline-fixes-patch;</para>
</listitem> </listitem>
<listitem revision="systemd">
<para>&systemd-upstream-patch;</para>
</listitem>
</itemizedlist> </itemizedlist>
<itemizedlist> <itemizedlist>

4
chapter03/patches.xml
View File

@ -135,7 +135,7 @@
</listitem> </listitem>
</varlistentry> </varlistentry>
<!--
<varlistentry revision="systemd"> <varlistentry revision="systemd">
<term>Systemd Upstream Patch - <token>&systemd-upstream-patch-size;</token>:</term> <term>Systemd Upstream Patch - <token>&systemd-upstream-patch-size;</token>:</term>
<listitem> <listitem>
@ -143,7 +143,7 @@
<para>MD5 sum: <literal>&systemd-upstream-patch-md5;</literal></para> <para>MD5 sum: <literal>&systemd-upstream-patch-md5;</literal></para>
</listitem> </listitem>
</varlistentry> </varlistentry>
-->
<!-- <!--
<varlistentry> <varlistentry>
<term>Xz Upstream Fix Patch - <token>&xz-upstream-fix-patch-size;</token>:</term> <term>Xz Upstream Fix Patch - <token>&xz-upstream-fix-patch-size;</token>:</term>

12
chapter08/mpc.xml
View File

@ -42,18 +42,6 @@
<sect2 role="installation"> <sect2 role="installation">
<title>Installation of MPC</title> <title>Installation of MPC</title>
<para>First, make a fix identified upstream:</para>
<screen><userinput remap="pre">sed -i '273{ h; d; }; 274,286 { H; d; }; 287 G' src/mpc.h</userinput></screen>
<note>
<para>This sed is a little complex and needs some explanation. It holds
the line 273 in a buffer, adds lines 274-286 to it. It then writes the
buffer out after line 287 is read. The result is that the line 287 is
moved upwards from an incorrect location to its correct location in an
#ifdef block.</para>
</note>
<para>Prepare MPC for compilation:</para> <para>Prepare MPC for compilation:</para>
<screen><userinput remap="configure">./configure --prefix=/usr \ <screen><userinput remap="configure">./configure --prefix=/usr \

6
chapter08/systemd.xml
View File

@ -40,11 +40,11 @@
<sect2 role="installation"> <sect2 role="installation">
<title>Installation of systemd</title> <title>Installation of systemd</title>
<!--
<para>First, fix an issue introduced by glibc-2.36.</para> <para>First, fix a security issue in systemd-coredump:</para>
<screen><userinput remap="pre">patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen> <screen><userinput remap="pre">patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen>
-->
<para>Remove two unneeded groups, <para>Remove two unneeded groups,
<systemitem class="groupname">render</systemitem> and <systemitem class="groupname">render</systemitem> and

29
chapter09/profile.xml
View File

@ -16,10 +16,10 @@
<para>The shell program <command>/bin/bash</command> (hereafter referred to <para>The shell program <command>/bin/bash</command> (hereafter referred to
as <quote>the shell</quote>) uses a collection of startup files to help as <quote>the shell</quote>) uses a collection of startup files to help
create an environment to run in. Each file has a specific use and may affect create the environment to run in. Each file has a specific use and may affect
login and interactive environments differently. The files in the <filename login and interactive environments differently. The files in the <filename
class="directory">/etc</filename> directory provide global settings. If an class="directory">/etc</filename> directory provide global settings. If
equivalent file exists in the home directory, it may override the global equivalent files exist in the home directory, they may override the global
settings.</para> settings.</para>
<para>An interactive login shell is started after a successful login, using <para>An interactive login shell is started after a successful login, using
@ -30,8 +30,9 @@
because it is processing a script and not waiting for user input between because it is processing a script and not waiting for user input between
commands.</para> commands.</para>
<para>For more information, see <command>info bash</command> under the <para>For more information, see the <emphasis>Bash Startup Files</emphasis> and
<emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para> <emphasis>Interactive Shells</emphasis> sections in the <emphasis>Bash
Features</emphasis> chapter of the Bash info pages (<command>info bash</command>).</para>
<para>The files <filename>/etc/profile</filename> and <para>The files <filename>/etc/profile</filename> and
<filename>~/.bash_profile</filename> are read when the shell is <filename>~/.bash_profile</filename> are read when the shell is
@ -91,8 +92,8 @@
<screen><computeroutput>ISO-8859-1</computeroutput></screen> <screen><computeroutput>ISO-8859-1</computeroutput></screen>
<para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>. <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
It is important that the locale found using the heuristic above is tested prior It is important that the locale found using the heuristic above is tested before
to it being added to the Bash startup files:</para> it is added to the Bash startup files:</para>
<screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language <screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language
LC_ALL=&lt;locale name&gt; locale charmap LC_ALL=&lt;locale name&gt; locale charmap
@ -129,9 +130,9 @@ LC_ALL=&lt;locale name&gt; locale int_prefix</userinput></screen>
For example, one would have to change "de_DE.ISO-8859-15@euro" to For example, one would have to change "de_DE.ISO-8859-15@euro" to
"de_DE@euro" in order to get this locale recognized by Xlib.</para> "de_DE@euro" in order to get this locale recognized by Xlib.</para>
--> -->
<para>Other packages can also function incorrectly (but may not necessarily <para>Other packages may also function incorrectly (but will not necessarily
display any error messages) if the locale name does not meet their expectations. display any error messages) if the locale name does not meet their expectations.
In those cases, investigating how other Linux distributions support your locale In such cases, investigating how other Linux distributions support your locale
might provide some useful information.</para> might provide some useful information.</para>
<para>Once the proper locale settings have been determined, create the <para>Once the proper locale settings have been determined, create the
@ -147,16 +148,16 @@ EOF</userinput></screen>
<para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended
one for United States English users) locales are different. <quote>C</quote> one for United States English users) locales are different. <quote>C</quote>
uses the US-ASCII 7-bit character set, and treats bytes with the high bit set uses the US-ASCII 7-bit character set, and treats bytes with the high-order bit set
as invalid characters. That's why, e.g., the <command>ls</command> command <quote>on</quote> as invalid characters. That's why, e.g., the <command>ls</command> command
substitutes them with question marks in that locale. Also, an attempt to send displays them as question marks in that locale. Also, an attempt to send
mail with such characters from Mutt or Pine results in non-RFC-conforming mail with such characters from Mutt or Pine results in non-RFC-conforming
messages being sent (the charset in the outgoing mail is indicated as <quote>unknown messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that 8-bit</quote>). So you can only use the <quote>C</quote> locale if you are sure
you will never need 8-bit characters.</para> you will never need 8-bit characters.</para>
<para>UTF-8 based locales are not supported well by some programs. <para>UTF-8 based locales are not supported well by some programs.
Work is in progress to document and, if possible, fix such problems, see Work is in progress to document and, if possible, fix such problems. See
<ulink url="&blfs-book;introduction/locale-issues.html"/>.</para> <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para>
</sect1> </sect1>

130
chapter09/usage.xml
View File

@ -19,25 +19,29 @@
<sect2> <sect2>
<title>How Do the System V Bootscripts Work?</title> <title>How Do the System V Bootscripts Work?</title>
<para>Linux uses a special booting facility named SysVinit that is based on a <para>This version of LFS uses a special booting facility named SysVinit, based on a
concept of <emphasis>run-levels</emphasis>. It can be quite different from one series of <emphasis>run levels</emphasis>. The boot procedure can be quite different from one
system to another, so it cannot be assumed that because things worked in one system to another; the fact that things worked one way in a particular Linux
particular Linux distribution, they should work the same in LFS too. LFS has its distribution does not guarantee they will work the same way in LFS. LFS has its
own way of doing things, but it respects generally accepted standards.</para> own way of doing things, but it does respect generally accepted standards.</para>
<para>There is an alternative boot procedure called <command>systemd</command>. We will
not discuss that boot process any further here. For a detailed description visit
<ulink url="https://www.linux.com/training-tutorials/understanding-and-using-systemd/"/>.</para>
<para>SysVinit (which will be referred to as <quote>init</quote> from now on) <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels uses a run levels scheme. There are seven run levels, numbered 0 to 6.
(actually, there are more run-levels, but they are for special cases and are (Actually, there are more run levels, but the others are for special cases and are
generally not used. See <filename>init(8)</filename> for more details), and generally not used. See <filename>init(8)</filename> for more details.)
each one of those corresponds to the actions the computer is supposed to Each one of the seven corresponds to actions the computer is supposed to
perform when it starts up. The default run-level is 3. Here are the perform when it starts up or shuts down. The default run level is 3. Here are the
descriptions of the different run-levels as they are implemented in LFS:</para> descriptions of the different run levels as they are implemented in LFS:</para>
<literallayout>0: halt the computer <literallayout>0: halt the computer
1: single-user mode 1: single-user mode
2: reserved for customization, otherwise does the same as 3 2: reserved for customization, otherwise the same as 3
3: multi-user mode with networking 3: multi-user mode with networking
4: reserved for customization, otherwise does the same as 3 4: reserved for customization, otherwise the same as 3
5: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>) 5: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>)
6: reboot the computer</literallayout> 6: reboot the computer</literallayout>
@ -45,9 +49,9 @@
<para> <para>
Classically, run level 2 above was defined as Classically, run level 2 above was defined as
"multi-user mode without networking", but this was only the case "multi-user mode without networking", but this was only the case
many years ago when multiple users could log into a system connected via many years ago when multiple users could connect to a system via
serial ports. In today's environment it makes no sense and serial ports. In today's environment it makes no sense, and
we designate it now as "reserved". we now say it is "reserved".
</para> </para>
</note> </note>
@ -65,8 +69,8 @@
<primary sortas="e-/etc/inittab">/etc/inittab</primary> <primary sortas="e-/etc/inittab">/etc/inittab</primary>
</indexterm> </indexterm>
<para>During the kernel initialization, the first program that is run <para>During kernel initialization, the first program that is run
is either specified on the command line or, by default (if not overridden on the command line) is
<command>init</command>. This program reads the initialization file <command>init</command>. This program reads the initialization file
<filename>/etc/inittab</filename>. Create this file with:</para> <filename>/etc/inittab</filename>. Create this file with:</para>
@ -101,8 +105,8 @@ s1:1:respawn:/sbin/sulogin
EOF</userinput></screen> EOF</userinput></screen>
<para>An explanation of this initialization file is in the man page for <para>An explanation of this initialization file is in the man page for
<emphasis>inittab</emphasis>. For LFS, the key command that is run is <emphasis>inittab</emphasis>. In LFS, the key command is
<command>rc</command>. The initialization file above will instruct <command>rc</command>. The initialization file above instructs
<command>rc</command> to run all the scripts starting with an S in the <command>rc</command> to run all the scripts starting with an S in the
<filename class="directory">/etc/rc.d/rcS.d</filename> directory <filename class="directory">/etc/rc.d/rcS.d</filename> directory
followed by all the scripts starting with an S in the <filename followed by all the scripts starting with an S in the <filename
@ -113,22 +117,22 @@ EOF</userinput></screen>
functions in <filename class="directory">/lib/lsb/init-functions</filename>. functions in <filename class="directory">/lib/lsb/init-functions</filename>.
This library also reads an optional configuration file, This library also reads an optional configuration file,
<filename>/etc/sysconfig/rc.site</filename>. Any of the system <filename>/etc/sysconfig/rc.site</filename>. Any of the system
configuration file parameters described in subsequent sections can be configuration parameters described in subsequent sections can be
alternatively placed in this file allowing consolidation of all system placed in this file, allowing consolidation of all system
parameters in this one file.</para> parameters in this one file.</para>
<para>As a debugging convenience, the functions script also logs all output <para>As a debugging convenience, the functions script also logs all output
to <filename>/run/var/bootlog</filename>. Since the <filename to <filename>/run/var/bootlog</filename>. Since the <filename
class="directory">/run</filename> directory is a tmpfs, this file is not class="directory">/run</filename> directory is a tmpfs, this file is not
persistent across boots, however it is appended to the more permanent file persistent across boots; however, it is appended to the more permanent file
<filename>/var/log/boot.log</filename> at the end of the boot process.</para> <filename>/var/log/boot.log</filename> at the end of the boot process.</para>
<sect3 id="init-levels" > <sect3 id="init-levels" >
<title>Changing Run Levels</title> <title>Changing Run Levels</title>
<para>Changing run-levels is done with <command>init <para>Changing run levels is done with <command>init
<replaceable>&lt;runlevel&gt;</replaceable></command>, where <replaceable>&lt;runlevel&gt;</replaceable></command>, where
<replaceable>&lt;runlevel&gt;</replaceable> is the target run-level. For example, to <replaceable>&lt;runlevel&gt;</replaceable> is the target run level. For example, to
reboot the computer, a user could issue the <command>init 6</command> command, reboot the computer, a user could issue the <command>init 6</command> command,
which is an alias for the <command>reboot</command> command. Likewise, which is an alias for the <command>reboot</command> command. Likewise,
<command>init 0</command> is an alias for the <command>halt</command> <command>init 0</command> is an alias for the <command>halt</command>
@ -136,15 +140,15 @@ EOF</userinput></screen>
<para>There are a number of directories under <filename <para>There are a number of directories under <filename
class="directory">/etc/rc.d</filename> that look like <filename class="directory">/etc/rc.d</filename> that look like <filename
class="directory">rc?.d</filename> (where ? is the number of the run-level) and class="directory">rc?.d</filename> (where ? is the number of the run level) and
<filename class="directory">rcS.d</filename>, all containing a number of <filename class="directory">rcS.d</filename>, all containing a number of
symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with symbolic links. Some links begin with a <emphasis>K</emphasis>; the others begin with
an <emphasis>S</emphasis>, and all of them have two numbers following the an <emphasis>S</emphasis>, and all of them have two numbers following the
initial letter. The K means to stop (kill) a service and the S means to start a initial letter. The K means to stop (kill) a service and the S means to start a
service. The numbers determine the order in which the scripts are run, from 00 service. The numbers determine the order in which the scripts are run, from 00
to 99&mdash;the lower the number the earlier it gets executed. When to 99&mdash;the smaller the number, the sooner tht script runs. When
<command>init</command> switches to another run-level, the appropriate services <command>init</command> switches to another run level, the appropriate services
are either started or stopped, depending on the runlevel chosen.</para> are either started or stopped, depending on the run level chosen.</para>
<para>The real scripts are in <filename <para>The real scripts are in <filename
class="directory">/etc/rc.d/init.d</filename>. They do the actual work, and class="directory">/etc/rc.d/init.d</filename>. They do the actual work, and
@ -227,25 +231,25 @@ EOF</userinput></screen>
<para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts <para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts
<command>udevd</command>, triggers any "coldplug" devices that have <command>udevd</command>, triggers any "coldplug" devices that have
already been created by the kernel and waits for any rules to complete. already been created by the kernel, and waits for any rules to complete.
The script also unsets the uevent handler from the default of The script also unsets the uevent handler from the default of
<filename>/sbin/hotplug </filename>. This is done because the kernel no <filename>/sbin/hotplug </filename>. This is done because the kernel no
longer needs to call out to an external binary. Instead longer needs to call an external binary. Instead,
<command>udevd</command> will listen on a netlink socket for uevents that <command>udevd</command> will listen on a netlink socket for uevents that
the kernel raises.</para> the kernel raises.</para>
<para>The <command>/etc/rc.d/init.d/udev_retry</command> initscript takes <para>The <command>/etc/rc.d/init.d/udev_retry</command> script takes
care of re-triggering events for subsystems whose rules may rely on care of re-triggering events for subsystems whose rules may rely on
filesystems that are not mounted until the <command>mountfs</command> file systems that are not mounted until the <command>mountfs</command>
script is run (in particular, <filename class="directory">/usr</filename> script is run (in particular, <filename class="directory">/usr</filename>
and <filename class="directory">/var</filename> may cause this). This and <filename class="directory">/var</filename> may cause this). This
script runs after the <command>mountfs</command> script, so those rules script runs after the <command>mountfs</command> script, so those rules
(if re-triggered) should succeed the second time around. It is (if re-triggered) should succeed the second time around. It is
configured from the <filename>/etc/sysconfig/udev_retry</filename> file; configured by the <filename>/etc/sysconfig/udev_retry</filename> file;
any words in this file other than comments are considered subsystem names any words in this file other than comments are considered subsystem names
to trigger at retry time. To find the subsystem of a device, use to trigger at retry time. To find the subsystem of a device, use
<command>udevadm info --attribute-walk &lt;device&gt;</command> where <command>udevadm info --attribute-walk &lt;device&gt;</command> where
&lt;device&gt; is an absolute path in /dev or /sys such as /dev/sr0 or &lt;device&gt; is an absolute path in /dev or /sys, such as /dev/sr0, or
/sys/class/rtc.</para> /sys/class/rtc.</para>
<para>For information on kernel module loading and udev, see <para>For information on kernel module loading and udev, see
@ -260,13 +264,13 @@ EOF</userinput></screen>
<secondary>configuring</secondary></indexterm> <secondary>configuring</secondary></indexterm>
<para>The <command>setclock</command> script reads the time from the hardware <para>The <command>setclock</command> script reads the time from the hardware
clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor clock, also known as the BIOS or Complementary Metal Oxide Semiconductor
(CMOS) clock. If the hardware clock is set to UTC, this script will convert the (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
hardware clock's time to the local time using the hardware clock's time to the local time using the
<filename>/etc/localtime</filename> file (which tells the <filename>/etc/localtime</filename> file (which tells the
<command>hwclock</command> program which timezone to use). There is no <command>hwclock</command> program which time zone to use). There is no
way to detect whether or not the hardware clock is set to UTC, so this way to detect whether or not the hardware clock is set to UTC, so this
needs to be configured manually.</para> must be configured manually.</para>
<para>The <command>setclock</command> program is run via <para>The <command>setclock</command> program is run via
<application>udev</application> when the kernel detects the hardware <application>udev</application> when the kernel detects the hardware
@ -279,9 +283,9 @@ EOF</userinput></screen>
clock. If this time matches whatever your watch says, then the hardware clock is clock. If this time matches whatever your watch says, then the hardware clock is
set to local time. If the output from <command>hwclock</command> is not local set to local time. If the output from <command>hwclock</command> is not local
time, chances are it is set to UTC time. Verify this by adding or subtracting time, chances are it is set to UTC time. Verify this by adding or subtracting
the proper amount of hours for the timezone to the time shown by the proper number of hours for your time zone to the time shown by
<command>hwclock</command>. For example, if you are currently in the MST <command>hwclock</command>. For example, if you are currently in the MST
timezone, which is also known as GMT -0700, add seven hours to the local time zone, which is also known as GMT -0700, add seven hours to the local
time.</para> time.</para>
<para>Change the value of the <envar>UTC</envar> variable below <para>Change the value of the <envar>UTC</envar> variable below
@ -325,7 +329,7 @@ EOF</userinput></screen>
<para>This section discusses how to configure the <command>console</command> <para>This section discusses how to configure the <command>console</command>
bootscript that sets up the keyboard map, console font, and console kernel log bootscript that sets up the keyboard map, console font, and console kernel log
level. If non-ASCII characters (e.g., the copyright sign, the British pound level. If non-ASCII characters (e.g., the copyright sign, the British pound
sign and Euro symbol) will not be used and the keyboard is a U.S. one, much sign, and the Euro symbol) will not be used and the keyboard is a U.S. one, much
of this section can be skipped. Without the configuration file, (or of this section can be skipped. Without the configuration file, (or
equivalent settings in <filename>rc.site</filename>), the equivalent settings in <filename>rc.site</filename>), the
<command>console</command> bootscript will do nothing.</para> <command>console</command> bootscript will do nothing.</para>
@ -333,11 +337,11 @@ EOF</userinput></screen>
<para>The <command>console</command> script reads the <para>The <command>console</command> script reads the
<filename>/etc/sysconfig/console</filename> file for configuration <filename>/etc/sysconfig/console</filename> file for configuration
information. Decide which keymap and screen font will be used. Various information. Decide which keymap and screen font will be used. Various
language-specific HOWTOs can also help with this, see <ulink language-specific HOWTOs can also help with this; see <ulink
url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
doubt, look in the <filename class="directory">/usr/share/keymaps</filename> doubt, look in the <filename class="directory">/usr/share/keymaps</filename>
and <filename class="directory">/usr/share/consolefonts</filename> directories and <filename class="directory">/usr/share/consolefonts</filename> directories
for valid keymaps and screen fonts. Read <filename>loadkeys(1)</filename> and for valid keymaps and screen fonts. Read the <filename>loadkeys(1)</filename> and
<filename>setfont(8)</filename> manual pages to determine the correct <filename>setfont(8)</filename> manual pages to determine the correct
arguments for these programs.</para> arguments for these programs.</para>
@ -358,7 +362,7 @@ EOF</userinput></screen>
<term>KEYMAP</term> <term>KEYMAP</term>
<listitem> <listitem>
<para>This variable specifies the arguments for the <para>This variable specifies the arguments for the
<command>loadkeys</command> program, typically, the name of keymap <command>loadkeys</command> program, typically, the name of the keymap
to load, e.g., <quote>it</quote>. If this variable is not set, the to load, e.g., <quote>it</quote>. If this variable is not set, the
bootscript will not run the <command>loadkeys</command> program, bootscript will not run the <command>loadkeys</command> program,
and the default kernel keymap will be used. Note that a few keymaps and the default kernel keymap will be used. Note that a few keymaps
@ -390,11 +394,11 @@ EOF</userinput></screen>
name, <quote>-m</quote>, and the name of the application character name, <quote>-m</quote>, and the name of the application character
map to load. E.g., in order to load the <quote>lat1-16</quote> font map to load. E.g., in order to load the <quote>lat1-16</quote> font
together with the <quote>8859-1</quote> application character map together with the <quote>8859-1</quote> application character map
(as it is appropriate in the USA), (appropriate in the USA),
<!-- because of the copyright sign --> <!-- because of the copyright sign -->
set this variable to <quote>lat1-16 -m 8859-1</quote>. set this variable to <quote>lat1-16 -m 8859-1</quote>.
In UTF-8 mode, the kernel uses the application character map for In UTF-8 mode, the kernel uses the application character map to
conversion of composed 8-bit key codes in the keymap to UTF-8, and thus convert 8-bit key codes to UTF-8. Therefore
the argument of the "-m" parameter should be set to the encoding of the the argument of the "-m" parameter should be set to the encoding of the
composed key codes in the keymap.</para> composed key codes in the keymap.</para>
@ -404,7 +408,7 @@ EOF</userinput></screen>
<varlistentry> <varlistentry>
<term>UNICODE</term> <term>UNICODE</term>
<listitem> <listitem>
<para>Set this variable to <quote>1</quote>, <quote>yes</quote> or <para>Set this variable to <quote>1</quote>, <quote>yes</quote>, or
<quote>true</quote> in order to put the <quote>true</quote> in order to put the
console into UTF-8 mode. This is useful in UTF-8 based locales and console into UTF-8 mode. This is useful in UTF-8 based locales and
harmful otherwise.</para> harmful otherwise.</para>
@ -522,7 +526,7 @@ EOF</userinput></screen>
UTF-8 mode it is a problem; e.g., for the Greek language, where one UTF-8 mode it is a problem; e.g., for the Greek language, where one
sometimes needs to put an accent on the letter <quote>alpha</quote>. sometimes needs to put an accent on the letter <quote>alpha</quote>.
The solution is either to avoid the use of UTF-8, or to install the The solution is either to avoid the use of UTF-8, or to install the
X window system that doesn't have this limitation in its input X window system, which doesn't have this limitation, in its input
handling.</para> handling.</para>
</listitem> </listitem>
@ -531,7 +535,7 @@ EOF</userinput></screen>
console cannot be configured to display the needed characters. Users console cannot be configured to display the needed characters. Users
who need such languages should install the X Window System, fonts that who need such languages should install the X Window System, fonts that
cover the necessary character ranges, and the proper input method (e.g., cover the necessary character ranges, and the proper input method (e.g.,
SCIM, supports a wide variety of languages).</para> SCIM supports a wide variety of languages).</para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
@ -565,7 +569,7 @@ EOF</userinput></screen>
</sect2> </sect2>
<sect2 id="ch-config-sysklogd"> <sect2 id="ch-config-sysklogd">
<title>Configuring the sysklogd Script</title> <title>Configuring the Sysklogd Script</title>
<indexterm zone="ch-config-sysklogd"> <indexterm zone="ch-config-sysklogd">
<primary sortas="d-sysklogd">sysklogd</primary> <primary sortas="d-sysklogd">sysklogd</primary>
@ -600,8 +604,8 @@ EOF</userinput></screen>
<filename>console</filename>, and <filename>clock</filename> files in the <filename>console</filename>, and <filename>clock</filename> files in the
<filename class='directory'>/etc/sysconfig/</filename> directory. If the <filename class='directory'>/etc/sysconfig/</filename> directory. If the
associated variables are present in both these separate files and associated variables are present in both these separate files and
<filename>rc.site</filename>, the values in the script specific files have <filename>rc.site</filename>, the values in the script-specific files take
precedence. </para> effect. </para>
<para><filename>rc.site</filename> also contains parameters that can <para><filename>rc.site</filename> also contains parameters that can
customize other aspects of the boot process. Setting the IPROMPT variable customize other aspects of the boot process. Setting the IPROMPT variable
@ -615,8 +619,8 @@ EOF</userinput></screen>
<title>Customizing the Boot and Shutdown Scripts</title> <title>Customizing the Boot and Shutdown Scripts</title>
<para>The LFS boot scripts boot and shut down a system in a fairly <para>The LFS boot scripts boot and shut down a system in a fairly
efficient manner, but there are a few tweaks that you can make in the efficient manner, but there are a few tweaks you can make in the
rc.site file to improve speed even more and to adjust messages according rc.site file to improve speed even more, and to adjust messages according
to your preferences. To do this, adjust the settings in to your preferences. To do this, adjust the settings in
the <filename>/etc/sysconfig/rc.site</filename> file above.</para> the <filename>/etc/sysconfig/rc.site</filename> file above.</para>
@ -624,18 +628,18 @@ EOF</userinput></screen>
<listitem><para>During the boot script <filename>udev</filename>, there is <listitem><para>During the boot script <filename>udev</filename>, there is
a call to <command>udev settle</command> that requires some time to a call to <command>udev settle</command> that requires some time to
complete. This time may or may not be required depending on devices present complete. This time may or may not be required depending on the devices
in the system. If you only have simple partitions and a single ethernet in the system. If you only have simple partitions and a single ethernet
card, the boot process will probably not need to wait for this command. To card, the boot process will probably not need to wait for this command. To
skip it, set the variable OMIT_UDEV_SETTLE=y.</para></listitem> skip it, set the variable OMIT_UDEV_SETTLE=y.</para></listitem>
<listitem><para>The boot script <filename>udev_retry</filename> also runs <listitem><para>The boot script <filename>udev_retry</filename> also runs
<command>udev settle</command> by default. This command is only needed by <command>udev settle</command> by default. This command is only needed
default if the <filename class='directory'>/var</filename> directory is if the <filename class='directory'>/var</filename> directory is
separately mounted. This is because the clock needs the file separately mounted, because the clock needs the
<filename>/var/lib/hwclock/adjtime</filename>. Other customizations may <filename>/var/lib/hwclock/adjtime</filename> file. Other customizations may
also need to wait for udev to complete, but in many installations it is not also need to wait for udev to complete, but in many installations it is not
needed. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y. necessary. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
</para></listitem> </para></listitem>
<listitem><para>By default, the file system checks are silent. This can <listitem><para>By default, the file system checks are silent. This can
@ -664,7 +668,7 @@ EOF</userinput></screen>
<listitem><para>During shutdown, the <command>init</command> program sends <listitem><para>During shutdown, the <command>init</command> program sends
a TERM signal to each program it has started (e.g. agetty), waits for a set a TERM signal to each program it has started (e.g. agetty), waits for a set
time (default 3 seconds), and sends each process a KILL signal and waits time (default 3 seconds), then sends each process a KILL signal and waits
again. This process is repeated in the <command>sendsignals</command> again. This process is repeated in the <command>sendsignals</command>
script for any processes that are not shut down by their own scripts. The script for any processes that are not shut down by their own scripts. The
delay for <command>init</command> can be set by passing a parameter. For delay for <command>init</command> can be set by passing a parameter. For

35
chapter10/grub.xml
View File

@ -23,7 +23,7 @@
</para> </para>
<para> <para>
If you've installed GRUB for UEFI with optional dependencies following If you've installed GRUB for UEFI with optional dependencies following
BLFS, you should skip this page, and config GRUB with UEFI support BLFS, you should skip this page, and configure GRUB with UEFI support
using the instructions provided in using the instructions provided in
<ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>, <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>,
but replace <parameter>--target=x86_64-efi</parameter> with but replace <parameter>--target=x86_64-efi</parameter> with
@ -70,8 +70,8 @@
<para>GRUB uses its own naming structure for drives and partitions in <para>GRUB uses its own naming structure for drives and partitions in
the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
is the hard drive number and <emphasis>m</emphasis> is the partition is the hard drive number and <emphasis>m</emphasis> is the partition
number. The hard drive number starts from zero, but the partition number number. The hard drive numbers start from zero, but the partition numbers
starts from one for normal partitions and five for extended partitions. start from one for normal partitions (from five for extended partitions).
Note that this is different from earlier versions where Note that this is different from earlier versions where
both numbers started from zero. For example, partition <filename both numbers started from zero. For example, partition <filename
class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to class="partition">sda1</filename> is <emphasis>(hd0,1)</emphasis> to
@ -120,12 +120,13 @@ mount /boot/efi</userinput></screen>
files and access can be made from any booted system. If you choose to do files and access can be made from any booted system. If you choose to do
this, you will need to mount the separate partition, move all files in the this, you will need to mount the separate partition, move all files in the
current <filename class="directory">/boot</filename> directory (e.g. the current <filename class="directory">/boot</filename> directory (e.g. the
linux kernel you just built in the previous section) to the new partition. Linux kernel you just built in the previous section) to the new partition.
You will then need to unmount the partition and remount it as <filename You will then need to unmount the partition and remount it as <filename
class="directory">/boot</filename>. If you do this, be sure to update class="directory">/boot</filename>. If you do this, be sure to update
<filename>/etc/fstab</filename>.</para> <filename>/etc/fstab</filename>.</para>
<para>Using the current lfs partition will also work, but configuration <para>Leaving <filename class="directory">/boot</filename> on
the current LFS partition will also work, but configuration
for multiple systems is more difficult.</para> for multiple systems is more difficult.</para>
<para>Using the above information, determine the appropriate <para>Using the above information, determine the appropriate
@ -231,26 +232,28 @@ EOF</userinput></screen>
The change may cause boot failure because The change may cause boot failure because
<filename>grub.cfg</filename> refers to some <quote>old</quote> <filename>grub.cfg</filename> refers to some <quote>old</quote>
designators. If you wish to avoid such a problem, you may use designators. If you wish to avoid such a problem, you may use
the UUID of partition and filesystem instead of GRUB designator to the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to
specify a partition. specify a device.
Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show
the UUID of your filesystems (in <literal>UUID</literal> column) and the UUIDs of your filesystems (in the <literal>UUID</literal> column) and
partitions (in <literal>PARTUUID</literal> column). Then replace partitions (in the <literal>PARTUUID</literal> column). Then replace
<literal>set root=(hdx,y)</literal> with <literal>set root=(hdx,y)</literal> with
<literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem where the kernel is installed&gt;</replaceable></literal>, and replace <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem
where the kernel is installed&gt;</replaceable></literal>, and replace
<literal>root=/dev/sda2</literal> with <literal>root=/dev/sda2</literal> with
<literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS is built&gt;</replaceable></literal>.</para> <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS
<para>Note that the UUID of a partition and the UUID of the filesystem is built&gt;</replaceable></literal>.</para>
in this partition is completely different. Some online resources may <para>Note that the UUID of a partition is completely different from the
UUID of the filesystem in this partition. Some online resources may
instruct you to use instruct you to use
<literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal> <literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal>
instead of instead of
<literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>, <literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
but doing so will require an initramfs which is beyond the scope of but doing so will require an initramfs, which is beyond the scope of
LFS.</para> LFS.</para>
<para>The name of the device node for a partition in <para>The name of the device node for a partition in
<filename class='directory'>/dev</filename> may also change (more <filename class='directory'>/dev</filename> may also change (this is less
unlikely than GRUB designator change though). You can also replace likely than a GRUB designator change). You can also replace
paths to device nodes like <literal>/dev/sda1</literal> with paths to device nodes like <literal>/dev/sda1</literal> with
<literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>, <literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
in <filename>/etc/fstab</filename>, to avoid a potential boot failure in <filename>/etc/fstab</filename>, to avoid a potential boot failure

2
git-version.sh
View File

@ -29,7 +29,7 @@ if ! git status > /dev/null; then
fi fi
export LC_ALL=en_US.utf8 export LC_ALL=en_US.utf8
export TZ=US/Pacific export TZ=America/Chicago
commit_date=$(git show -s --format=format:"%cd" --date=local) commit_date=$(git show -s --format=format:"%cd" --date=local)

50
packages.ent
View File

@ -58,10 +58,10 @@
<!ENTITY bash-fin-du "50 MB"> <!ENTITY bash-fin-du "50 MB">
<!ENTITY bash-fin-sbu "1.4 SBU"> <!ENTITY bash-fin-sbu "1.4 SBU">
<!ENTITY bc-version "6.1.1"> <!ENTITY bc-version "6.2.1">
<!ENTITY bc-size "445 KB"> <!ENTITY bc-size "446 KB">
<!ENTITY bc-url "https://github.com/gavinhoward/bc/releases/download/&bc-version;/bc-&bc-version;.tar.xz"> <!ENTITY bc-url "https://github.com/gavinhoward/bc/releases/download/&bc-version;/bc-&bc-version;.tar.xz">
<!ENTITY bc-md5 "9a7ffa015c499272e7d41b4c0f28e691"> <!ENTITY bc-md5 "ad4b3546e5bd5cc6f46b887fb2992ae4">
<!ENTITY bc-home "https://git.yzena.com/gavin/bc"> <!ENTITY bc-home "https://git.yzena.com/gavin/bc">
<!ENTITY bc-fin-du "7.4 MB"> <!ENTITY bc-fin-du "7.4 MB">
<!ENTITY bc-fin-sbu "less than 0.1 SBU"> <!ENTITY bc-fin-sbu "less than 0.1 SBU">
@ -179,10 +179,10 @@
<!ENTITY expect-tmp-du "3.9 MB"> <!ENTITY expect-tmp-du "3.9 MB">
<!ENTITY expect-tmp-sbu "0.2 SBU"> <!ENTITY expect-tmp-sbu "0.2 SBU">
<!ENTITY file-version "5.43"> <!ENTITY file-version "5.44">
<!ENTITY file-size "1,136 KB"> <!ENTITY file-size "1,159 KB">
<!ENTITY file-url "https://astron.com/pub/file/file-&file-version;.tar.gz"> <!ENTITY file-url "https://astron.com/pub/file/file-&file-version;.tar.gz">
<!ENTITY file-md5 "8effd70da368210a6c6eece037f978eb"> <!ENTITY file-md5 "a60d586d49d015d842b9294864a89c7a">
<!ENTITY file-home "https://www.darwinsys.com/file/"> <!ENTITY file-home "https://www.darwinsys.com/file/">
<!ENTITY file-tmp-du "34 MB"> <!ENTITY file-tmp-du "34 MB">
<!ENTITY file-tmp-sbu "0.2 SBU"> <!ENTITY file-tmp-sbu "0.2 SBU">
@ -317,10 +317,10 @@
<!ENTITY gzip-fin-du "21 MB"> <!ENTITY gzip-fin-du "21 MB">
<!ENTITY gzip-fin-sbu "0.3 SBU"> <!ENTITY gzip-fin-sbu "0.3 SBU">
<!ENTITY iana-etc-version "20221209"> <!ENTITY iana-etc-version "20221220">
<!ENTITY iana-etc-size "585 KB"> <!ENTITY iana-etc-size "586 KB">
<!ENTITY iana-etc-url "https://github.com/Mic92/iana-etc/releases/download/&iana-etc-version;/iana-etc-&iana-etc-version;.tar.gz"> <!ENTITY iana-etc-url "https://github.com/Mic92/iana-etc/releases/download/&iana-etc-version;/iana-etc-&iana-etc-version;.tar.gz">
<!ENTITY iana-etc-md5 "b5e3e7ee1f65edff9284e614000a3815"> <!ENTITY iana-etc-md5 "b394b994883d01d8b33c80bc57917117">
<!ENTITY iana-etc-home "https://www.iana.org/protocols"> <!ENTITY iana-etc-home "https://www.iana.org/protocols">
<!ENTITY iana-etc-fin-du "4.8 MB"> <!ENTITY iana-etc-fin-du "4.8 MB">
<!ENTITY iana-etc-fin-sbu "less than 0.1 SBU"> <!ENTITY iana-etc-fin-sbu "less than 0.1 SBU">
@ -382,7 +382,7 @@
<!ENTITY less-fin-du "4.2 MB"> <!ENTITY less-fin-du "4.2 MB">
<!ENTITY less-fin-sbu "less than 0.1 SBU"> <!ENTITY less-fin-sbu "less than 0.1 SBU">
<!ENTITY lfs-bootscripts-version "20220920"> <!-- Scripts depend on this format --> <!ENTITY lfs-bootscripts-version "20230101"> <!-- Scripts depend on this format -->
<!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB"> <!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">
<!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz"> <!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz">
<!ENTITY lfs-bootscripts-md5 "BOOTSCRIPTS-MD5SUM"> <!ENTITY lfs-bootscripts-md5 "BOOTSCRIPTS-MD5SUM">
@ -423,13 +423,13 @@
<!ENTITY libtool-fin-sbu "1.5 SBU"> <!ENTITY libtool-fin-sbu "1.5 SBU">
<!ENTITY linux-major-version "6"> <!ENTITY linux-major-version "6">
<!ENTITY linux-minor-version "0"> <!ENTITY linux-minor-version "1">
<!ENTITY linux-patch-version "11"> <!ENTITY linux-patch-version "1">
<!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">--> <!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">-->
<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;"> <!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;">
<!ENTITY linux-size "130,780 KB"> <!ENTITY linux-size "131,573 KB">
<!ENTITY linux-url "&kernel;linux/kernel/v&linux-major-version;.x/linux-&linux-version;.tar.xz"> <!ENTITY linux-url "&kernel;linux/kernel/v&linux-major-version;.x/linux-&linux-version;.tar.xz">
<!ENTITY linux-md5 "7a47796e842b77519613abbca6037c91"> <!ENTITY linux-md5 "3482feaa021961d10ac88e789788bf07">
<!ENTITY linux-home "https://www.kernel.org/"> <!ENTITY linux-home "https://www.kernel.org/">
<!-- measured for 5.13.4 / gcc-11.1.0 on x86_64 : minimum is <!-- measured for 5.13.4 / gcc-11.1.0 on x86_64 : minimum is
allnoconfig rounded down to allow for ongoing cleanups, allnoconfig rounded down to allow for ongoing cleanups,
@ -471,10 +471,10 @@
<!ENTITY man-db-fin-du "40 MB"> <!ENTITY man-db-fin-du "40 MB">
<!ENTITY man-db-fin-sbu "0.4 SBU"> <!ENTITY man-db-fin-sbu "0.4 SBU">
<!ENTITY man-pages-version "6.01"> <!ENTITY man-pages-version "6.02">
<!ENTITY man-pages-size "1,748 KB"> <!ENTITY man-pages-size "1,759 KB">
<!ENTITY man-pages-url "&kernel;linux/docs/man-pages/man-pages-&man-pages-version;.tar.xz"> <!ENTITY man-pages-url "&kernel;linux/docs/man-pages/man-pages-&man-pages-version;.tar.xz">
<!ENTITY man-pages-md5 "83b25a1a120df78ec4c01221a1926463"> <!ENTITY man-pages-md5 "05b9e8ce59f6257141fe9e4edd5bd149">
<!ENTITY man-pages-home "https://www.kernel.org/doc/man-pages/"> <!ENTITY man-pages-home "https://www.kernel.org/doc/man-pages/">
<!ENTITY man-pages-fin-du "33 MB"> <!ENTITY man-pages-fin-du "33 MB">
<!ENTITY man-pages-fin-sbu "less than 0.1 SBU"> <!ENTITY man-pages-fin-sbu "less than 0.1 SBU">
@ -487,18 +487,18 @@
<!ENTITY markupsafe-fin-du "168 KB"> <!ENTITY markupsafe-fin-du "168 KB">
<!ENTITY markupsafe-fin-sbu "less than 0.1 SBU"> <!ENTITY markupsafe-fin-sbu "less than 0.1 SBU">
<!ENTITY meson-version "0.64.1"> <!ENTITY meson-version "1.0.0">
<!ENTITY meson-size "2,041 KB"> <!ENTITY meson-size "2,051 KB">
<!ENTITY meson-url "&github;/mesonbuild/meson/releases/download/&meson-version;/meson-&meson-version;.tar.gz"> <!ENTITY meson-url "&github;/mesonbuild/meson/releases/download/&meson-version;/meson-&meson-version;.tar.gz">
<!ENTITY meson-md5 "9f260adfcbc66ed2e15047c6eb98e503"> <!ENTITY meson-md5 "009b78125467cd9ee4d467175a5c12e1">
<!ENTITY meson-home "https://mesonbuild.com"> <!ENTITY meson-home "https://mesonbuild.com">
<!ENTITY meson-fin-du "38 MB"> <!ENTITY meson-fin-du "38 MB">
<!ENTITY meson-fin-sbu "less than 0.1 SBU"> <!ENTITY meson-fin-sbu "less than 0.1 SBU">
<!ENTITY mpc-version "1.3.0"> <!ENTITY mpc-version "1.3.1">
<!ENTITY mpc-size "756 KB"> <!ENTITY mpc-size "756 KB">
<!ENTITY mpc-url "https://ftp.gnu.org/gnu/mpc/mpc-&mpc-version;.tar.gz"> <!ENTITY mpc-url "https://ftp.gnu.org/gnu/mpc/mpc-&mpc-version;.tar.gz">
<!ENTITY mpc-md5 "b0f5e2ad6009781777ed026bcf71bf0e"> <!ENTITY mpc-md5 "5c9bc658c9fd0f940e8e3e0f09530c62">
<!ENTITY mpc-home "https://www.multiprecision.org/"> <!ENTITY mpc-home "https://www.multiprecision.org/">
<!ENTITY mpc-fin-du "21 MB"> <!ENTITY mpc-fin-du "21 MB">
<!ENTITY mpc-fin-sbu "0.3 SBU"> <!ENTITY mpc-fin-sbu "0.3 SBU">
@ -654,10 +654,10 @@
<!ENTITY systemd-fin-du "258 MB"> <!ENTITY systemd-fin-du "258 MB">
<!ENTITY systemd-fin-sbu "2.5 SBU"> <!ENTITY systemd-fin-sbu "2.5 SBU">
<!ENTITY sysvinit-version "3.05"> <!ENTITY sysvinit-version "3.06">
<!ENTITY sysvinit-size "229 KB"> <!ENTITY sysvinit-size "247 KB">
<!ENTITY sysvinit-url "&github;/slicer69/sysvinit/releases/download/&sysvinit-version;/sysvinit-&sysvinit-version;.tar.xz"> <!ENTITY sysvinit-url "&github;/slicer69/sysvinit/releases/download/&sysvinit-version;/sysvinit-&sysvinit-version;.tar.xz">
<!ENTITY sysvinit-md5 "57577060e5f21fd9899fa601aa45b064"> <!ENTITY sysvinit-md5 "96771d0a88315c91199830ea49b859ca">
<!ENTITY sysvinit-home "&savannah-nongnu;/projects/sysvinit"> <!ENTITY sysvinit-home "&savannah-nongnu;/projects/sysvinit">
<!ENTITY sysvinit-fin-du "2.7 MB"> <!ENTITY sysvinit-fin-du "2.7 MB">
<!ENTITY sysvinit-fin-sbu "less than 0.1 SBU"> <!ENTITY sysvinit-fin-sbu "less than 0.1 SBU">

14
patches.ent
View File

@ -88,14 +88,14 @@
<!ENTITY shadow-segfault-patch-size "1.7 KB"> <!ENTITY shadow-segfault-patch-size "1.7 KB">
--> -->
<!ENTITY sysvinit-consolidated-patch "sysvinit-&sysvinit-version;-consolidated-1.patch"> <!ENTITY sysvinit-consolidated-patch "sysvinit-&sysvinit-version;-consolidated-1.patch">
<!ENTITY sysvinit-consolidated-patch-md5 "372d367918134f2f41daf54f2acf280a"> <!ENTITY sysvinit-consolidated-patch-md5 "17ffccbb8e18c39e8cedc32046f3a475">
<!ENTITY sysvinit-consolidated-patch-size "2.4 KB"> <!ENTITY sysvinit-consolidated-patch-size "2.5 KB">
<!ENTITY systemd-upstream-patch "systemd-&systemd-version;-security_fix-1.patch">
<!ENTITY systemd-upstream-patch-md5 "da817e69e897d35cdffd7c45ea06be39">
<!ENTITY systemd-upstream-patch-size "76.0 KB">
<!--
<!ENTITY systemd-upstream-patch "systemd-&systemd-version;-glibc_2.36_fix-1.patch">
<!ENTITY systemd-upstream-patch-md5 "fd8dc901e73ad00dc72a351a0d4ac48c">
<!ENTITY systemd-upstream-patch-size "3.0 KB">
-->
<!-- <!--
<!ENTITY xz-upstream-fix-patch "xz-&xz-version;-upstream_fix-1.patch"> <!ENTITY xz-upstream-fix-patch "xz-&xz-version;-upstream_fix-1.patch">
<!ENTITY xz-upstream-fix-patch-md5 "584c72ea3d8f7502b2770670f3090788"> <!ENTITY xz-upstream-fix-patch-md5 "584c72ea3d8f7502b2770670f3090788">