Changeset 9e7475a for chapter09


Ignore:
Timestamp:
06/12/2020 09:04:48 PM (4 years ago)
Author:
Douglas R. Reno <renodr@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
4234aea6
Parents:
a3d0817
Message:

Updates to chapter09 for systemd

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/cross2@11929 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter09
Files:
8 edited

Legend:

Unmodified
Added
Removed

  • chapter09/clock.xml

    ra3d0817 r9e7475a  
    1717  <para>This section discusses how to configure the
    1818  <command>systemd-timedated</command> system service, which configures
    19   system clock and timezone.</para>
     19  the system clock and timezone.</para>
    2020
    2121  <para>If you cannot remember whether or not the hardware clock is set to UTC,
    … …  
    3131
    3232  <para><command>systemd-timedated</command> reads <filename>/etc/adjtime</filename>,
    33   and depending on the contents of the file, it sets the clock to either UTC or
     33  and depending on the contents of the file, sets the clock to either UTC or
    3434  local time.</para>
    3535
    … …  
    6060<screen role="nodump"><userinput>timedatectl set-time YYYY-MM-DD HH:MM:SS</userinput></screen>
    6161
    62   <para>Hardware clock will also be updated accordingly.</para>
     62  <para>The hardware clock will also be updated accordingly.</para>
    6363
    6464  <para>To change your current time zone, issue:</para>

  • chapter09/consoled.xml

    ra3d0817 r9e7475a  
    2525  language-specific HOWTOs can also help with this, see <ulink
    2626  url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>.
    27   Examine <command>localectl list-keymaps</command> output for a list of
    28   valid console keymaps. Look in
     27  Examine the output of <command>localectl list-keymaps</command> for a list of
     28  valid console keymaps. Look in the
    2929  <filename class="directory">/usr/share/consolefonts</filename>
    3030  directory for valid screen fonts.</para>
    … …  
    107107      <term>list-x11-keymap-models</term>
    108108      <listitem>
    109         <para>Show known X11 keyboard mapping models.</para>
     109        <para>Shows known X11 keyboard mapping models.</para>
    110110      </listitem>
    111111    </varlistentry>
    … …  
    114114      <term>list-x11-keymap-layouts</term>
    115115      <listitem>
    116         <para>Show known X11 keyboard mapping layouts.</para>
     116        <para>Shows known X11 keyboard mapping layouts.</para>
    117117      </listitem>
    118118    </varlistentry>
    … …  
    121121      <term>list-x11-keymap-variants</term>
    122122      <listitem>
    123         <para>Show known X11 keyboard mapping variants.</para>
     123        <para>Shows known X11 keyboard mapping variants.</para>
    124124      </listitem>
    125125    </varlistentry>
    … …  
    128128      <term>list-x11-keymap-options</term>
    129129      <listitem>
    130         <para>Show known X11 keyboard mapping options.</para>
     130        <para>Shows known X11 keyboard mapping options.</para>
    131131      </listitem>
    132132    </varlistentry>
    … …  
    135135
    136136  <note><para>Using any of the parameters listed above requires the
    137   XKeyboard Config package from BLFS.</para></note>
     137  XKeyboard-Config package from BLFS.</para></note>
    138138
    139139</sect1>

  • chapter09/etcshells.xml

    ra3d0817 r9e7475a  
    2929  <para>For example, this file is consulted by <command>chsh</command>
    3030  to determine whether an unprivileged user may change the login shell for her
    31   own account. If the command name is not listed, the user will be denied of
    32   change.</para>
     31  own account. If the command name is not listed, the user will be denied the
     32  ability to change shells.</para>
    3333
    3434  <para>It is a requirement for applications such as

  • chapter09/introductiond.xml

    ra3d0817 r9e7475a  
    3939  </itemizedlist>
    4040
    41   <para>Third, configuring the system clock and keyboard layout.</para>
     41  <para>Third, configuring the system clock and keyboard layout is shown.</para>
    4242
    4343  <itemizedlist>
    … …  
    5050  </itemizedlist>
    5151
    52 
    5352  <para>Fourth, a brief introduction to the scripts and configuration
    54   files used when the user logs into the system.</para>
     53  files used when the user logs into the system is presented.</para>
    5554
    5655  <itemizedlist>
    … …  
    6362  </itemizedlist>
    6463
    65   <para>And finally, configuring the systemd behavior.</para>
     64  <para>And finally, configuring the behavior of systemd is discussed.</para>
    6665
    6766  <itemizedlist>

  • chapter09/locale.xml

    ra3d0817 r9e7475a  
    1515  </indexterm>
    1616
    17   <para>The <filename>/etc/locale.conf</filename> below sets some
     17  <para>The <filename>/etc/locale.conf</filename> file below sets some
    1818  environment variables necessary for native language support. Setting
    1919  them properly results in:</para>
    … …  
    2121  <itemizedlist>
    2222    <listitem>
    23       <para>The output of programs translated into the native language</para>
     23      <para>The output of programs being translated into your native language</para>
    2424    </listitem>
    2525    <listitem>
    26       <para>Correct classification of characters into letters, digits and other
     26      <para>The correct classification of characters into letters, digits and other
    2727      classes. This is necessary for <command>bash</command> to properly accept
    2828      non-ASCII characters in command lines in non-English locales</para>
    … …  
    3232    </listitem>
    3333    <listitem>
    34       <para>Appropriate default paper size</para>
     34      <para>The appropriate default paper size</para>
    3535    </listitem>
    3636    <listitem>
    37       <para>Correct formatting of monetary, time, and date values</para>
     37      <para>The correct formatting of monetary, time, and date values</para>
    3838    </listitem>
    3939  </itemizedlist>
    4040
    4141  <para>Replace <replaceable>&lt;ll&gt;</replaceable> below with the two-letter code
    42   for the desired language (e.g., <quote>en</quote>) and
     42  for your desired language (e.g., <quote>en</quote>) and
    4343  <replaceable>&lt;CC&gt;</replaceable> with the two-letter code for the appropriate
    4444  country (e.g., <quote>GB</quote>). <replaceable>&lt;charmap&gt;</replaceable> should
    … …  
    5555  Some applications cannot handle the various synonyms correctly (e.g., require
    5656  that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
    57   <quote>utf8</quote>), so it is safest in most
     57  <quote>utf8</quote>), so it is the safest in most
    5858  cases to choose the canonical name for a particular locale. To determine
    5959  the canonical name, run the following command, where <replaceable>&lt;locale
    … …  
    8181  before the telephone number in order to get into the country. If any of the
    8282  commands above fail with a message similar to the one shown below, this means
    83   that your locale was either not installed in Chapter&nbsp;6 or is not supported by
    84   the default installation of Glibc.</para>
     83  that your locale was either not installed in Chapter&nbsp;6 or is not
     84  supported by the default installation of Glibc.</para>
    8585
    8686<screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen>
    … …  
    9191  Glibc.</para>
    9292
    93   <!-- FIXME: the xlib example will became obsolete real soon -->
     93  <!-- FIXME: the xlib example will become obsolete in the future.-->
    9494  <para>Some packages beyond LFS may also lack support for your chosen locale. One
    9595  example is the X library (part of the X Window System), which outputs the
    … …  
    143143  mail with such characters from Mutt or Pine results in non-RFC-conforming
    144144  messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
    145   8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that
    146   you will never need 8-bit characters.</para>
     145  8-bit</quote>). It's suggested that you use the <quote>C</quote> locale only
     146  if you are certain that you will never need 8-bit characters.</para>
    147147
     148<!--
    148149  <para>UTF-8 based locales are not supported well by many programs.
    149150  Work is in progress to document and, if possible, fix such problems, see
    150151  <ulink url="&blfs-book;introduction/locale-issues.html"/>.</para>
     152-->
    151153
    152154</sect1>

  • chapter09/networkd.xml

    ra3d0817 r9e7475a  
    4949      <para>
    5050        Udev normally assigns network card interface names based
    51         on system physical characteristics such as enp2s1. If you are
     51        on physical system characteristics such as enp2s1. If you are
    5252        not sure what your interface name is, you can always run
    5353        <command>ip link</command> after you have booted your system.
    … …  
    7777             Create a manual naming scheme, for example by naming the
    7878             interfaces something like "internet0", "dmz0", or "lan0".
    79              For that, create .link
    80              files in /etc/systemd/network/, that choose an explicit name or a
    81              better naming scheme for one, some, or all of your interfaces.
    82              For example:
     79             To do that, create .link files in /etc/systemd/network/ that
     80             select an explicit name or a better naming scheme for your
     81             network interfaces. For example:
    8382          </para>
    8483
    … …  
    171170      <note><para>If using another means to configure your network
    172171      interfaces (ex: ppp, network-manager, etc.), or if using any type of
    173       local resolver (ex: bind, dnsmasq, etc.), or any other software that
    174       generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf), the
    175       <command>systemd-resolved</command> service should not be
     172      local resolver (ex: bind, dnsmasq, unbound, etc.), or any other software
     173      that generates an <filename>/etc/resolv.conf</filename> (ex: resolvconf),
     174      the <command>systemd-resolved</command> service should not be
    176175      used.</para></note>
    177176
    … …  
    207206      <para>Replace
    208207      <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
    209       with the IP address of the DNS most appropriate for the setup. There will
    210       often be more than one entry (requirements demand secondary servers for
    211       fallback capability). If you only need or want one DNS server, remove the
    212       second <emphasis>nameserver</emphasis> line from the file. The IP address
    213       may also be a router on the local network.</para>
     208      with the IP address of the DNS server most appropriate for your setup.
     209      There will often be more than one entry (requirements demand secondary
     210      servers for fallback capability). If you only need or want one DNS server,
     211      remove the second <emphasis>nameserver</emphasis> line from the file.
     212      The IP address may also be a router on the local network. Another option
     213      is to use the Google Public DNS service using the IP addresses below as
     214      nameservers.</para>
    214215
    215216      <note><para>The Google Public IPv4 DNS addresses are
    … …  
    263264
    264265     <para>Decide on a fully-qualified domain name (FQDN), and possible aliases
    265      for use in the <filename>/etc/hosts</filename> file. If using static
     266     for use in the <filename>/etc/hosts</filename> file. If using static IP
    266267     addresses, you'll also need to decide on an IP address. The syntax
    267268     for a hosts file entry is:</para>
    … …  
    286287
    287288     <para>Even if not using a network card, a valid FQDN is still required.
    288      This is necessary for certain programs to operate correctly.</para>
    289 
    290      <para>If using DHCP, DHCPv6, IPv6 Autoconfiguration, or if a network card
    291      is not going to be configured, create the <filename>/etc/hosts</filename>
    292      file by running the following command:</para>
     289     This is necessary for certain programs, such as MTAs, to operate properly.</para>
     290
     291     <para>Create the /etc/hosts file using the following command:</para>
    293292
    294293<screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
    … …  
    308307     specifically for the FQDN.</para>
    309308
     309<!--
    310310     <para>If using a static address, create the <filename>/etc/hosts</filename>
    311311     file by running this command instead:</para>
    … …  
    314314<literal># Begin /etc/hosts
    315315
    316 127.0.0.1 localhost
     316127.0.0.1 localhost.localdomain localhost
    317317127.0.1.1 <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable>
    318318<replaceable>&lt;192.168.0.2&gt;</replaceable> <replaceable>&lt;FQDN&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> <replaceable>[alias1] [alias2] ...</replaceable>
    … …  
    330330     network/system administrator and the machine will be connected to an
    331331     existing network). The optional alias name(s) can be omitted.</para>
    332    
     332-->
    333333   </sect2>
    334334

  • chapter09/systemd-custom.xml

    ra3d0817 r9e7475a  
    5050
    5151    <para>By default, <filename class="directory">/tmp</filename> is created as
    52     a tmpfs. If this is not desired, it can be overridden by the following:</para>
     52    a tmpfs. If this is not desired, it can be overridden by executing the
     53    following command:</para>
    5354
    5455<screen role="nodump"><userinput>ln -sfv /dev/null /etc/systemd/system/tmp.mount</userinput></screen>
    … …  
    5657    <para>Alternatively, if a a separate partition for
    5758    <filename class="directory">/tmp</filename> is desired, specify that
    58     partition in an <filename>/etc/fstab</filename> entry.</para>
     59    partition in a <filename>/etc/fstab</filename> entry.</para>
    5960
    6061    <warning>
    … …  
    8889    files with the same name in
    8990    <filename class="directory">/usr/lib/tmpfiles.d</filename>. See
    90     <filename>tmpfiles.d(5)</filename> manual page  for file format
     91    <filename>tmpfiles.d(5)</filename> manual page for file format
    9192    details.</para>
    9293
    … …  
    104105      which in turn references type d (directory). This then creates the
    105106      specified directory if is is not present and adjusts the permissions
    106       and ownership as specified.  Contents of the directory will be
     107      and ownership as specified. Contents of the directory will be
    107108      subject to time based cleanup if the age argument is specified.
    108109     </para>
    … …  
    122123    <title>Overriding Default Services Behavior</title>
    123124
    124     <para>The parameter of a unit can be overriden by creating a directory
     125    <para>The parameters of a unit can be overriden by creating a directory
    125126    and a configuration file in <filename
    126127    class="directory">/etc/systemd/system</filename>. For example:</para>
    … …  
    181182    <para>Logging on a system booted with systemd is handled with
    182183    systemd-journald (by default), rather than a typical unix syslog daemon.
    183     You can also add a normal syslog daemon and have both work side by
     184    You can also add a normal syslog daemon and have both operate side by
    184185    side if desired. The systemd-journald program stores journal entries in a
    185186    binary format rather than a plain text log file. To assist with
    … …  
    203204       </listitem>
    204205       <listitem>
    205          <para><command>journalctl -f</command>: povides functionality similar
     206         <para><command>journalctl -f</command>: provides functionality similar
    206207         to tail -f (follow).</para>
    207208       </listitem>
    … …  
    216217    when a daemon process crashes. On systemd booted systems the core
    217218    dumping is handled by <command>systemd-coredump</command>.  It will
    218     log the core dump into the journal and store the core dump itself in
     219    log the core dump in the journal and store the core dump itself in
    219220    <filename class="directory">/var/lib/systemd/coredump</filename>.
    220     To retrieve and process core dumps, <command>coredumpctl</command>
     221    To retrieve and process core dumps, the <command>coredumpctl</command>
    221222    tool is provided.  Here are some examples of frequently used commands:
    222223    </para>
    … …  
    225226      <listitem>
    226227        <para><command>coredumpctl -r</command>: lists all core dumps in
    227         reversed chronological order.</para>
    228       </listitem>
    229       <listitem>
    230         <para><command>coredumpctl -1 info</command>: show the information
    231         of the last core dump.</para>
    232       </listitem>
    233       <listitem>
    234         <para><command>coredumpctl -1 debug</command>: load the last core
     228        reverse chronological order.</para>
     229      </listitem>
     230      <listitem>
     231        <para><command>coredumpctl -1 info</command>: shows the information
     232        from the last core dump.</para>
     233      </listitem>
     234      <listitem>
     235        <para><command>coredumpctl -1 debug</command>: loads the last core
    235236        dump into <ulink url="&blfs-book;general/gdb.html">GDB</ulink>.
    236237        </para>
    … …  
    250251EOF</userinput></screen>
    251252
    252     <para>See <filename>systemd-coredump(8)</filename>,
     253    <para>See the <filename>systemd-coredump(8)</filename>,
    253254    <filename>coredumpctl(1)</filename>, and
    254255    <filename>coredump.conf.d(5)</filename> manual pages for more
    … …  
    285286          after the user session has ended, but breaks backwards compatibility
    286287          with tools like <command>nohup</command> and utilities that use
    287           <function>deamon()</function>.
     288          <function>daemon()</function>.
    288289        </para>
    289290      </listitem>
    … …  
    299300      <listitem>
    300301        <para>
    301           <emphasis>Disable at build-time</emphasis>: You can enable
     302          <emphasis>Disable at build-time</emphasis>: You can disable
    302303          lingering by default while building systemd by adding the switch
    303304          <parameter>-Ddefault-kill-user-processes=false</parameter> to the

  • chapter09/udev.xml

    ra3d0817 r9e7475a  
    224224      <para>Note that the <quote>softdep</quote> command also allows
    225225      <literal>pre:</literal> dependencies, or a mixture of both
    226       <literal>pre:</literal> and <literal>post:</literal>.  See the
    227       <filename>modprobe.d(5)</filename> manual page for more information
     226      <literal>pre:</literal> and <literal>post:</literal> dependencies.  See
     227      the <filename>modprobe.d(5)</filename> manual page for more information
    228228      on <quote>softdep</quote> syntax and capabilities.</para>
    229229
    230       <para>If the module in question is not a wrapper and is useful by itself,
    231       configure the <command>modules</command> bootscript to load this
    232       module on system boot. To do this, add the module name to the
     230      <para revision="sysv">If the module in question is not a wrapper and is
     231      useful by itself, configure the <command>modules</command> bootscript to
     232      load this module on system boot. To do this, add the module name to the
    233233      <filename>/etc/sysconfig/modules</filename> file on a separate line.
    234234      This works for wrapper modules too, but is suboptimal in that case.</para>
Note: See TracChangeset for help on using the changeset viewer.