Changes in / [0cbb853:688a8f5]


Ignore:
Files:
12 edited

Legend:

Unmodified
Added
Removed

  • appendices/dependencies.xml

    r0cbb853 r688a8f5  
    14751475
    14761476<!-- Begin Jinja2 dependency info -->
    1477   <bridgehead revision='systemd' renderas="sect2" id="jinja2-dep">Jinja2</bridgehead>
    1478 
    1479       <segmentedlist id="jinja2-depends" revision='systemd'>
     1477  <bridgehead renderas="sect2" id="jinja2-dep">Jinja2</bridgehead>
     1478
     1479      <segmentedlist id="jinja2-depends">
    14801480        <segtitle>&dependencies;</segtitle>
    14811481        <seglistitem>
    … …  
    14841484      </segmentedlist>
    14851485
    1486       <segmentedlist id="jinja2-rundeps" revision='systemd'>
     1486      <segmentedlist id="jinja2-rundeps">
    14871487        <segtitle>&runtime;</segtitle>
    14881488        <seglistitem>
    … …  
    14911491      </segmentedlist>
    14921492
    1493       <segmentedlist id="jinja2-testdeps" revision='systemd'>
     1493      <segmentedlist id="jinja2-testdeps">
    14941494        <segtitle>&testsuites;</segtitle>
    14951495        <seglistitem>
    … …  
    14981498      </segmentedlist>
    14991499
    1500       <segmentedlist id="jinja2-before" revision='systemd'>
     1500      <segmentedlist id="jinja2-before">
    15011501        <segtitle>&before;</segtitle>
    15021502        <seglistitem>
    … …  
    15051505      </segmentedlist>
    15061506
    1507       <segmentedlist id="jinja2-optdeps" revision='systemd'>
     1507      <segmentedlist id="jinja2-optdeps">
    15081508        <segtitle>&external;</segtitle>
    15091509        <seglistitem>
    … …  
    20722072
    20732073<!-- Begin MarkupSafe dependency info -->
    2074   <bridgehead renderas="sect2" id="markupsafe-dep" revision='systemd'>MarkupSafe</bridgehead>
    2075 
    2076       <segmentedlist id="markupsafe-depends" revision='systemd'>
     2074  <bridgehead renderas="sect2" id="markupsafe-dep">MarkupSafe</bridgehead>
     2075
     2076      <segmentedlist id="markupsafe-depends">
    20772077        <segtitle>&dependencies;</segtitle>
    20782078        <seglistitem>
    … …  
    20812081      </segmentedlist>
    20822082
    2083       <segmentedlist id="markupsafe-rundeps" revision='systemd'>
     2083      <segmentedlist id="markupsafe-rundeps">
    20842084        <segtitle>&runtime;</segtitle>
    20852085        <seglistitem>
    … …  
    20882088      </segmentedlist>
    20892089
    2090       <segmentedlist id="markupsafe-testdeps" revision='systemd'>
     2090      <segmentedlist id="markupsafe-testdeps">
    20912091        <segtitle>&testsuites;</segtitle>
    20922092        <seglistitem>
    … …  
    20952095      </segmentedlist>
    20962096
    2097       <segmentedlist id="markupsafe-before" revision='systemd'>
     2097      <segmentedlist id="markupsafe-before">
    20982098        <segtitle>&before;</segtitle>
    20992099        <seglistitem>
    … …  
    21022102      </segmentedlist>
    21032103
    2104       <segmentedlist id="markupsafe-optdeps" revision='systemd'>
     2104      <segmentedlist id="markupsafe-optdeps">
    21052105        <segtitle>&external;</segtitle>
    21062106        <seglistitem>
    … …  
    21362136        <segtitle>&before;</segtitle>
    21372137        <seglistitem>
    2138           <seg>
    2139             <phrase revision='sysv'>None</phrase>
    2140             <phrase revision='systemd'>Systemd</phrase>
    2141           </seg>
     2138          <seg>Systemd</seg>
    21422139        </seglistitem>
    21432140      </segmentedlist>
    … …  
    27532750
    27542751<!-- Begin systemd dependency info -->
    2755   <bridgehead renderas="sect2" id="systemd-dep" revision='systemd'>Systemd</bridgehead>
    2756 
    2757       <segmentedlist id="systemd-depends" revision='systemd'>
     2752  <bridgehead renderas="sect2" id="systemd-dep">Systemd</bridgehead>
     2753
     2754      <segmentedlist id="systemd-depends">
    27582755        <segtitle>&dependencies;</segtitle>
    27592756        <seglistitem>
    … …  
    27642761      </segmentedlist>
    27652762
    2766       <segmentedlist id="systemd-rundeps" revision='systemd'>
     2763      <segmentedlist id="systemd-rundeps">
    27672764        <segtitle>&runtime;</segtitle>
    27682765        <seglistitem>
    … …  
    27712768      </segmentedlist>
    27722769
    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'>
     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">
    27882785        <segtitle>&external;</segtitle>
    27892786        <seglistitem>
    … …  
    28402837
    28412838<!-- Begin Sysvinit dependency info -->
    2842   <bridgehead renderas="sect2" id="sysvinit-dep" revision='sysv'>Sysvinit</bridgehead>
    2843 
    2844       <segmentedlist id="sysvinit-depends" revision='sysv'>
     2839  <bridgehead renderas="sect2" id="sysvinit-dep">Sysvinit</bridgehead>
     2840
     2841      <segmentedlist id="sysvinit-depends">
    28452842        <segtitle>&dependencies;</segtitle>
    28462843        <seglistitem>
    … …  
    28492846      </segmentedlist>
    28502847
    2851       <segmentedlist id="sysvinit-rundeps" revision='sysv'>
     2848      <segmentedlist id="sysvinit-rundeps">
    28522849        <segtitle>&runtime;</segtitle>
    28532850        <seglistitem>
    … …  
    28562853      </segmentedlist>
    28572854
    2858       <segmentedlist id="sysvinit-testdeps" revision='sysv'>
     2855      <segmentedlist id="sysvinit-testdeps">
    28592856        <segtitle>&testsuites;</segtitle>
    28602857        <seglistitem>
    … …  
    28632860      </segmentedlist>
    28642861
    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'>
     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">
    28732870        <segtitle>&external;</segtitle>
    28742871        <seglistitem>
    … …  
    31133110        <segtitle>&before;</segtitle>
    31143111        <seglistitem>
    3115           <seg>
    3116             <phrase revision='sysv'>None</phrase>
    3117             <phrase revision='systemd'>Jinja2</phrase>
    3118           </seg>
     3112          <seg>Jinja2</seg>
    31193113        </seglistitem>
    31203114      </segmentedlist>
    … …  
    32693263        <segtitle>&before;</segtitle>
    32703264        <seglistitem>
    3271           <seg>GCC <phrase revision='systemd'>and Systemd</phrase></seg>
     3265          <seg>GCC and Systemd</seg>
    32723266        </seglistitem>
    32733267      </segmentedlist>

  • chapter01/changelog.xml

    r0cbb853 r688a8f5  
    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>
    10043      <para>2022-12-15</para>
    10144      <itemizedlist>

  • chapter01/whatsnew.xml

    r0cbb853 r688a8f5  
    300300      <para>&readline-fixes-patch;</para>
    301301    </listitem>
    302 
    303     <listitem revision="systemd">
    304       <para>&systemd-upstream-patch;</para>
    305     </listitem>
    306302  </itemizedlist>
    307303

  • chapter03/patches.xml

    r0cbb853 r688a8f5  
    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

    r0cbb853 r688a8f5  
    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>
    4456
    4557    <para>Prepare MPC for compilation:</para>

  • chapter08/systemd.xml

    r0cbb853 r688a8f5  
    4141    <title>Installation of systemd</title>
    4242
    43 
    44     <para>First, fix a security issue in systemd-coredump:</para>
     43<!--
     44    <para>First, fix an issue introduced by glibc-2.36.</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

    r0cbb853 r688a8f5  
    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 the environment to run in. Each file has a specific use and may affect
     19  create an 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
    22   equivalent files exist in the home directory, they may override the global
     21  class="directory">/etc</filename> directory provide global settings. If an
     22  equivalent file exists in the home directory, it may override the global
    2323  settings.</para>
    2424
    … …  
    3131  commands.</para>
    3232
    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>
     33  <para>For more information, see <command>info bash</command> under the
     34  <emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para>
    3635
    3736  <para>The files <filename>/etc/profile</filename> and
    … …  
    9392
    9493  <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
    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>
     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>
    9796
    9897<screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language
    … …  
    131130  "de_DE@euro" in order to get this locale recognized by Xlib.</para>
    132131-->
    133   <para>Other packages may also function incorrectly (but will not necessarily
     132  <para>Other packages can also function incorrectly (but may not necessarily
    134133  display any error messages) if the locale name does not meet their expectations.
    135   In such cases, investigating how other Linux distributions support your locale
     134  In those cases, investigating how other Linux distributions support your locale
    136135  might provide some useful information.</para>
    137136
    … …  
    149148  <para>The <quote>C</quote> (default) and <quote>en_US.utf8</quote> (the recommended
    150149  one for United States English users) locales are different. <quote>C</quote>
    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
     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
    154153  mail with such characters from Mutt or Pine results in non-RFC-conforming
    155154  messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
    156   8-bit</quote>). So you can only use the <quote>C</quote> locale if you are sure
     155  8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that
    157156  you will never need 8-bit characters.</para>
    158157
    159158  <para>UTF-8 based locales are not supported well by some programs.
    160   Work is in progress to document and, if possible, fix such problems. See
     159  Work is in progress to document and, if possible, fix such problems, see
    161160  <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para>
    162161

  • chapter09/usage.xml

    r0cbb853 r688a8f5  
    2020    <title>How Do the System V Bootscripts Work?</title>
    2121
    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>
     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>
    3127
    3228    <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
    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>
     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>
    3935
    4036<literallayout>0: halt the computer
    41371: single-user mode
    42 2: reserved for customization, otherwise the same as 3
     382: reserved for customization, otherwise does the same as 3
    43393: multi-user mode with networking
    44 4: reserved for customization, otherwise the same as 3
     404: reserved for customization, otherwise does the same as 3
    45415: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>)
    46426: reboot the computer</literallayout>
    … …  
    5046          Classically, run level 2 above was defined as
    5147          "multi-user mode without networking", but this was only the case
    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".
     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".
    5551       </para>
    5652    </note>
    … …  
    7066  </indexterm>
    7167
    72   <para>During kernel initialization, the first program that is run
    73   (if not overridden on the command line) is
     68  <para>During the kernel initialization, the first program that is run
     69  is either specified on the command line or, by default
    7470  <command>init</command>.  This program reads the initialization file
    7571  <filename>/etc/inittab</filename>.  Create this file with:</para>
    … …  
    106102
    107103  <para>An explanation of this initialization file is in the man page for
    108   <emphasis>inittab</emphasis>.  In LFS, the key command is
    109   <command>rc</command>. The initialization file above instructs
     104  <emphasis>inittab</emphasis>.  For LFS, the key command that is run is
     105  <command>rc</command>. The initialization file above will instruct
    110106  <command>rc</command> to run all the scripts starting with an S in the
    111107  <filename class="directory">/etc/rc.d/rcS.d</filename> directory
    … …  
    118114  This library also reads an optional configuration file,
    119115  <filename>/etc/sysconfig/rc.site</filename>.  Any of the system
    120   configuration parameters described in subsequent sections can be
    121   placed in this file, allowing consolidation of all system
     116  configuration file parameters described in subsequent sections can be
     117  alternatively placed in this file allowing consolidation of all system
    122118  parameters in this one file.</para>
    123119
    … …  
    125121  to <filename>/run/var/bootlog</filename>.  Since the <filename
    126122  class="directory">/run</filename> directory is a tmpfs, this file is not
    127   persistent across boots; however, it is appended to the more permanent file
     123  persistent across boots, however it is appended to the more permanent file
    128124  <filename>/var/log/boot.log</filename> at the end of the boot process.</para>
    129125
    … …  
    131127  <title>Changing Run Levels</title>
    132128
    133   <para>Changing run levels is done with <command>init
     129  <para>Changing run-levels is done with <command>init
    134130  <replaceable>&lt;runlevel&gt;</replaceable></command>, where
    135   <replaceable>&lt;runlevel&gt;</replaceable> is the target run level. For example, to
     131  <replaceable>&lt;runlevel&gt;</replaceable> is the target run-level. For example, to
    136132  reboot the computer, a user could issue the <command>init 6</command> command,
    137133  which is an alias for the <command>reboot</command> command. Likewise,
    … …  
    141137  <para>There are a number of directories under <filename
    142138  class="directory">/etc/rc.d</filename> that look like <filename
    143   class="directory">rc?.d</filename> (where ? is the number of the run level) and
     139  class="directory">rc?.d</filename> (where ? is the number of the run-level) and
    144140  <filename class="directory">rcS.d</filename>, all containing a number of
    145   symbolic links. Some links begin with a <emphasis>K</emphasis>; the others begin with
     141  symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
    146142  an <emphasis>S</emphasis>, and all of them have two numbers following the
    147143  initial letter. The K means to stop (kill) a service and the S means to start a
    148144  service. The numbers determine the order in which the scripts are run, from 00
    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>
     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>
    152148
    153149  <para>The real scripts are in <filename
    … …  
    232228      <para>The <filename>/etc/rc.d/init.d/udev</filename> initscript starts
    233229      <command>udevd</command>, triggers any "coldplug" devices that have
    234       already been created by the kernel, and waits for any rules to complete.
     230      already been created by the kernel and waits for any rules to complete.
    235231      The script also unsets the uevent handler from the default of
    236232      <filename>/sbin/hotplug </filename>.  This is done because the kernel no
    237       longer needs to call an external binary.  Instead,
     233      longer needs to call out to an external binary.  Instead
    238234      <command>udevd</command> will listen on a netlink socket for uevents that
    239235      the kernel raises.</para>
    240236
    241       <para>The <command>/etc/rc.d/init.d/udev_retry</command> script takes
     237      <para>The <command>/etc/rc.d/init.d/udev_retry</command> initscript takes
    242238      care of re-triggering events for subsystems whose rules may rely on
    243       file systems that are not mounted until the <command>mountfs</command>
     239      filesystems that are not mounted until the <command>mountfs</command>
    244240      script is run (in particular, <filename class="directory">/usr</filename>
    245241      and <filename class="directory">/var</filename> may cause this).  This
    246242      script runs after the <command>mountfs</command> script, so those rules
    247243      (if re-triggered) should succeed the second time around.  It is
    248       configured by the <filename>/etc/sysconfig/udev_retry</filename> file;
     244      configured from the <filename>/etc/sysconfig/udev_retry</filename> file;
    249245      any words in this file other than comments are considered subsystem names
    250246      to trigger at retry time.  To find the subsystem of a device, use
    251247      <command>udevadm info --attribute-walk &lt;device&gt;</command> where
    252       &lt;device&gt; is an absolute path in /dev or /sys, such as /dev/sr0, or
     248      &lt;device&gt; is an absolute path in /dev or /sys such as /dev/sr0 or
    253249      /sys/class/rtc.</para>
    254250
    … …  
    265261
    266262    <para>The <command>setclock</command> script reads the time from the hardware
    267     clock, also known as the BIOS or Complementary Metal Oxide Semiconductor
     263    clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
    268264    (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
    269265    hardware clock's time to the local time using the
    270266    <filename>/etc/localtime</filename> file (which tells the
    271     <command>hwclock</command> program which time zone to use). There is no
     267    <command>hwclock</command> program which timezone to use). There is no
    272268    way to detect whether or not the hardware clock is set to UTC, so this
    273     must be configured manually.</para>
     269    needs to be configured manually.</para>
    274270
    275271    <para>The <command>setclock</command> program is run via
    … …  
    284280    set to local time. If the output from <command>hwclock</command> is not local
    285281    time, chances are it is set to UTC time. Verify this by adding or subtracting
    286     the proper number of hours for your time zone to the time shown by
     282    the proper amount of hours for the timezone to the time shown by
    287283    <command>hwclock</command>. For example, if you are currently in the MST
    288     time zone, which is also known as GMT -0700, add seven hours to the local
     284    timezone, which is also known as GMT -0700, add seven hours to the local
    289285    time.</para>
    290286
    … …  
    330326  bootscript that sets up the keyboard map, console font, and console kernel log
    331327  level. If non-ASCII characters (e.g., the copyright sign, the British pound
    332   sign, and the Euro symbol) will not be used and the keyboard is a U.S. one, much
     328  sign and Euro symbol) will not be used and the keyboard is a U.S. one, much
    333329  of this section can be skipped. Without the configuration file, (or
    334330  equivalent settings in <filename>rc.site</filename>), the
    … …  
    338334  <filename>/etc/sysconfig/console</filename> file for configuration
    339335  information.  Decide which keymap and screen font will be used. Various
    340   language-specific HOWTOs can also help with this; see <ulink
     336  language-specific HOWTOs can also help with this, see <ulink
    341337  url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
    342338  doubt, look in the <filename class="directory">/usr/share/keymaps</filename>
    343339  and <filename class="directory">/usr/share/consolefonts</filename> directories
    344   for valid keymaps and screen fonts. Read the <filename>loadkeys(1)</filename> and
     340  for valid keymaps and screen fonts. Read <filename>loadkeys(1)</filename> and
    345341  <filename>setfont(8)</filename> manual pages to determine the correct
    346342  arguments for these programs.</para>
    … …  
    363359      <listitem>
    364360        <para>This variable specifies the arguments for the
    365         <command>loadkeys</command> program, typically, the name of the keymap
     361        <command>loadkeys</command> program, typically, the name of keymap
    366362        to load, e.g., <quote>it</quote>. If this variable is not set, the
    367363        bootscript will not run the <command>loadkeys</command> program,
    … …  
    395391        map to load. E.g., in order to load the <quote>lat1-16</quote> font
    396392        together with the <quote>8859-1</quote> application character map
    397         (appropriate in the USA),
     393        (as it is appropriate in the USA),
    398394        <!-- because of the copyright sign -->
    399395        set this variable to <quote>lat1-16 -m 8859-1</quote>.
    400         In UTF-8 mode, the kernel uses the application character map to
    401         convert 8-bit key codes to UTF-8. Therefore
     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
    402398        the argument of the "-m" parameter should be set to the encoding of the
    403399        composed key codes in the keymap.</para>
    … …  
    409405      <term>UNICODE</term>
    410406      <listitem>
    411         <para>Set this variable to <quote>1</quote>, <quote>yes</quote>, or
     407        <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or
    412408        <quote>true</quote> in order to put the
    413409        console into UTF-8 mode. This is useful in UTF-8 based locales and
    … …  
    527523      sometimes needs to put an accent on the letter <quote>alpha</quote>.
    528524      The solution is either to avoid the use of UTF-8, or to install the
    529       X window system, which doesn't have this limitation, in its input
     525      X window system that doesn't have this limitation in its input
    530526      handling.</para>
    531527    </listitem>
    … …  
    536532      who need such languages should install the X Window System, fonts that
    537533      cover the necessary character ranges, and the proper input method (e.g.,
    538       SCIM supports a wide variety of languages).</para>
     534      SCIM, supports a wide variety of languages).</para>
    539535    </listitem>
    540536
    … …  
    570566
    571567  <sect2 id="ch-config-sysklogd">
    572     <title>Configuring the Sysklogd Script</title>
     568    <title>Configuring the sysklogd Script</title>
    573569
    574570    <indexterm zone="ch-config-sysklogd">
    … …  
    605601    <filename class='directory'>/etc/sysconfig/</filename> directory.  If the
    606602    associated variables are present in both these separate files and
    607     <filename>rc.site</filename>, the values in the script-specific files take
    608     effect. </para>
     603    <filename>rc.site</filename>, the values in the script specific files have
     604    precedence. </para>
    609605
    610606    <para><filename>rc.site</filename> also contains parameters that can
    … …  
    620616
    621617      <para>The LFS boot scripts boot and shut down a system in a fairly
    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
     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
    624620      to your preferences. To do this, adjust the settings in
    625621      the <filename>/etc/sysconfig/rc.site</filename> file above.</para>
    … …  
    629625      <listitem><para>During the boot script <filename>udev</filename>, there is
    630626      a call to <command>udev settle</command> that requires some time to
    631       complete. This time may or may not be required depending on the devices
     627      complete. This time may or may not be required depending on devices present
    632628      in the system.  If you only have simple partitions and a single ethernet
    633629      card, the boot process will probably not need to wait for this command.  To
    … …  
    635631
    636632      <listitem><para>The boot script <filename>udev_retry</filename> also runs
    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
     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
    641637      also need to wait for udev to complete, but in many installations it is not
    642       necessary.  Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
     638      needed.  Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
    643639      </para></listitem>
    644640
    … …  
    669665      <listitem><para>During shutdown, the <command>init</command> program sends
    670666      a TERM signal to each program it has started (e.g. agetty), waits for a set
    671       time (default 3 seconds), then sends each process a KILL signal and waits
     667      time (default 3 seconds), and sends each process a KILL signal and waits
    672668      again.  This process is repeated in the <command>sendsignals</command>
    673669      script for any processes that are not shut down by their own scripts.  The

  • chapter10/grub.xml

    r0cbb853 r688a8f5  
    2424    <para>
    2525      If you've installed GRUB for UEFI with optional dependencies following
    26       BLFS, you should skip this page, and configure GRUB with UEFI support
     26      BLFS, you should skip this page, and config GRUB with UEFI support
    2727      using the instructions provided in
    2828      <ulink url="&blfs-book;postlfs/grub-setup.html">the BLFS page</ulink>,
    … …  
    7171    the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis>
    7272    is the hard drive number and <emphasis>m</emphasis> is the partition
    73     number. The hard drive numbers start from zero, but the partition numbers
    74     start from one for normal partitions (from five for extended partitions).
     73    number. The hard drive number starts from zero, but the partition number
     74    starts from one for normal partitions and five for extended partitions.
    7575    Note that this is different from earlier versions where
    7676    both numbers started from zero. For example, partition <filename
    … …  
    121121    this, you will need to mount the separate partition, move all files in the
    122122    current <filename class="directory">/boot</filename> directory (e.g. the
    123     Linux kernel you just built in the previous section) to the new partition.
     123    linux kernel you just built in the previous section) to the new partition.
    124124    You will then need to unmount the partition and remount it as <filename
    125125    class="directory">/boot</filename>.  If you do this, be sure to update
    126126    <filename>/etc/fstab</filename>.</para>
    127127
    128     <para>Leaving <filename class="directory">/boot</filename> on
    129     the current LFS partition will also work, but configuration
     128    <para>Using the current lfs partition will also work, but configuration
    130129    for multiple systems is more difficult.</para>
    131130
    … …  
    233232      <filename>grub.cfg</filename> refers to some <quote>old</quote>
    234233      designators.  If you wish to avoid such a problem, you may use
    235       the UUID of a partition and the UUID of a filesystem instead of a GRUB designator to
    236       specify a device.
     234      the UUID of partition and filesystem instead of GRUB designator to
     235      specify a partition.
    237236      Run <command>lsblk -o UUID,PARTUUID,PATH,MOUNTPOINT</command> to show
    238       the UUIDs of your filesystems (in the <literal>UUID</literal> column) and
    239       partitions (in the <literal>PARTUUID</literal> column).  Then replace
     237      the UUID of your filesystems (in <literal>UUID</literal> column) and
     238      partitions (in <literal>PARTUUID</literal> column).  Then replace
    240239      <literal>set root=(hdx,y)</literal> with
    241       <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem
    242       where the kernel is installed&gt;</replaceable></literal>, and replace
     240      <literal>search --set=root --fs-uuid <replaceable>&lt;UUID of the filesystem where the kernel is installed&gt;</replaceable></literal>, and replace
    243241      <literal>root=/dev/sda2</literal> with
    244       <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS
    245       is built&gt;</replaceable></literal>.</para>
    246       <para>Note that the UUID of a partition is completely different from the
    247       UUID of the filesystem in this partition.  Some online resources may
     242      <literal>root=PARTUUID=<replaceable>&lt;UUID of the partition where LFS is built&gt;</replaceable></literal>.</para>
     243      <para>Note that the UUID of a partition and the UUID of the filesystem
     244      in this partition is completely different.  Some online resources may
    248245      instruct you to use
    249246      <literal>root=UUID=<replaceable>&lt;filesystem UUID&gt;</replaceable></literal>
    250247      instead of
    251248      <literal>root=PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,
    252       but doing so will require an initramfs, which is beyond the scope of
     249      but doing so will require an initramfs which is beyond the scope of
    253250      LFS.</para>
    254251      <para>The name of the device node for a partition in
    255       <filename class='directory'>/dev</filename> may also change (this is less
    256       likely than a GRUB designator change).  You can also replace
     252      <filename class='directory'>/dev</filename> may also change (more
     253      unlikely than GRUB designator change though).  You can also replace
    257254      paths to device nodes like <literal>/dev/sda1</literal> with
    258255      <literal>PARTUUID=<replaceable>&lt;partition UUID&gt;</replaceable></literal>,

  • git-version.sh

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

  • packages.ent

    r0cbb853 r688a8f5  
    5959<!ENTITY bash-fin-sbu "1.4 SBU">
    6060
    61 <!ENTITY bc-version "6.2.1">
    62 <!ENTITY bc-size "446 KB">
     61<!ENTITY bc-version "6.1.1">
     62<!ENTITY bc-size "445 KB">
    6363<!ENTITY bc-url "https://github.com/gavinhoward/bc/releases/download/&bc-version;/bc-&bc-version;.tar.xz">
    64 <!ENTITY bc-md5 "ad4b3546e5bd5cc6f46b887fb2992ae4">
     64<!ENTITY bc-md5 "9a7ffa015c499272e7d41b4c0f28e691">
    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.44">
    183 <!ENTITY file-size "1,159 KB">
     182<!ENTITY file-version "5.43">
     183<!ENTITY file-size "1,136 KB">
    184184<!ENTITY file-url "https://astron.com/pub/file/file-&file-version;.tar.gz">
    185 <!ENTITY file-md5 "a60d586d49d015d842b9294864a89c7a">
     185<!ENTITY file-md5 "8effd70da368210a6c6eece037f978eb">
    186186<!ENTITY file-home "https://www.darwinsys.com/file/">
    187187<!ENTITY file-tmp-du "34 MB">
    … …  
    318318<!ENTITY gzip-fin-sbu "0.3 SBU">
    319319
    320 <!ENTITY iana-etc-version "20221220">
    321 <!ENTITY iana-etc-size "586 KB">
     320<!ENTITY iana-etc-version "20221209">
     321<!ENTITY iana-etc-size "585 KB">
    322322<!ENTITY iana-etc-url "https://github.com/Mic92/iana-etc/releases/download/&iana-etc-version;/iana-etc-&iana-etc-version;.tar.gz">
    323 <!ENTITY iana-etc-md5 "b394b994883d01d8b33c80bc57917117">
     323<!ENTITY iana-etc-md5 "b5e3e7ee1f65edff9284e614000a3815">
    324324<!ENTITY iana-etc-home "https://www.iana.org/protocols">
    325325<!ENTITY iana-etc-fin-du "4.8 MB">
    … …  
    383383<!ENTITY less-fin-sbu "less than 0.1 SBU">
    384384
    385 <!ENTITY lfs-bootscripts-version "20230101">      <!-- Scripts depend on this format -->
     385<!ENTITY lfs-bootscripts-version "20220920">      <!-- Scripts depend on this format -->
    386386<!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">
    387387<!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz">
    … …  
    424424
    425425<!ENTITY linux-major-version "6">
    426 <!ENTITY linux-minor-version "1">
    427 <!ENTITY linux-patch-version "1">
     426<!ENTITY linux-minor-version "0">
     427<!ENTITY linux-patch-version "11">
    428428<!--<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;">-->
    429429<!ENTITY linux-version "&linux-major-version;.&linux-minor-version;.&linux-patch-version;">
    430 <!ENTITY linux-size "131,573 KB">
     430<!ENTITY linux-size "130,780 KB">
    431431<!ENTITY linux-url "&kernel;linux/kernel/v&linux-major-version;.x/linux-&linux-version;.tar.xz">
    432 <!ENTITY linux-md5 "3482feaa021961d10ac88e789788bf07">
     432<!ENTITY linux-md5 "7a47796e842b77519613abbca6037c91">
    433433<!ENTITY linux-home "https://www.kernel.org/">
    434434<!-- measured for 5.13.4 / gcc-11.1.0 on x86_64 : minimum is
    … …  
    472472<!ENTITY man-db-fin-sbu "0.4 SBU">
    473473
    474 <!ENTITY man-pages-version "6.02">
    475 <!ENTITY man-pages-size "1,759 KB">
     474<!ENTITY man-pages-version "6.01">
     475<!ENTITY man-pages-size "1,748 KB">
    476476<!ENTITY man-pages-url "&kernel;linux/docs/man-pages/man-pages-&man-pages-version;.tar.xz">
    477 <!ENTITY man-pages-md5 "05b9e8ce59f6257141fe9e4edd5bd149">
     477<!ENTITY man-pages-md5 "83b25a1a120df78ec4c01221a1926463">
    478478<!ENTITY man-pages-home "https://www.kernel.org/doc/man-pages/">
    479479<!ENTITY man-pages-fin-du "33 MB">
    … …  
    488488<!ENTITY markupsafe-fin-sbu "less than 0.1 SBU">
    489489
    490 <!ENTITY meson-version "1.0.0">
    491 <!ENTITY meson-size "2,051 KB">
     490<!ENTITY meson-version "0.64.1">
     491<!ENTITY meson-size "2,041 KB">
    492492<!ENTITY meson-url "&github;/mesonbuild/meson/releases/download/&meson-version;/meson-&meson-version;.tar.gz">
    493 <!ENTITY meson-md5 "009b78125467cd9ee4d467175a5c12e1">
     493<!ENTITY meson-md5 "9f260adfcbc66ed2e15047c6eb98e503">
    494494<!ENTITY meson-home "https://mesonbuild.com">
    495495<!ENTITY meson-fin-du "38 MB">
    496496<!ENTITY meson-fin-sbu "less than 0.1 SBU">
    497497
    498 <!ENTITY mpc-version "1.3.1">
     498<!ENTITY mpc-version "1.3.0">
    499499<!ENTITY mpc-size "756 KB">
    500500<!ENTITY mpc-url "https://ftp.gnu.org/gnu/mpc/mpc-&mpc-version;.tar.gz">
    501 <!ENTITY mpc-md5 "5c9bc658c9fd0f940e8e3e0f09530c62">
     501<!ENTITY mpc-md5 "b0f5e2ad6009781777ed026bcf71bf0e">
    502502<!ENTITY mpc-home "https://www.multiprecision.org/">
    503503<!ENTITY mpc-fin-du "21 MB">
    … …  
    655655<!ENTITY systemd-fin-sbu  "2.5 SBU">
    656656
    657 <!ENTITY sysvinit-version "3.06">
    658 <!ENTITY sysvinit-size "247 KB">
     657<!ENTITY sysvinit-version "3.05">
     658<!ENTITY sysvinit-size "229 KB">
    659659<!ENTITY sysvinit-url "&github;/slicer69/sysvinit/releases/download/&sysvinit-version;/sysvinit-&sysvinit-version;.tar.xz">
    660 <!ENTITY sysvinit-md5 "96771d0a88315c91199830ea49b859ca">
     660<!ENTITY sysvinit-md5 "57577060e5f21fd9899fa601aa45b064">
    661661<!ENTITY sysvinit-home "&savannah-nongnu;/projects/sysvinit">
    662662<!ENTITY sysvinit-fin-du "2.7 MB">

  • patches.ent

    r0cbb853 r688a8f5  
    8989-->
    9090<!ENTITY sysvinit-consolidated-patch "sysvinit-&sysvinit-version;-consolidated-1.patch">
    91 <!ENTITY sysvinit-consolidated-patch-md5 "17ffccbb8e18c39e8cedc32046f3a475">
    92 <!ENTITY sysvinit-consolidated-patch-size "2.5 KB">
     91<!ENTITY sysvinit-consolidated-patch-md5 "372d367918134f2f41daf54f2acf280a">
     92<!ENTITY sysvinit-consolidated-patch-size "2.4 KB">
    9393
    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 
     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-->
    9999<!--
    100100<!ENTITY xz-upstream-fix-patch "xz-&xz-version;-upstream_fix-1.patch">
Note: See TracChangeset for help on using the changeset viewer.