Changeset 328eb6f for chapter08


Ignore:
Timestamp:
02/27/2024 03:52:31 PM (5 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
xry111/arm64
Children:
e4e7ffb
Parents:
648f145 (diff), 23f4367 (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/arm64

Location:
chapter08
Files:
23 edited

Legend:

Unmodified
Added
Removed
  • chapter08/bash.xml

    r648f145 r328eb6f  
    4141    <title>Installation of Bash</title>
    4242
     43    <para>First, fix some issues identified upstream:</para>
     44
     45<screen><userinput remap="pre">patch -Np1 -i ../&bash-upstream-fixes-patch;</userinput></screen>
     46
    4347    <para>Prepare Bash for compilation:</para>
    4448
     
    7276    <para>To prepare the tests, ensure that the <systemitem class="username">tester</systemitem> user can write to the sources tree:</para>
    7377
    74 <screen><userinput remap="test">chown -Rv tester .</userinput></screen>
     78<screen><userinput remap="test">chown -R tester .</userinput></screen>
    7579
    7680    <para>The test suite of this package is designed to be run as a non-&root;
     
    8084    class="username">tester</systemitem> user:</para>
    8185
    82 <screen><userinput remap="test">su -s /usr/bin/expect tester &lt;&lt; EOF
     86<screen><userinput remap="test">su -s /usr/bin/expect tester &lt;&lt; "EOF"
    8387set timeout -1
    8488spawn make tests
  • chapter08/binutils.xml

    r648f145 r328eb6f  
    136136<screen><userinput remap="test">grep '^FAIL:' $(find -name '*.log')</userinput></screen>
    137137
    138     <para>Three tests in the gprofng suite are known to fail.</para>
     138 <!--    <para>Three tests in the gprofng suite are also known to fail.</para>-->
    139139
    140140    <para>Install the package:</para>
  • chapter08/coreutils.xml

    r648f145 r328eb6f  
    122122    compile and run the tests:</para>
    123123
    124 <screen><userinput remap="test">chown -Rv tester . </userinput></screen>
     124<screen><userinput remap="test">chown -R tester . </userinput></screen>
    125125
    126126    <para>Now run the tests:</para>
     
    130130<!-- Sometimes skipped, but if not it may fail.
    131131     Please DO NOT remove or comment out this unless we can fully
    132      understand it!  -->
     132     understand it!
    133133    <para>The test-getlogin test may fail in the LFS chroot environment.</para>
     134    20240226: Commented out as it seems the upstream has root-caused and
     135    fixed the issue.  I've checked the fix is in Coreutils 9.4 release
     136    tarball:
     137
     138    https://lists.gnu.org/archive/html/bug-gnulib/2022-06/msg00079.html
     139-->
    134140
    135141    <para>Remove the temporary group:</para>
     
    12621268        <term><command>yes</command></term>
    12631269        <listitem>
    1264           <para>Repeatedly outputs <quote>y</quote>, or a given string, until
    1265           killed</para>
     1270          <para>Repeatedly outputs <literal>y</literal> or a given string,
     1271          until killed</para>
    12661272          <indexterm zone="ch-system-coreutils yes">
    12671273            <primary sortas="b-yes">yes</primary>
  • chapter08/e2fsprogs.xml

    r648f145 r328eb6f  
    160160
    161161    <para>
    162       Read the man page <filename>mke2fs.conf(5)</filename> for details.
     162      Read the man page <ulink role='man'
     163      url='&man;mke2fs.conf.5'>mke2fs.conf(5)</ulink> for details.
    163164    </para>
    164165  </sect2>
  • chapter08/expect.xml

    r648f145 r328eb6f  
    4949    <title>Installation of Expect</title>
    5050
     51    <para>Expect needs PTYs to work.  Verify that the PTYs are working
     52    properly inside the chroot environment by performing a simple
     53    test:</para>
     54
     55<screen><userinput remap="test">python3 -c 'from pty import spawn; spawn(["echo", "ok"])'</userinput></screen>
     56
     57    <para>This command should output <computeroutput>ok</computeroutput>.
     58    If, instead, the output includes <computeroutput>OSError: out of pty
     59    devices</computeroutput>, then the environment is not set up for proper
     60    PTY operation.  You need to exit from the chroot environment, read
     61    <xref linkend='ch-tools-kernfs'/> again, and ensure the
     62    <systemitem class="filesystem">devpts</systemitem> file system (and
     63    other virtual kernel file systems) mounted correctly.  Then reenter
     64    the chroot environment following <xref linkend='ch-tools-chroot'/>.
     65    This issue needs to be resolved before continuing, or the test suites
     66    requiring Expect (for example the test suites of Bash, Binutils, GCC,
     67    GDBM, and of course Expect itself) will fail catastrophically, and other
     68    subtle breakages may also happen.</para>
     69
    5170    <para>Update two config scripts to allow building this package for
    5271    AArch64:</para>
     
    89108<screen><userinput remap="make">make</userinput></screen>
    90109
    91     <important>
    92       <para>The test suite for Expect is considered critical.
    93       Do not skip it under any circumstances.</para>
    94     </important>
    95 
    96110    <para>To test the results, issue:</para>
    97111
    98112<screen><userinput remap="test">make test</userinput></screen>
    99 
    100     <para>If any test fails with the message
    101     <quote><computeroutput>The system has no more ptys.  Ask your system
    102     administrator to create more</computeroutput></quote>, it indicates
    103     you've not mounted the
    104     <systemitem class="filesystem">devpts</systemitem> file system
    105     correctly.  You need to exit from the chroot environment, read
    106     <xref linkend='ch-tools-kernfs'/> again, and ensure the
    107     <systemitem class="filesystem">devpts</systemitem> file system (and
    108     other virtual kernel file systems) mounted correctly.  Then reenter
    109     the chroot environment following <xref linkend='ch-tools-chroot'/>.
    110     This issue needs to be resolved before continuing.</para>
    111113
    112114    <para>Install the package:</para>
  • chapter08/findutils.xml

    r648f145 r328eb6f  
    8383    <para>To test the results, issue:</para>
    8484
    85 <screen><userinput remap="test">chown -Rv tester .
     85<screen><userinput remap="test">chown -R tester .
    8686su tester -c "PATH=$PATH make check"</userinput></screen>
    8787
  • chapter08/gawk.xml

    r648f145 r328eb6f  
    5555    <para>To test the results, issue:</para>
    5656
    57 <screen><userinput remap="test">chown -Rv tester .
     57<screen><userinput remap="test">chown -R tester .
    5858su tester -c "PATH=$PATH make check"</userinput></screen>
    5959
  • chapter08/gcc.xml

    r648f145 r328eb6f  
    155155    <para>Test the results as a non-privileged user, but do not stop at errors:</para>
    156156
    157 <screen><userinput remap="test">chown -Rv tester .
     157<screen><userinput remap="test">chown -R tester .
    158158su tester -c "PATH=$PATH make -k check"</userinput></screen>
    159159
     
    171171    <para>
    172172    <!-- https://gcc.gnu.org/PR107915 and https://gcc.gnu.org/PR109353 -->
    173     Two tests named <filename>copy.cc</filename> and
    174     <filename>contracts-tmpl-spec2.C</filename> are known to fail.
     173    One test named <filename>contracts-tmpl-spec2.C</filename> is known to fail.
    175174    <!-- https://gcc.gnu.org/PR111224 -->
    176175    Some C++ module tests named <filename>xtreme-*</filename> are known to
     
    182181
    183182    <para>
    184       With Glibc-2.38, the analyzer tests named
    185       <filename>data-model-4.c</filename> and
    186       <filename>conftest-1.c</filename>
    187         are known to fail.
    188       In the asan tests, several tests in <filename>asan_test.C</filename>
    189         are known to fail.
    190       The test named <filename>interception-malloc-test-1.C</filename>
    191         is known to fail.
     183    Eight gcc tests (out of over 185,000):
     184    <!-- https://gcc.gnu.org/PR106375 --><filename>pr56837.c</filename>
     185    and seven tests in the <filename class='directory'>analyzer</filename>
     186    directory are known to fail.
     187
     188    <!-- https://gcc.gnu.org/PR109353 -->
     189    One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is
     190    known to fail.
     191
     192    For g++, 21 tests (out of approximately 250,000): 14
     193    <quote>AddressSanitizer*</quote>
     194    tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
     195    known to fail.
    192196    </para>
    193197
     
    196200    Unless the test results are vastly different from those at the above URL,
    197201    it is safe to continue.</para>
    198 
    199     <!--note><para>
    200       On some combinations of kernel configuration and AMD processors
    201       there may be more than 1100 failures in the gcc.target/i386/mpx
    202       tests (which are designed to test the MPX option on recent
    203       Intel processors). These can safely be ignored on AMD
    204       processors. These tests will also fail on Intel processors if MPX support
    205       is not enabled in the kernel even though it is present on the CPU.
    206     </para></note-->
    207202
    208203    <para>Install the package:</para>
  • chapter08/glibc.xml

    r648f145 r328eb6f  
    5050
    5151<screen><userinput remap="pre">patch -Np1 -i ../&glibc-fhs-patch;</userinput></screen>
    52 
     52<!--
    5353    <para>Now fix two security vulnerabilities and a regression causing the
    5454    posix_memalign() function very slow in some conditions:</para>
    5555
    5656<screen><userinput remap="pre">patch -Np1 -i ../&glibc-upstream-fixes-patch;</userinput></screen>
    57 
     57-->
    5858    <para>The Glibc documentation recommends building Glibc
    5959    in a dedicated build directory:</para>
     
    7474             --enable-kernel=&min-kernel;                     \
    7575             --enable-stack-protector=strong          \
    76              --with-headers=/usr/include              \
    7776             --disable-nscd                           \
    7877             libc_cv_slibdir=/usr/lib</userinput></screen>
     
    104103          <para>This option increases system security by adding
    105104          extra code to check for buffer overflows, such as stack
    106           smashing attacks.</para>
    107         </listitem>
    108       </varlistentry>
    109 <!-- do we need this one? -->
    110       <varlistentry>
    111         <term><parameter>--with-headers=/usr/include</parameter></term>
    112         <listitem>
    113           <para>This option tells the build system where to find the
    114           kernel API headers.</para>
     105          smashing attacks.  Note that Glibc always explicitly overrides
     106          the default of GCC, so this option is still needed even though
     107          we've already specified <option>--enable-default-ssp</option> for
     108          GCC.</para>
    115109        </listitem>
    116110      </varlistentry>
     
    170164      </listitem>
    171165
    172 <!-- Did not fail with glibc-2.38
    173       <listitem>
    174         <para><emphasis>misc/tst-ttyname</emphasis>
    175         is known to fail in the LFS chroot environment.</para>
    176       </listitem>
    177 -->
    178 
    179       <!-- https://sourceware.org/pipermail/libc-alpha/2022-August/141567.html -->
    180       <listitem>
    181         <para>The <emphasis>stdlib/tst-arc4random-thread</emphasis>
    182         test is known to fail if the host kernel is relatively old.</para>
    183       </listitem>
    184 
    185166      <listitem>
    186167        <para>Some tests, for example
    187         <emphasis>nss/tst-nss-files-hosts-multi</emphasis>,
    188         are known to fail on relatively slow systems due to an internal
    189         timeout.</para>
     168        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> and
     169        <emphasis>nptl/tst-thread-affinity*</emphasis>
     170        are known to fail due to a timeout (especially when the system is
     171        relatively slow and/or running the test suite with multiple
     172        parallel make jobs).  These tests can be identified with:</para>
     173
     174        <!-- TODO: Using nodump for freeze.  Change it to role="test" after
     175             12.1 release so jhalfs can list these in the log.  -->
     176        <screen role="nodump"><userinput>grep "Timed out" -l $(find -name \*.out)</userinput></screen>
     177
     178        <para>It's possible to re-run a single test with enlarged timeout
     179        with
     180        <command>TIMEOUTFACTOR=<replaceable>&lt;factor&gt;</replaceable>
     181        make test t=<replaceable>&lt;test name&gt;</replaceable></command>.
     182        For example, <command>TIMEOUTFACTOR=10 make test
     183        t=nss/tst-nss-files-hosts-multi</command> will re-run
     184        <emphasis>nss/tst-nss-files-hosts-multi</emphasis> with ten times
     185        the original timeout.</para>
    190186      </listitem>
    191187
    192188      <listitem>
    193189        <para>Additionally, some tests may fail with a relatively old CPU
    194         model or host kernel version.</para>
     190        model (for example
     191        <emphasis>elf/tst-cpu-features-cpuinfo</emphasis>) or host kernel
     192        version (for example
     193        <emphasis>stdlib/tst-arc4random-thread</emphasis>).</para>
    195194      </listitem>
    196195    </itemizedlist>
     
    207206
    208207<screen><userinput remap="install">sed '/test-installation/s@$(PERL)@echo not running@' -i ../Makefile</userinput></screen>
     208
     209    <important>
     210      <para>
     211        If upgrading Glibc to a new minor version (for example, from
     212        Glibc-2.36 to Glibc-&glibc-version;) on a running LFS system, you
     213        need to take some extra precautions to avoid breaking the system:
     214      </para>
     215
     216      <itemizedlist>
     217        <listitem>
     218          <!-- There are two reasons we don't support this:
     219               1. Upgrading on a system with separate /lib and /usr/lib is
     220                  tricky.
     221               2. With Glibc prior to 2.34 libc.so.6 etc. are symlinks to
     222                  libc-2.33.so etc., again causing the upgradation tricky.
     223                  The Glibc NEWS file explicit states they no longer use
     224                  symlinks for the ABI names to avoid upgradation
     225                  issues.  -->
     226          <para>
     227            Upgrading Glibc on a LFS system prior to 11.0 (exclusive) is
     228            not supported.  Rebuild LFS if you are running such an old LFS
     229            system but you need a newer Glibc.
     230          </para>
     231        </listitem>
     232
     233        <!-- https://sourceware.org/pipermail/libc-alpha/2024-January/154095.html -->
     234        <listitem>
     235          <para>
     236            If upgrading on a LFS system prior to 12.0 (exclusive), install
     237            <application>Libxcrypt</application> following
     238            <xref role='.' linkend='ch-system-libxcrypt'/>  In addition to
     239            a normal <application>Libxcrypt</application> installation,
     240            <emphasis role='bold'>you MUST follow the note in Libxcrypt
     241            section to install
     242            <filename class='libraryfile'>libcrypt.so.1*</filename>
     243            (replacing
     244            <filename class='libraryfile'>libcrypt.so.1</filename> from the
     245            prior Glibc installation)</emphasis>.
     246          </para>
     247        </listitem>
     248
     249        <!-- Otherwise on lfs-systemd nscd will fail to start on boot,
     250             and on both lfs-sysv and lfs-systemd useradd etc. will try
     251             to start nscd, then nscd will fail to start as well and
     252             produce some spurious error message.  -->
     253        <listitem>
     254          <para>
     255            If upgrading on a LFS system prior to 12.1 (exclusive),
     256            remove the <command>nscd</command> program:
     257          </para>
     258
     259          <screen role='nodump'><userinput>rm -f /usr/sbin/nscd</userinput></screen>
     260
     261          <para revision='systemd'>
     262            If this system (prior to LFS 12.1, exclusive) is based on
     263            Systemd, it's also needed to disable and stop the
     264            <command>nscd</command> service now:
     265          </para>
     266
     267          <screen revision='systemd' role='nodump'><userinput>systemctl disable --now nscd</userinput></screen>
     268        </listitem>
     269
     270        <listitem>
     271          <para>
     272            Upgrade the kernel and reboot if it's older than &min-kernel;
     273            (check the current version with <command>uname -r</command>)
     274            or if you want to upgrade it anyway, following
     275            <xref linkend='ch-bootable-kernel' role='.'/>
     276          </para>
     277        </listitem>
     278
     279        <listitem>
     280          <para>
     281            Upgrade the kernel API headers if it's older than &min-kernel;
     282            (check the current version with
     283            <command>cat /usr/include/linux/version.h</command>)
     284            or if you want to upgrade it anyway, following
     285            <xref linkend='ch-tools-linux-headers'/> (but removing
     286            <envar>$LFS</envar> from the <command>cp</command> command).
     287          </para>
     288        </listitem>
     289
     290        <!-- This is to ensure we don't start a process at the time point
     291             where some Glibc shared libraries are updated but the others
     292             are not.  Such mismatches can cause programs crash on startup,
     293             esp. a mismatch between ld-linux-x86-64.so.2 and
     294             libc.so.6.  Note that a crash in the installation process
     295             will leave the system in a state with the mismatch forever,
     296             unrecoverable without the help of another distro.  -->
     297        <listitem>
     298          <para>
     299            Perform a <envar>DESTDIR</envar> installation and upgrade
     300            the Glibc shared libraries on the system using one single
     301            <command>install</command> command:
     302          </para>
     303
     304          <screen role='nodump'><userinput>make DESTDIR=$PWD/dest install
     305install -vm755 dest/usr/lib/*.so.* /usr/lib</userinput></screen>
     306        </listitem>
     307      </itemizedlist>
     308
     309      <para>
     310        It's imperative to strictly follow these steps above unless you
     311        completely understand what you are doing.
     312        <emphasis role='bold'>Any unexpected deviation may render the
     313        system completely unusable.  YOU ARE WARNED.</emphasis>
     314      </para>
     315
     316      <para>
     317        Then continue to run the <command>make install</command> command,
     318        the <command>sed</command> command against
     319        <filename>/usr/bin/ldd</filename>, and the commands to install
     320        the locales.  Once they are finished, reboot the system
     321        immediately.
     322      </para>
     323    </important>
    209324
    210325    <para>Install the package:</para>
     
    421536        <listitem>
    422537          <para>This creates the <filename>posixrules</filename> file. We use
    423           New York because POSIX requires the daylight savings time rules
     538          New York because POSIX requires the daylight saving time rules
    424539          to be in accordance with US rules.</para>
    425540        </listitem>
  • chapter08/gmp.xml

    r648f145 r328eb6f  
    5050
    5151      <!-- To editors: the configure script says "the none host is obsolete,
    52            use - -disable-assembly", but don't believe it: with the latter
     52           use - -disable-assembly," but don't believe it: with the latter
    5353           CFLAGS is still automatically set to -march=something.  -->
    5454    </note>
     
    9898    it is built. Occasionally, the code that detects the processor misidentifies
    9999    the system capabilities and there will be errors in the tests or other
    100     applications using the gmp libraries with the message "Illegal
    101     instruction".  In this case, gmp should be reconfigured with the option
     100    applications using the gmp libraries with the message
     101    <computeroutput>Illegal instruction</computeroutput>.
     102    In this case, gmp should be reconfigured with the option
    102103    <option>--host=none-linux-gnu</option> and rebuilt.</para></caution>
    103104
  • chapter08/libtool.xml

    r648f145 r328eb6f  
    5757    <para>Five tests are known to fail in the LFS build environment due
    5858    to a circular dependency, but these tests pass if rechecked after
    59     automake has been installed.  Additionally, with grep-3.8, two tests will
    60     trigger a warning for non-POSIX regular expressions and fail.</para>
     59    automake has been installed.  Additionally, with grep-3.8 or newer,
     60    two tests will trigger a warning for non-POSIX regular expressions and
     61    fail.</para>
    6162
    6263    <para>Install the package:</para>
  • chapter08/libxcrypt.xml

    r648f145 r328eb6f  
    111111            --disable-failure-tokens
    112112make
    113 cp -av .libs/libcrypt.so.1* /usr/lib</userinput></screen>
     113cp -av --remove-destination .libs/libcrypt.so.1* /usr/lib</userinput></screen>
    114114    </note>
    115115
  • chapter08/make.xml

    r648f145 r328eb6f  
    5454    <para>To test the results, issue:</para>
    5555
    56 <screen><userinput remap="test">chown -Rv tester .
     56<screen><userinput remap="test">chown -R tester .
    5757su tester -c "PATH=$PATH make check"</userinput></screen>
    5858
  • chapter08/openssl.xml

    r648f145 r328eb6f  
    164164            of <application>OpenSSL</application>'s crypto library from the
    165165            shell. It can be used for various functions which are documented in
    166             <filename>openssl(1)</filename>
     166            <ulink role='man' url='&man;openssl.1'>openssl(1)</ulink>
    167167          </para>
    168168          <indexterm zone="ch-system-openssl openssl-prog">
     
    196196            implements the Transport Layer Security (TLS v1) protocol.
    197197            It provides a rich API, documentation
    198             on which can be found in <filename>ssl(7)</filename>
     198            on which can be found in <ulink role='man'
     199            url='&man;ssl.7'>ssl(7)</ulink>
    199200          </para>
    200201          <indexterm zone="ch-system-openssl libssl">
  • chapter08/pkgconf.xml

    r648f145 r328eb6f  
    4444
    4545    <title>Installation of Pkgconf</title>
    46 
    47     <!-- https://github.com/pkgconf/pkgconf/issues/317 -->
    48     <para>Fix a regression in pkgconf-2.1.0 breaking BLFS packages:</para>
    49 
    50     <screen><userinput remap="pre">patch -Np1 -i ../&pkgconf-upstream-fix-patch;</userinput></screen>
    5146
    5247    <para>Prepare Pkgconf for compilation:</para>
  • chapter08/pkgmgt.xml

    r648f145 r328eb6f  
    5757        The system will keep working fine thanks to the well-defined interface
    5858        between the kernel and userspace.  Specifically, Linux API headers
    59         need not be (and should not be, see the next item) upgraded
     59        need not be upgraded
    6060        along with the kernel.  You will merely need to reboot your system to use the
    6161        upgraded kernel.</para>
     
    6363
    6464      <listitem>
    65         <para>If the Linux API headers or Glibc need to be upgraded to a newer
    66         version, (e.g.,  from Glibc-2.31 to Glibc-2.32), it is safer to
    67         rebuild LFS.  Though you <emphasis>may</emphasis> be able to rebuild
    68         all the packages in their dependency order, we do not recommend
    69         it.  </para>
    70       </listitem>
    71 
    72       <listitem>
    73         <para>Reinstalling the same version of Glibc (&glibc-version; for
    74         this release of LFS) with patches should be safe when these patches
    75         do not change ABI and API.  When a security vulnerability is found
    76         in Glibc, we often need to apply such a patch to fix the
    77         vulnerability and reinstall Glibc.  Consult
    78         <ulink url='&lfs-root;lfs/advisories/'>LFS security
    79         advisories</ulink> if you are alerted for a published Glibc security
    80         vulnerability but unsure about the action to take.</para>
     65        <para>If Glibc needs to be upgraded to a newer
     66        version, (e.g.,  from Glibc-2.36 to Glibc-&glibc-version;),
     67        some extra steps are needed to avoid breaking the system.
     68        Read <xref linkend='ch-system-glibc'/> for details.</para>
    8169      </listitem>
    8270
  • chapter08/procps.xml

    r648f145 r328eb6f  
    7373    <para> To run the test suite, run:</para>
    7474
    75 <screen><userinput remap="test">make check</userinput></screen>
     75<screen><userinput remap="test">make -k check</userinput></screen>
     76
     77    <para>One test named
     78    <literal>ps with output flag bsdtime,cputime,etime,etimes</literal>
     79    is known to fail if the host kernel is not built with
     80    <literal>CONFIG_BSD_PROCESS_ACCT</literal> enabled.
     81    <!-- These two tests just do not work as root but they seem to pass
     82         in most time due to some internal hazards of Tcl/Expect/DejaGNU
     83         framework.  However the failures have been really observed.
     84         TODO: run the test suite as tester after the freeze ends.  -->
     85    Two tests named
     86    <literal>pmap X with unreachable process</literal> and
     87    <literal>pmap XX with unreachable process</literal> are known to
     88    fail occasionally.</para>
    7689
    7790    <para>Install the package:</para>
  • chapter08/sed.xml

    r648f145 r328eb6f  
    5252    <para>To test the results, issue:</para>
    5353
    54 <screen><userinput remap="test">chown -Rv tester .
     54<screen><userinput remap="test">chown -R tester .
    5555su tester -c "PATH=$PATH make check"</userinput></screen>
    5656
  • chapter08/shadow.xml

    r648f145 r328eb6f  
    204204    parameter to <command>useradd</command>, or else change the setting of
    205205    <parameter>USERGROUPS_ENAB</parameter> in
    206     <filename>/etc/login.defs</filename>. See <filename>useradd(8)</filename>
    207     for more information.</para>
     206    <filename>/etc/login.defs</filename>. See <ulink role='man'
     207    url='&man;useradd.8'>useradd(8)</ulink> for more information.</para>
    208208
    209209    <para>Second, to change the default parameters, the file
  • chapter08/stripping.xml

    r648f145 r328eb6f  
    5454  The construct below selects the
    5555  correct name for the current architecture, excluding anything ending
    56   with <quote>g</quote>, in case the commands below have already been
     56  with <literal>g</literal>, in case the commands below have already been
    5757  run.</para></note>
    5858
  • chapter08/systemd.xml

    r648f145 r328eb6f  
    5151    <!-- https://github.com/systemd/systemd/pull/30549 -->
    5252    <para>Now fix a security vulnerability in the DNSSEC verification of
    53     <command>systemd-resolved</command>:</para>
    54 
    55 <screen><userinput remap='pre'>sed -e '/return FLAGS_SET.*AUTHENTICATED/s/(t/(dt/' \
    56     -i src/resolve/resolved-dns-transaction.c</userinput></screen>
     53    <command>systemd-resolved</command> and a bug breaking running
     54    <command>systemd-analyze verify</command> on an instantiated systemd
     55    unit:</para>
     56
     57<screen><userinput remap='pre'>patch -Np1 -i ../&systemd-upstream-patch;</userinput></screen>
    5758
    5859    <para>Prepare systemd for compilation:</para>
  • chapter08/util-linux.xml

    r648f145 r328eb6f  
    104104    </warning>
    105105
    106 <screen><userinput remap="test">chown -Rv tester .
     106<screen><userinput remap="test">chown -R tester .
    107107su tester -c "make -k check"</userinput></screen>
    108108
     
    575575        <listitem>
    576576          <para>Displays kernel interrupt counter information in
    577           <filename>top(1)</filename> style view</para>
     577          <ulink role='man' url='&man;top.1'>top(1)</ulink> style
     578          view</para>
    578579          <indexterm zone="ch-system-util-linux irqtop">
    579580            <primary sortas="b-irqtop">irqtop</primary>
  • chapter08/vim.xml

    r648f145 r328eb6f  
    6767    to the source tree:</para>
    6868
    69 <screen><userinput remap="test">chown -Rv tester .</userinput></screen>
     69<screen><userinput remap="test">chown -R tester .</userinput></screen>
    7070
    7171    <para>Now run the tests as user <systemitem
    7272    class="username">tester</systemitem>:</para>
    7373
    74 <screen><userinput remap="test">su tester -c "LANG=en_US.UTF-8 make -j1 test" &amp;> vim-test.log</userinput></screen>
     74<screen><userinput remap="test">su tester -c "TERM=xterm-256color LANG=en_US.UTF-8 make -j1 test" \
     75   &amp;> vim-test.log</userinput></screen>
    7576
    7677    <para>The test suite outputs a lot of binary data to the screen.  This can
    77     cause issues with the settings of the current terminal.  The problem can be
     78    cause issues with the settings of the current terminal (especially while
     79    we are overriding the <envar>TERM</envar> variable to satisify some
     80    assumptions of the test suite).  The problem can be
    7881    avoided by redirecting the output to a log file as shown above.  A
    79     successful test will result in the words "ALL DONE" in the log file
    80     at completion.</para>
     82    successful test will result in the words <computeroutput>ALL
     83    DONE</computeroutput> in the log file at completion.</para>
    8184
    8285    <para>Install the package:</para>
Note: See TracChangeset for help on using the changeset viewer.