Changeset 985d253


Ignore:
Timestamp:
01/06/2023 04:58:37 AM (16 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/clfs-ng
Children:
0678bd4
Parents:
76b84d2 (diff), af944eb (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge remote-tracking branch 'origin/trunk' into xry111/clfs-ng

Files:
12 edited

Legend:

Unmodified
Added
Removed

  • appendices/dependencies.xml

    r76b84d2 r985d253  
    14751475
    14761476<!-- Begin Jinja2 dependency info -->
    1477   <bridgehead renderas="sect2" id="jinja2-dep">Jinja2</bridgehead>
    1478 
    1479       <segmentedlist id="jinja2-depends">
     1477  <bridgehead revision='systemd' renderas="sect2" id="jinja2-dep">Jinja2</bridgehead>
     1478
     1479      <segmentedlist id="jinja2-depends" revision='systemd'>
    14801480        <segtitle>&dependencies;</segtitle>
    14811481        <seglistitem>
    … …  
    14841484      </segmentedlist>
    14851485
    1486       <segmentedlist id="jinja2-rundeps">
     1486      <segmentedlist id="jinja2-rundeps" revision='systemd'>
    14871487        <segtitle>&runtime;</segtitle>
    14881488        <seglistitem>
    … …  
    14911491      </segmentedlist>
    14921492
    1493       <segmentedlist id="jinja2-testdeps">
     1493      <segmentedlist id="jinja2-testdeps" revision='systemd'>
    14941494        <segtitle>&testsuites;</segtitle>
    14951495        <seglistitem>
    … …  
    14981498      </segmentedlist>
    14991499
    1500       <segmentedlist id="jinja2-before">
     1500      <segmentedlist id="jinja2-before" revision='systemd'>
    15011501        <segtitle>&before;</segtitle>
    15021502        <seglistitem>
    … …  
    15051505      </segmentedlist>
    15061506
    1507       <segmentedlist id="jinja2-optdeps">
     1507      <segmentedlist id="jinja2-optdeps" revision='systemd'>
    15081508        <segtitle>&external;</segtitle>
    15091509        <seglistitem>
    … …  
    20722072
    20732073<!-- Begin MarkupSafe dependency info -->
    2074   <bridgehead renderas="sect2" id="markupsafe-dep">MarkupSafe</bridgehead>
    2075 
    2076       <segmentedlist id="markupsafe-depends">
     2074  <bridgehead renderas="sect2" id="markupsafe-dep" revision='systemd'>MarkupSafe</bridgehead>
     2075
     2076      <segmentedlist id="markupsafe-depends" revision='systemd'>
    20772077        <segtitle>&dependencies;</segtitle>
    20782078        <seglistitem>
    … …  
    20812081      </segmentedlist>
    20822082
    2083       <segmentedlist id="markupsafe-rundeps">
     2083      <segmentedlist id="markupsafe-rundeps" revision='systemd'>
    20842084        <segtitle>&runtime;</segtitle>
    20852085        <seglistitem>
    … …  
    20882088      </segmentedlist>
    20892089
    2090       <segmentedlist id="markupsafe-testdeps">
     2090      <segmentedlist id="markupsafe-testdeps" revision='systemd'>
    20912091        <segtitle>&testsuites;</segtitle>
    20922092        <seglistitem>
    … …  
    20952095      </segmentedlist>
    20962096
    2097       <segmentedlist id="markupsafe-before">
     2097      <segmentedlist id="markupsafe-before" revision='systemd'>
    20982098        <segtitle>&before;</segtitle>
    20992099        <seglistitem>
    … …  
    21022102      </segmentedlist>
    21032103
    2104       <segmentedlist id="markupsafe-optdeps">
     2104      <segmentedlist id="markupsafe-optdeps" revision='systemd'>
    21052105        <segtitle>&external;</segtitle>
    21062106        <seglistitem>
    … …  
    21362136        <segtitle>&before;</segtitle>
    21372137        <seglistitem>
    2138           <seg>Systemd</seg>
     2138          <seg>
     2139            <phrase revision='sysv'>None</phrase>
     2140            <phrase revision='systemd'>Systemd</phrase>
     2141          </seg>
    21392142        </seglistitem>
    21402143      </segmentedlist>
    … …  
    27502753
    27512754<!-- Begin systemd dependency info -->
    2752   <bridgehead renderas="sect2" id="systemd-dep">Systemd</bridgehead>
    2753 
    2754       <segmentedlist id="systemd-depends">
     2755  <bridgehead renderas="sect2" id="systemd-dep" revision='systemd'>Systemd</bridgehead>
     2756
     2757      <segmentedlist id="systemd-depends" revision='systemd'>
    27552758        <segtitle>&dependencies;</segtitle>
    27562759        <seglistitem>
    … …  
    27612764      </segmentedlist>
    27622765
    2763       <segmentedlist id="systemd-rundeps">
     2766      <segmentedlist id="systemd-rundeps" revision='systemd'>
    27642767        <segtitle>&runtime;</segtitle>
    27652768        <seglistitem>
    … …  
    27682771      </segmentedlist>
    27692772
    2770       <segmentedlist id="systemd-testdeps">
    2771         <segtitle>&testsuites;</segtitle>
    2772         <seglistitem>
    2773           <seg>None</seg>
    2774         </seglistitem>
    2775       </segmentedlist>
    2776 
    2777       <segmentedlist id="systemd-before">
    2778         <segtitle>&before;</segtitle>
    2779         <seglistitem>
    2780           <seg>None</seg>
    2781         </seglistitem>
    2782       </segmentedlist>
    2783 
    2784       <segmentedlist id="systemd-optdeps">
     2773      <segmentedlist id="systemd-testdeps" revision='systemd'>
     2774        <segtitle>&testsuites;</segtitle>
     2775        <seglistitem>
     2776          <seg>None</seg>
     2777        </seglistitem>
     2778      </segmentedlist>
     2779
     2780      <segmentedlist id="systemd-before" revision='systemd'>
     2781        <segtitle>&before;</segtitle>
     2782        <seglistitem>
     2783          <seg>None</seg>
     2784        </seglistitem>
     2785      </segmentedlist>
     2786
     2787      <segmentedlist id="systemd-optdeps" revision='systemd'>
    27852788        <segtitle>&external;</segtitle>
    27862789        <seglistitem>
    … …  
    28372840
    28382841<!-- Begin Sysvinit dependency info -->
    2839   <bridgehead renderas="sect2" id="sysvinit-dep">Sysvinit</bridgehead>
    2840 
    2841       <segmentedlist id="sysvinit-depends">
     2842  <bridgehead renderas="sect2" id="sysvinit-dep" revision='sysv'>Sysvinit</bridgehead>
     2843
     2844      <segmentedlist id="sysvinit-depends" revision='sysv'>
    28422845        <segtitle>&dependencies;</segtitle>
    28432846        <seglistitem>
    … …  
    28462849      </segmentedlist>
    28472850
    2848       <segmentedlist id="sysvinit-rundeps">
     2851      <segmentedlist id="sysvinit-rundeps" revision='sysv'>
    28492852        <segtitle>&runtime;</segtitle>
    28502853        <seglistitem>
    … …  
    28532856      </segmentedlist>
    28542857
    2855       <segmentedlist id="sysvinit-testdeps">
     2858      <segmentedlist id="sysvinit-testdeps" revision='sysv'>
    28562859        <segtitle>&testsuites;</segtitle>
    28572860        <seglistitem>
    … …  
    28602863      </segmentedlist>
    28612864
    2862       <segmentedlist id="sysvinit-before">
    2863         <segtitle>&before;</segtitle>
    2864         <seglistitem>
    2865           <seg>None</seg>
    2866         </seglistitem>
    2867       </segmentedlist>
    2868 
    2869       <segmentedlist id="sysvinit-optdeps">
     2865      <segmentedlist id="sysvinit-before" revision='sysv'>
     2866        <segtitle>&before;</segtitle>
     2867        <seglistitem>
     2868          <seg>None</seg>
     2869        </seglistitem>
     2870      </segmentedlist>
     2871
     2872      <segmentedlist id="sysvinit-optdeps" revision='sysv'>
    28702873        <segtitle>&external;</segtitle>
    28712874        <seglistitem>
    … …  
    31103113        <segtitle>&before;</segtitle>
    31113114        <seglistitem>
    3112           <seg>Jinja2</seg>
     3115          <seg>
     3116            <phrase revision='sysv'>None</phrase>
     3117            <phrase revision='systemd'>Jinja2</phrase>
     3118          </seg>
    31133119        </seglistitem>
    31143120      </segmentedlist>
    … …  
    32633269        <segtitle>&before;</segtitle>
    32643270        <seglistitem>
    3265           <seg>GCC and Systemd</seg>
     3271          <seg>GCC <phrase revision='systemd'>and Systemd</phrase></seg>
    32663272        </seglistitem>
    32673273      </segmentedlist>

  • chapter01/changelog.xml

    r76b84d2 r985d253  
    4141    -->
    4242    <listitem>
     43      <para>2023-01-01</para><!-- Happy New Year! -->
     44      <itemizedlist>
     45        <listitem>
     46          <para>[thomas] - Remove an obsolete sed from mpc.</para>
     47        </listitem>
     48      </itemizedlist>
     49    </listitem>
     50
     51    <listitem>
     52      <para>2022-12-31</para>
     53      <itemizedlist>
     54        <listitem>
     55          <para>[bdubbs] - Update to iana-etc-20221220. Addresses
     56          <ulink url="&lfs-ticket-root;5006">#5006</ulink>.</para>
     57        </listitem>
     58        <listitem revision="sysv">
     59          <para>[bdubbs] - Update to sysvinit-3.06. Fixes
     60          <ulink url="&lfs-ticket-root;5186">#5186</ulink>.</para>
     61        </listitem>
     62        <listitem>
     63          <para>[bdubbs] - Update to mpc-1.3.1. Fixes
     64          <ulink url="&lfs-ticket-root;5185">#5185</ulink>.</para>
     65        </listitem>
     66        <listitem>
     67          <para>[bdubbs] - Update to meson-1.0.0. Fixes
     68          <ulink url="&lfs-ticket-root;5190">#5190</ulink>.</para>
     69        </listitem>
     70        <listitem>
     71          <para>[bdubbs] - Update to man-pages-6.02. Fixes
     72          <ulink url="&lfs-ticket-root;5188">#5188</ulink>.</para>
     73        </listitem>
     74        <listitem>
     75          <para>[bdubbs] - Update to linux-6.1.1. Fixes
     76          <ulink url="&lfs-ticket-root;5179">#5179</ulink>.</para>
     77        </listitem>
     78        <listitem>
     79          <para>[bdubbs] - Update to file-5.44. Fixes
     80          <ulink url="&lfs-ticket-root;5191">#5191</ulink>.</para>
     81        </listitem>
     82        <listitem>
     83          <para>[bdubbs] - Update to bc-6.2.1. Fixes
     84          <ulink url="&lfs-ticket-root;5189">#5189</ulink>.</para>
     85        </listitem>
     86      </itemizedlist>
     87    </listitem>
     88
     89    <listitem revision="systemd">
     90      <para>2022-12-28</para>
     91      <itemizedlist>
     92        <listitem>
     93          <para>[renodr] - Patch systemd against CVE-2022-4415. Fixes
     94          <ulink url="&lfs-ticket-root;5187">#5187</ulink>.</para>
     95        </listitem>
     96      </itemizedlist>
     97    </listitem>
     98
     99    <listitem>
    43100      <para>2022-12-15</para>
    44101      <itemizedlist>

  • chapter01/whatsnew.xml

    r76b84d2 r985d253  
    300300      <para>&readline-fixes-patch;</para>
    301301    </listitem>
     302
     303    <listitem revision="systemd">
     304      <para>&systemd-upstream-patch;</para>
     305    </listitem>
    302306  </itemizedlist>
    303307

  • chapter03/patches.xml

    r76b84d2 r985d253  
    136136    </varlistentry>
    137137
    138 <!--
     138
    139139    <varlistentry revision="systemd">
    140140      <term>Systemd Upstream Patch - <token>&systemd-upstream-patch-size;</token>:</term>
    … …  
    144144      </listitem>
    145145    </varlistentry>
    146 -->
     146
    147147<!--
    148148    <varlistentry>

  • chapter08/mpc.xml

    r76b84d2 r985d253  
    4242  <sect2 role="installation">
    4343    <title>Installation of MPC</title>
    44 
    45     <para>First, make a fix identified upstream:</para>
    46 
    47 <screen><userinput remap="pre">sed -i '273{ h; d; }; 274,286 { H; d; }; 287 G' src/mpc.h</userinput></screen>
    48 
    49     <note>
    50        <para>This sed is a little complex and needs some explanation.  It holds
    51        the line 273 in a buffer, adds lines 274-286 to it. It then writes the
    52        buffer out after line 287 is read. The result is that the line 287 is
    53        moved upwards from an incorrect location to its correct location in an
    54        #ifdef block.</para>
    55     </note>
    5644
    5745    <para>Prepare MPC for compilation:</para>

  • chapter08/systemd.xml

    r76b84d2 r985d253  
    4141    <title>Installation of systemd</title>
    4242
    43 <!--
    44     <para>First, fix an issue introduced by glibc-2.36.</para>
     43
     44    <para>First, fix a security issue in systemd-coredump:</para>
    4545
    4646<screen><userinput remap="pre">patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen>
    47 -->
     47
    4848
    4949    <para>Remove two unneeded groups,

  • chapter09/profile.xml

    r76b84d2 r985d253  
    1717  <para>The shell program <command>/bin/bash</command> (hereafter referred to
    1818  as <quote>the shell</quote>) uses a collection of startup files to help
    19   create an environment to run in. Each file has a specific use and may affect
     19  create the environment to run in. Each file has a specific use and may affect
    2020  login and interactive environments differently. The files in the <filename
    21   class="directory">/etc</filename> directory provide global settings. If an
    22   equivalent file exists in the home directory, it may override the global
     21  class="directory">/etc</filename> directory provide global settings. If
     22  equivalent files exist in the home directory, they may override the global
    2323  settings.</para>
    2424
    … …  
    3131  commands.</para>
    3232
    33   <para>For more information, see <command>info bash</command> under the
    34   <emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para>
     33<para>For more information, see the <emphasis>Bash Startup Files</emphasis> and
     34  <emphasis>Interactive Shells</emphasis> sections in the <emphasis>Bash
     35  Features</emphasis> chapter of the Bash info pages (<command>info bash</command>).</para>
    3536
    3637  <para>The files <filename>/etc/profile</filename> and
    … …  
    9293
    9394  <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
    94   It is important that the locale found using the heuristic above is tested prior
    95   to it being added to the Bash startup files:</para>
     95  It is important that the locale found using the heuristic above is tested before
     96  it is added to the Bash startup files:</para>
    9697
    9798<screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language
    … …  
    130131  "de_DE@euro" in order to get this locale recognized by Xlib.</para>
    131132-->
    132   <para>Other packages can also function incorrectly (but may not necessarily
     133  <para>Other packages may also function incorrectly (but will not necessarily
    133134  display any error messages) if the locale name does not meet their expectations.
    134   In those cases, investigating how other Linux distributions support your locale
     135  In such cases, investigating how other Linux distributions support your locale
    135136  might provide some useful information.</para>
    136137
    … …  
    148149  <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended
    149150  one for United States English users) locales are different. <quote>C</quote>
    150   uses the US-ASCII 7-bit character set, and treats bytes with the high bit set
    151   as invalid characters. That's why, e.g., the <command>ls</command> command
    152   substitutes them with question marks in that locale. Also, an attempt to send
     151  uses the US-ASCII 7-bit character set, and treats bytes with the high-order bit set
     152  <quote>on</quote> as invalid characters. That's why, e.g., the <command>ls</command> command
     153  displays them as question marks in that locale. Also, an attempt to send
    153154  mail with such characters from Mutt or Pine results in non-RFC-conforming
    154155  messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
    155   8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that
     156  8-bit</quote>). So you can only use the <quote>C</quote> locale if you are sure
    156157  you will never need 8-bit characters.</para>
    157158
    158159  <para>UTF-8 based locales are not supported well by some programs.
    159   Work is in progress to document and, if possible, fix such problems, see
     160  Work is in progress to document and, if possible, fix such problems. See
    160161  <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para>
    161162

  • chapter09/usage.xml

    r76b84d2 r985d253  
    2020    <title>How Do the System V Bootscripts Work?</title>
    2121
    22     <para>Linux uses a special booting facility named SysVinit that is based on a
    23     concept of <emphasis>run-levels</emphasis>. It can be quite different from one
    24     system to another, so it cannot be assumed that because things worked in one
    25     particular Linux distribution, they should work the same in LFS too. LFS has its
    26     own way of doing things, but it respects generally accepted standards.</para>
     22    <para>This version of LFS uses a special booting facility named SysVinit, based on a
     23    series of <emphasis>run levels</emphasis>. The boot procedure can be quite different from one
     24    system to another; the fact that things worked one way in a particular Linux
     25    distribution does not guarantee they will work the same way in LFS. LFS has its
     26    own way of doing things, but it does respect generally accepted standards.</para>
     27 
     28    <para>There is an alternative boot procedure called <command>systemd</command>. We will
     29    not discuss that boot process any further here. For a detailed description visit
     30    <ulink url="https://www.linux.com/training-tutorials/understanding-and-using-systemd/"/>.</para>
    2731
    2832    <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
    29     works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels
    30     (actually, there are more run-levels, but they are for special cases and are
    31     generally not used. See <filename>init(8)</filename> for more details), and
    32     each one of those corresponds to the actions the computer is supposed to
    33     perform when it starts up. The default run-level is 3. Here are the
    34     descriptions of the different run-levels as they are implemented in LFS:</para>
     33    uses a run levels scheme. There are seven run levels, numbered 0 to 6.
     34    (Actually, there are more run levels, but the others are for special cases and are
     35    generally not used. See <filename>init(8)</filename> for more details.)
     36    Each one of the seven corresponds to actions the computer is supposed to
     37    perform when it starts up or shuts down. The default run level is 3. Here are the
     38    descriptions of the different run levels as they are implemented in LFS:</para>
    3539
    3640<literallayout>0: halt the computer
    37411: single-user mode
    38 2: reserved for customization, otherwise does the same as 3
     422: reserved for customization, otherwise the same as 3
    39433: multi-user mode with networking
    40 4: reserved for customization, otherwise does the same as 3
     444: reserved for customization, otherwise the same as 3
    41455: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>)
    42466: reboot the computer</literallayout>
    … …  
    4650          Classically, run level 2 above was defined as
    4751          "multi-user mode without networking", but this was only the case
    48           many years ago when multiple users could log into a system connected via
    49           serial ports.  In today's environment it makes no sense and
    50           we designate it now as "reserved".
     52          many years ago when multiple users could connect to a system via
     53          serial ports.  In today's environment it makes no sense, and
     54          we now say it is "reserved".
    5155       </para>
    5256    </note>
    … …  
    6670  </indexterm>
    6771
    68   <para>During the kernel initialization, the first program that is run
    69   is either specified on the command line or, by default
     72  <para>During kernel initialization, the first program that is run
     73  (if not overridden on the command line) is
    7074  <command>init</command>.  This program reads the initialization file
    7175  <filename>/etc/inittab</filename>.  Create this file with:</para>
    … …  
    102106
    103107  <para>An explanation of this initialization file is in the man page for
    104   <emphasis>inittab</emphasis>.  For LFS, the key command that is run is
    105   <command>rc</command>. The initialization file above will instruct
     108  <emphasis>inittab</emphasis>.  In LFS, the key command is
     109  <command>rc</command>. The initialization file above instructs
    106110  <command>rc</command> to run all the scripts starting with an S in the
    107111  <filename class="directory">/etc/rc.d/rcS.d</filename> directory
    … …  
    114118  This library also reads an optional configuration file,
    115119  <filename>/etc/sysconfig/rc.site</filename>.  Any of the system
    116   configuration file parameters described in subsequent sections can be
    117   alternatively placed in this file allowing consolidation of all system
     120  configuration parameters described in subsequent sections can be
     121  placed in this file, allowing consolidation of all system
    118122  parameters in this one file.</para>
    119123
    … …  
    121125  to <filename>/run/var/bootlog</filename>.  Since the <filename
    122126  class="directory">/run</filename> directory is a tmpfs, this file is not
    123   persistent across boots, however it is appended to the more permanent file
     127  persistent across boots; however, it is appended to the more permanent file
    124128  <filename>/var/log/boot.log</filename> at the end of the boot process.</para>
    125129
    … …  
    127131  <title>Changing Run Levels</title>
    128132
    129   <para>Changing run-levels is done with <command>init
     133  <para>Changing run levels is done with <command>init
    130134  <replaceable>&lt;runlevel&gt;</replaceable></command>, where
    131   <replaceable>&lt;runlevel&gt;</replaceable> is the target run-level. For example, to
     135  <replaceable>&lt;runlevel&gt;</replaceable> is the target run level. For example, to
    132136  reboot the computer, a user could issue the <command>init 6</command> command,
    133137  which is an alias for the <command>reboot</command> command. Likewise,
    … …  
    137141  <para>There are a number of directories under <filename
    138142  class="directory">/etc/rc.d</filename> that look like <filename
    139   class="directory">rc?.d</filename> (where ? is the number of the run-level) and
     143  class="directory">rc?.d</filename> (where ? is the number of the run level) and
    140144  <filename class="directory">rcS.d</filename>, all containing a number of
    141   symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
     145  symbolic links. Some links begin with a <emphasis>K</emphasis>; the others begin with
    142146  an <emphasis>S</emphasis>, and all of them have two numbers following the
    143147  initial letter. The K means to stop (kill) a service and the S means to start a
    144148  service. The numbers determine the order in which the scripts are run, from 00
    145   to 99&mdash;the lower the number the earlier it gets executed. When
    146   <command>init</command> switches to another run-level, the appropriate services
    147   are either started or stopped, depending on the runlevel chosen.</para>
     149  to 99&mdash;the smaller the number, the sooner tht script runs. When
     150  <command>init</command> switches to another run level, the appropriate services
     151  are either started or stopped, depending on the run level chosen.</para>
    148152
    149153  <para>The real scripts are in <filename
    … …  
    228232      <para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts
    229233      <command>udevd</command>, triggers any "coldplug" devices that have
    230       already been created by the kernel and waits for any rules to complete.
     234      already been created by the kernel, and waits for any rules to complete.
    231235      The script also unsets the uevent handler from the default of
    232236      <filename>/sbin/hotplug </filename>.  This is done because the kernel no
    233       longer needs to call out to an external binary.  Instead
     237      longer needs to call an external binary.  Instead,
    234238      <command>udevd</command> will listen on a netlink socket for uevents that
    235239      the kernel raises.</para>
    236240
    237       <para>The <command>/etc/rc.d/init.d/udev_retry</command> initscript takes
     241      <para>The <command>/etc/rc.d/init.d/udev_retry</command> script takes
    238242      care of re-triggering events for subsystems whose rules may rely on
    239       filesystems that are not mounted until the <command>mountfs</command>
     243      file systems that are not mounted until the <command>mountfs</command>
    240244      script is run (in particular, <filename class="directory">/usr</filename>
    241245      and <filename class="directory">/var</filename> may cause this).  This
    242246      script runs after the <command>mountfs</command> script, so those rules
    243247      (if re-triggered) should succeed the second time around.  It is
    244       configured from the <filename>/etc/sysconfig/udev_retry</filename> file;
     248      configured by the <filename>/etc/sysconfig/udev_retry</filename> file;
    245249      any words in this file other than comments are considered subsystem names
    246250      to trigger at retry time.  To find the subsystem of a device, use
    247251      <command>udevadm info --attribute-walk &lt;device&gt;</command> where
    248       &lt;device&gt; is an absolute path in /dev or /sys such as /dev/sr0 or
     252      &lt;device&gt; is an absolute path in /dev or /sys, such as /dev/sr0, or
    249253      /sys/class/rtc.</para>
    250254
    … …  
    261265
    262266    <para>The <command>setclock</command> script reads the time from the hardware
    263     clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
     267    clock, also known as the BIOS or Complementary Metal Oxide Semiconductor
    264268    (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
    265269    hardware clock's time to the local time using the
    266270    <filename>/etc/localtime</filename> file (which tells the
    267     <command>hwclock</command> program which timezone to use). There is no
     271    <command>hwclock</command> program which time zone to use). There is no
    268272    way to detect whether or not the hardware clock is set to UTC, so this
    269     needs to be configured manually.</para>
     273    must be configured manually.</para>
    270274
    271275    <para>The <command>setclock</command> program is run via
    … …  
    280284    set to local time. If the output from <command>hwclock</command> is not local
    281285    time, chances are it is set to UTC time. Verify this by adding or subtracting
    282     the proper amount of hours for the timezone to the time shown by
     286    the proper number of hours for your time zone to the time shown by
    283287    <command>hwclock</command>. For example, if you are currently in the MST
    284     timezone, which is also known as GMT -0700, add seven hours to the local
     288    time zone, which is also known as GMT -0700, add seven hours to the local
    285289    time.</para>
    286290
    … …  
    326330  bootscript that sets up the keyboard map, console font, and console kernel log
    327331  level. If non-ASCII characters (e.g., the copyright sign, the British pound
    328   sign and Euro symbol) will not be used and the keyboard is a U.S. one, much
     332  sign, and the Euro symbol) will not be used and the keyboard is a U.S. one, much
    329333  of this section can be skipped. Without the configuration file, (or
    330334  equivalent settings in <filename>rc.site</filename>), the
    … …  
    334338  <filename>/etc/sysconfig/console</filename> file for configuration
    335339  information.  Decide which keymap and screen font will be used. Various
    336   language-specific HOWTOs can also help with this, see <ulink
     340  language-specific HOWTOs can also help with this; see <ulink
    337341  url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
    338342  doubt, look in the <filename class="directory">/usr/share/keymaps</filename>
    339343  and <filename class="directory">/usr/share/consolefonts</filename> directories
    340   for valid keymaps and screen fonts. Read <filename>loadkeys(1)</filename> and
     344  for valid keymaps and screen fonts. Read the <filename>loadkeys(1)</filename> and
    341345  <filename>setfont(8)</filename> manual pages to determine the correct
    342346  arguments for these programs.</para>
    … …  
    359363      <listitem>
    360364        <para>This variable specifies the arguments for the
    361         <command>loadkeys</command> program, typically, the name of keymap
     365        <command>loadkeys</command> program, typically, the name of the keymap
    362366        to load, e.g., <quote>it</quote>. If this variable is not set, the
    363367        bootscript will not run the <command>loadkeys</command> program,
    … …  
    391395        map to load. E.g., in order to load the <quote>lat1-16</quote> font
    392396        together with the <quote>8859-1</quote> application character map
    393         (as it is appropriate in the USA),
     397        (appropriate in the USA),
    394398        <!-- because of the copyright sign -->
    395399        set this variable to <quote>lat1-16 -m 8859-1</quote>.
    396         In UTF-8 mode, the kernel uses the application character map for
    397         conversion of composed 8-bit key codes in the keymap to UTF-8, and thus
     400        In UTF-8 mode, the kernel uses the application character map to
     401        convert 8-bit key codes to UTF-8. Therefore
    398402        the argument of the "-m" parameter should be set to the encoding of the
    399403        composed key codes in the keymap.</para>
    … …  
    405409      <term>UNICODE</term>
    406410      <listitem>
    407         <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or
     411        <para>Set this variable to <quote>1</quote>, <quote>yes</quote>, or
    408412        <quote>true</quote> in order to put the
    409413        console into UTF-8 mode. This is useful in UTF-8 based locales and
    … …  
    523527      sometimes needs to put an accent on the letter <quote>alpha</quote>.
    524528      The solution is either to avoid the use of UTF-8, or to install the
    525       X window system that doesn't have this limitation in its input
     529      X window system, which doesn't have this limitation, in its input
    526530      handling.</para>
    527531    </listitem>
    … …  
    532536      who need such languages should install the X Window System, fonts that
    533537      cover the necessary character ranges, and the proper input method (e.g.,
    534       SCIM, supports a wide variety of languages).</para>
     538      SCIM supports a wide variety of languages).</para>
    535539    </listitem>
    536540
    … …  
    566570
    567571  <sect2 id="ch-config-sysklogd">
    568     <title>Configuring the sysklogd Script</title>
     572    <title>Configuring the Sysklogd Script</title>
    569573
    570574    <indexterm zone="ch-config-sysklogd">
    … …  
    601605    <filename class='directory'>/etc/sysconfig/</filename> directory.  If the
    602606    associated variables are present in both these separate files and
    603     <filename>rc.site</filename>, the values in the script specific files have
    604     precedence. </para>
     607    <filename>rc.site</filename>, the values in the script-specific files take
     608    effect. </para>
    605609
    606610    <para><filename>rc.site</filename> also contains parameters that can
    … …  
    616620
    617621      <para>The LFS boot scripts boot and shut down a system in a fairly
    618       efficient manner, but there are a few tweaks that you can make in the
    619       rc.site file to improve speed even more and to adjust messages according
     622      efficient manner, but there are a few tweaks you can make in the
     623      rc.site file to improve speed even more, and to adjust messages according
    620624      to your preferences. To do this, adjust the settings in
    621625      the <filename>/etc/sysconfig/rc.site</filename> file above.</para>
    … …  
    625629      <listitem><para>During the boot script <filename>udev</filename>, there is
    626630      a call to <command>udev settle</command> that requires some time to
    627       complete. This time may or may not be required depending on devices present
     631      complete. This time may or may not be required depending on the devices
    628632      in the system.  If you only have simple partitions and a single ethernet
    629633      card, the boot process will probably not need to wait for this command.  To
    … …  
    631635
    632636      <listitem><para>The boot script <filename>udev_retry</filename> also runs
    633       <command>udev settle</command> by default.  This command is only needed by
    634       default if the <filename class='directory'>/var</filename> directory is
    635       separately mounted.  This is because the clock needs the file
    636       <filename>/var/lib/hwclock/adjtime</filename>.  Other customizations may
     637      <command>udev settle</command> by default.  This command is only needed
     638      if the <filename class='directory'>/var</filename> directory is
     639      separately mounted, because the clock needs the
     640      <filename>/var/lib/hwclock/adjtime</filename> file.  Other customizations may
    637641      also need to wait for udev to complete, but in many installations it is not
    638       needed.  Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
     642      necessary.  Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
    639643      </para></listitem>
    640644
    … …  
    665669      <listitem><para>During shutdown, the <command>init</command> program sends
    666670      a TERM signal to each program it has started (e.g. agetty), waits for a set
    667       time (default 3 seconds), and sends each process a KILL signal and waits
     671      time (default 3 seconds), then sends each process a KILL signal and waits
    668672      again.  This process is repeated in the <command>sendsignals</command>
    669673      script for any processes that are not shut down by their own scripts.  The

  • chapter10/grub.xml

    r76b84d2 r985d253  
    2020    <para>
    2121      If your system has UEFI support and you wish to boot LFS with UEFI,
    22       you should skip this page, and config GRUB with UEFI support
     22      you should skip this page, and configure GRUB with UEFI support
    2323      using the instructions provided in
    2424      <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>.
    … …  
    5555    the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
    5656    is the hard drive number and <emphasis>m</emphasis> is the partition
    57     number. The hard drive number starts from zero, but the partition number
    58     starts from one for normal partitions and five for extended partitions.
     57    number. The hard drive numbers start from zero, but the partition numbers
     58    start from one for normal partitions (from five for extended partitions).
    5959    Note that this is different from earlier versions where
    6060    both numbers started from zero. For example, partition <filename
    … …  
    148148      <filename>grub.cfg</filename> refers to some <quote>old</quote>
    149149      designators.  If you wish to avoid such a problem, you may use
    150       the UUID of partition and filesystem instead of GRUB designator to
    151       specify a partition.
     150      the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to
     151      specify a device.
    152152      Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show
    153       the UUID of your filesystems (in <literal>UUID</literal> column) and
    154       partitions (in <literal>PARTUUID</literal> column).  Then replace
     153      the UUIDs of your filesystems (in the <literal>UUID</literal> column) and
     154      partitions (in the <literal>PARTUUID</literal> column).  Then replace
    155155      <literal>set root=(hdx,y)</literal> with
    156       <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem where the kernel is installed&gt;</replaceable></literal>, and replace
     156      <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem
     157      where the kernel is installed&gt;</replaceable></literal>, and replace
    157158      <literal>root=/dev/sda2</literal> with
    158       <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS is built&gt;</replaceable></literal>.</para>
    159       <para>Note that the UUID of a partition and the UUID of the filesystem
    160       in this partition is completely different.  Some online resources may
     159      <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS
     160      is built&gt;</replaceable></literal>.</para>
     161      <para>Note that the UUID of a partition is completely different from the
     162      UUID of the filesystem in this partition.  Some online resources may
    161163      instruct you to use
    162164      <literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal>
    163165      instead of
    164166      <literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
    165       but doing so will require an initramfs which is beyond the scope of
     167      but doing so will require an initramfs, which is beyond the scope of
    166168      LFS.</para>
    167169      <para>The name of the device node for a partition in
    168       <filename class='directory'>/dev</filename> may also change (more
    169       unlikely than GRUB designator change though).  You can also replace
     170      <filename class='directory'>/dev</filename> may also change (this is less
     171      likely than a GRUB designator change).  You can also replace
    170172      paths to device nodes like <literal>/dev/sda1</literal> with
    171173      <literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,

  • git-version.sh

    r76b84d2 r985d253  
    3030
    3131export LC_ALL=en_US.utf8
    32 export TZ=US/Pacific
     32export TZ=America/Chicago
    3333
    3434commit_date=$(git show -s --format=format:"%cd" --date=local)

  • packages.ent

    r76b84d2 r985d253  
    5959<!ENTITY bash-fin-sbu "1.4 SBU">
    6060
    61 <!ENTITY bc-version "6.1.1">
    62 <!ENTITY bc-size "445 KB">
     61<!ENTITY bc-version "6.2.1">
     62<!ENTITY bc-size "446 KB">
    6363<!ENTITY bc-url "https://github.com/gavinhoward/bc/releases/download/&bc-version;/bc-&bc-version;.tar.xz">
    64 <!ENTITY bc-md5 "9a7ffa015c499272e7d41b4c0f28e691">
     64<!ENTITY bc-md5 "ad4b3546e5bd5cc6f46b887fb2992ae4">
    6565<!ENTITY bc-home "https://git.yzena.com/gavin/bc">
    6666<!ENTITY bc-fin-du "7.4 MB">
    … …  
    180180<!ENTITY expect-tmp-sbu "0.2 SBU">
    181181
    182 <!ENTITY file-version "5.43">
    183 <!ENTITY file-size "1,136 KB">
     182<!ENTITY file-version "5.44">
     183<!ENTITY file-size "1,159 KB">
    184184<!ENTITY file-url "https://astron.com/pub/file/file-&file-version;.tar.gz">
    185 <!ENTITY file-md5 "8effd70da368210a6c6eece037f978eb">
     185<!ENTITY file-md5 "a60d586d49d015d842b9294864a89c7a">
    186186<!ENTITY file-home "https://www.darwinsys.com/file/">
    187187<!ENTITY file-tmp-du "34 MB">
    … …  
    320320<!ENTITY gzip-fin-sbu "0.3 SBU">
    321321
    322 <!ENTITY iana-etc-version "20221209">
    323 <!ENTITY iana-etc-size "585 KB">
     322<!ENTITY iana-etc-version "20221220">
     323<!ENTITY iana-etc-size "586 KB">
    324324<!ENTITY iana-etc-url "https://github.com/Mic92/iana-etc/releases/download/&iana-etc-version;/iana-etc-&iana-etc-version;.tar.gz">
    325 <!ENTITY iana-etc-md5 "b5e3e7ee1f65edff9284e614000a3815">
     325<!ENTITY iana-etc-md5 "b394b994883d01d8b33c80bc57917117">
    326326<!ENTITY iana-etc-home "https://www.iana.org/protocols">
    327327<!ENTITY iana-etc-fin-du "4.8 MB">
    … …  
    387387<!ENTITY less-fin-sbu "less than 0.1 SBU">
    388388
    389 <!ENTITY lfs-bootscripts-version "20220920">      <!-- Scripts depend on this format -->
     389<!ENTITY lfs-bootscripts-version "20230101">      <!-- Scripts depend on this format -->
    390390<!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">
    391391<!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz">
    … …  
    428428
    429429<!ENTITY linux-major-version "6">
    430 <!ENTITY linux-minor-version "0">
    431 <!ENTITY linux-patch-version "11">
     430<!ENTITY linux-minor-version "1">
     431<!ENTITY linux-patch-version "1">
    432432<!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">-->
    433433<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;">
    434 <!ENTITY linux-size "130,780 KB">
     434<!ENTITY linux-size "131,573 KB">
    435435<!ENTITY linux-url "&kernel;linux/kernel/v&linux-major-version;.x/linux-&linux-version;.tar.xz">
    436 <!ENTITY linux-md5 "7a47796e842b77519613abbca6037c91">
     436<!ENTITY linux-md5 "3482feaa021961d10ac88e789788bf07">
    437437<!ENTITY linux-home "https://www.kernel.org/">
    438438<!-- measured for 5.13.4 / gcc-11.1.0 on x86_64 : minimum is
    … …  
    478478<!ENTITY man-db-fin-sbu "0.4 SBU">
    479479
    480 <!ENTITY man-pages-version "6.01">
    481 <!ENTITY man-pages-size "1,748 KB">
     480<!ENTITY man-pages-version "6.02">
     481<!ENTITY man-pages-size "1,759 KB">
    482482<!ENTITY man-pages-url "&kernel;linux/docs/man-pages/man-pages-&man-pages-version;.tar.xz">
    483 <!ENTITY man-pages-md5 "83b25a1a120df78ec4c01221a1926463">
     483<!ENTITY man-pages-md5 "05b9e8ce59f6257141fe9e4edd5bd149">
    484484<!ENTITY man-pages-home "https://www.kernel.org/doc/man-pages/">
    485485<!ENTITY man-pages-fin-du "33 MB">
    … …  
    494494<!ENTITY markupsafe-fin-sbu "less than 0.1 SBU">
    495495
    496 <!ENTITY meson-version "0.64.1">
    497 <!ENTITY meson-size "2,041 KB">
     496<!ENTITY meson-version "1.0.0">
     497<!ENTITY meson-size "2,051 KB">
    498498<!ENTITY meson-url "&github;/mesonbuild/meson/releases/download/&meson-version;/meson-&meson-version;.tar.gz">
    499 <!ENTITY meson-md5 "9f260adfcbc66ed2e15047c6eb98e503">
     499<!ENTITY meson-md5 "009b78125467cd9ee4d467175a5c12e1">
    500500<!ENTITY meson-home "https://mesonbuild.com">
    501501<!ENTITY meson-fin-du "38 MB">
    502502<!ENTITY meson-fin-sbu "less than 0.1 SBU">
    503503
    504 <!ENTITY mpc-version "1.3.0">
     504<!ENTITY mpc-version "1.3.1">
    505505<!ENTITY mpc-size "756 KB">
    506506<!ENTITY mpc-url "https://ftp.gnu.org/gnu/mpc/mpc-&mpc-version;.tar.gz">
    507 <!ENTITY mpc-md5 "b0f5e2ad6009781777ed026bcf71bf0e">
     507<!ENTITY mpc-md5 "5c9bc658c9fd0f940e8e3e0f09530c62">
    508508<!ENTITY mpc-home "https://www.multiprecision.org/">
    509509<!ENTITY mpc-fin-du "21 MB">
    … …  
    661661<!ENTITY systemd-fin-sbu  "2.5 SBU">
    662662
    663 <!ENTITY sysvinit-version "3.05">
    664 <!ENTITY sysvinit-size "229 KB">
     663<!ENTITY sysvinit-version "3.06">
     664<!ENTITY sysvinit-size "247 KB">
    665665<!ENTITY sysvinit-url "&github;/slicer69/sysvinit/releases/download/&sysvinit-version;/sysvinit-&sysvinit-version;.tar.xz">
    666 <!ENTITY sysvinit-md5 "57577060e5f21fd9899fa601aa45b064">
     666<!ENTITY sysvinit-md5 "96771d0a88315c91199830ea49b859ca">
    667667<!ENTITY sysvinit-home "&savannah-nongnu;/projects/sysvinit">
    668668<!ENTITY sysvinit-fin-du "2.7 MB">

  • patches.ent

    r76b84d2 r985d253  
    8989-->
    9090<!ENTITY sysvinit-consolidated-patch "sysvinit-&sysvinit-version;-consolidated-1.patch">
    91 <!ENTITY sysvinit-consolidated-patch-md5 "372d367918134f2f41daf54f2acf280a">
    92 <!ENTITY sysvinit-consolidated-patch-size "2.4 KB">
     91<!ENTITY sysvinit-consolidated-patch-md5 "17ffccbb8e18c39e8cedc32046f3a475">
     92<!ENTITY sysvinit-consolidated-patch-size "2.5 KB">
    9393
    94 <!--
    95 <!ENTITY systemd-upstream-patch "systemd-&systemd-version;-glibc_2.36_fix-1.patch">
    96 <!ENTITY systemd-upstream-patch-md5 "fd8dc901e73ad00dc72a351a0d4ac48c">
    97 <!ENTITY systemd-upstream-patch-size "3.0 KB">
    98 -->
     94
     95<!ENTITY systemd-upstream-patch "systemd-&systemd-version;-security_fix-1.patch">
     96<!ENTITY systemd-upstream-patch-md5 "da817e69e897d35cdffd7c45ea06be39">
     97<!ENTITY systemd-upstream-patch-size "76.0 KB">
     98
    9999<!--
    100100<!ENTITY xz-upstream-fix-patch "xz-&xz-version;-upstream_fix-1.patch">
Note: See TracChangeset for help on using the changeset viewer.