Changeset 94cea1d


Ignore:
Timestamp:
06/24/2017 07:33:48 PM (7 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, 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:
d414cb0
Parents:
b2a5112
Message:

Remove section disussing configuration without a network card.
Update boot scripts to unmount network file systems before bringing down the network.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11260 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
7 edited

Legend:

Unmodified
Added
Removed

  • bootscripts/ChangeLog

    rb2a5112 r94cea1d  
     12015-06-24 Bruce Dubbs <bdubbs@linuxfromscratch.org>
     2   * Unmount network file systems before bringing down the network
     3   * Spell out some mount/umount options
     4
    152017-03-25 DJ Lucas <dj@linuxfromscratch.org>
    26   * Bash-4.4 changes no longer allow continue in function to pass to calling

  • bootscripts/lfs/init.d/mountfs

    rb2a5112 r94cea1d  
    3434   start)
    3535      log_info_msg "Remounting root file system in read-write mode..."
    36       mount -o remount,rw / >/dev/null
     36      mount --options remount,rw / >/dev/null
    3737      evaluate_retval
    3838
    … …  
    4747
    4848      log_info_msg "Mounting remaining file systems..."
    49       mount -a -O no_netdev >/dev/null
     49      mount --all --test-opts no_netdev >/dev/null
    5050      evaluate_retval
    5151      exit $failed
    … …  
    5555      # Don't unmount virtual file systems like /run
    5656      log_info_msg "Unmounting all other currently mounted file systems..."
    57       umount -a -d -r -t notmpfs,nosysfs,nodevtmpfs,noproc,nodevpts >/dev/null
     57      umount --all --detach-loop --read-only \
     58             --types notmpfs,nosysfs,nodevtmpfs,noproc,nodevpts >/dev/null
    5859      evaluate_retval
    5960
    6061      # Make sure / is mounted read only (umount bug)
    61       mount -o remount,ro /
     62      mount --test-opts remount,ro /
    6263
    6364      # Make all LVM volume groups unavailable, if appropriate

  • bootscripts/lfs/init.d/network

    rb2a5112 r94cea1d  
    4646
    4747   stop)
     48      # Unmount any network mounted file systems
     49       umount --all --force --types nfs,cifs,nfs4
     50
    4851      # Reverse list
    4952      net_files=""

  • chapter01/changelog.xml

    rb2a5112 r94cea1d  
    4343    appropriate for the entry or if needed the entire day's listitem.
    4444-->
     45    <listitem revision='sysv'>
     46      <para>2017-06-24</para>
     47      <itemizedlist>
     48        <listitem>
     49          <para>[bdubbs] - Remove section disussing configuration
     50          without a network card.</para>
     51        </listitem>
     52        <listitem>
     53          <para>[bdubbs] - Update boot scripts to unmount network
     54          file systems before bringing down the network.</para>
     55        </listitem>
     56      </itemizedlist>
     57    </listitem>
     58
    4559    <listitem>
    4660      <para>2017-06-21</para>

  • chapter07/network.xml

    rb2a5112 r94cea1d  
    1414    <primary sortas="d-network">network</primary>
    1515  <secondary>configuring</secondary></indexterm>
    16 
     16<!--
    1717  <para>This section only applies if a network card is to be
    1818  configured.</para>
    … …  
    2424  class="directory">/etc/rc.d/rc*.d</filename>) after the bootscripts are
    2525  installed in <xref linkend="ch-scripts-bootscripts"/>.</para>
    26 
     26-->
    2727  <sect2>
    2828    <title>Creating Network Interface Configuration Files</title>
    … …  
    3232    class="directory">/etc/sysconfig/</filename>.  This directory should
    3333    contain a file for each interface to be configured, such as
    34     <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is required to
    35     be a Network Card Interface name (e.g. eth0).  Inside this file are
    36     attributes to this interface, such as its IP address(es), subnet masks, and
    37     so forth.  It is necessary that the stem of the filename be
    38     <emphasis>ifconfig</emphasis>.</para>
     34    <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe
     35    the network card.  The interface name (e.g. eth0) is usually appropriate.
     36    Inside this file are attributes to this interface, such as its IP
     37    address(es), subnet masks, and so forth.  It is necessary that the stem of
     38    the filename be <emphasis>ifconfig</emphasis>.</para>
    3939
    4040    <note><para>If the procedure in the previous section was not used, Udev
    4141    will assign network card interface names based on system physical
    4242    characteristics such as enp2s1. If you are not sure what your interface
    43     name is, you can always run <command>ip link</command>  after you have
    44     booted your system.  Again, it is important that ifconfig.xyz is named
    45     after correct network card interface name (e.g. ifconfig.enp2s1 or
    46     ifconfig.eth0) or your network interface will not be initialized during
    47     the boot process.</para></note>
     43    name is, you can always run <command>ip link</command> or <command>ls
     44    /sys/class/net</command> after you have booted your system. 
     45    </para></note>
    4846
    4947    <para>The following command creates a sample file for the
    … …  
    9997
    10098  </sect2>
    101 <!--
    102   <sect2 id="systemd-net-enable">
    103     <title>Configuring the Network Interface Card at boot (systemd)</title>
    104 
    105     <para>Enabling of the network interface card configuration
    106     in systemd is done per interface. To enable network interface card
    107     configuration at boot, run:</para>
    108 
    109 <screen><userinput>systemctl enable ifupdown@eth0</userinput></screen>
    110 
    111     <para>To disable a previously enabled network interface
    112     card configuration at boot, run:</para>
    113 
    114 <screen role="nodump"><userinput>systemctl disable ifupdown@eth0</userinput></screen>
    115 
    116     <para>To manually start the network interface card configuration,
    117     run:</para>
    118 
    119 <screen role="nodump"><userinput>systemctl start ifupdown@eth0</userinput></screen>
    120 
    121     <para>Replace eth0 with the correct network interface card
    122     name as described on the beginning of this page.</para>
    123 
    124     <note><para>These procedures require the configuration files as specified
    125     in the previous section.</para></note>
    126 
    127     <note><para>The network card can also be started or stopped
    128     with the traditional <command>ifup &lt;device&gt;</command> or
    129     <command>ifdown &lt;device&gt;</command> commands.</para></note>
    130 
    131   </sect2>
    132 
    133   <sect2 id="systemd2-net-enable">
    134     <title>Configuring the Network Interface Card for systemd-networkd</title>
    135 
    136     <para>An alternative way to configure a NIC when booting with with
    137     systemd is to create a configuration file recognized by the
    138     systemd-networkd daemon.  To configure the device create a file similar
    139     to this:</para>
    140 
    141 <screen role="nodump"><userinput>cat &gt; /etc/systemd/network/10-static-eth0.network &lt;&lt; "EOF"
    142 [Match]
    143 Name=eth0
    144 
    145 [Network]
    146 Address=192.168.0.2/24
    147 Gateway=192.168.0.1
    148 EOF</userinput></screen>
    149 
    150     <para>You can use multiple .network files if desired.  You can also specify
    151     DHCP=yes instead of the Address and Gateway settings.  See the man page for
    152     systemd.network for more details,</para>
    153 
    154     <note><para>If this method is used, be sure to disable ifupdown@eth0 as
    155     described in the previous section (if it was enabled).</para></note>
    156 
    157   </sect2>
    158 -->
    15999  <sect2 id="resolv.conf">
    160100    <title>Creating the /etc/resolv.conf File</title>
    … …  
    164104    </indexterm>
    165105
    166     <para>If the system is going to be connected to the Internet, it will
    167     need some means of Domain Name Service (DNS) name resolution to
    168     resolve Internet domain names to IP addresses, and vice versa. This is
    169     best achieved by placing the IP address of the DNS server, available
    170     from the ISP or network administrator, into
     106    <para>The system will need some means of obtaining Domain Name Service
     107    (DNS) name resolution to resolve Internet domain names to IP addresses, and
     108    vice versa. This is best achieved by placing the IP address of the DNS
     109    server, available from the ISP or network administrator, into
    171110    <filename>/etc/resolv.conf</filename>. Create the file by running the
    172111    following:</para>
    … …  
    193132    may also be a router on the local network.</para>
    194133
    195     <note><para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para></note>
     134    <note>
     135      <para>The Google Public IPv4 DNS addresses are 8.8.8.8 and 8.8.4.4.</para>
     136    </note>
    196137
    197138  </sect2>
    … …  
    265206
    266207<screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
    267 <literal># Begin /etc/hosts (network card version)
     208<literal># Begin /etc/hosts
    268209
    269210127.0.0.1 localhost
    … …  
    274215ff02::2   ip6-allrouters
    275216
    276 # End /etc/hosts (network card version)</literal>
     217# End /etc/hosts</literal>
    277218EOF</userinput></screen>
    278219
    … …  
    283224     network/system administrator and the machine will be connected to an
    284225     existing network). The optional alias name(s) can be omitted.</para>
    285    
     226
     227<!--  This is not very useful
     228
    286229     <para>If a network card is not going to be configured, create the
    287230     <filename>/etc/hosts</filename> file by running:</para>
    … …  
    297240
    298241# End /etc/hosts (no network card version)</literal>
    299 EOF</userinput></screen>
     242EOF</userinput></screen> -->
    300243
    301244   </sect2>

  • general.ent

    rb2a5112 r94cea1d  
    1 <!ENTITY version         "SVN-20170621">
     1<!ENTITY version         "SVN-20170624">
    22<!ENTITY short-version   "svn">  <!-- Used below in &blfs-book;
    33                                      Change to x.y for release but not -rc releases -->
    44<!ENTITY generic-version "development"> <!-- Use "development"  or "x.y[-pre{x}]" -->
    55
    6 <!ENTITY versiond        "20170602-systemd">
     6<!ENTITY versiond        "20170621-systemd">
    77<!ENTITY short-versiond  "systemd">
    88<!ENTITY generic-versiond "systemd">
    99
    10 <!ENTITY releasedate     "June 21, 2017">
     10<!ENTITY releasedate     "June 24, 2017">
    1111
    1212<!ENTITY copyrightdate   "1999-2017"><!-- jhalfs needs a literal dash, not &ndash; -->

  • packages.ent

    rb2a5112 r94cea1d  
    367367<!ENTITY less-ch6-sbu "less than 0.1 SBU">
    368368
    369 <!ENTITY lfs-bootscripts-version "20170325">              <!-- Scripts depend on this format -->
     369<!ENTITY lfs-bootscripts-version "20170624">      <!-- Scripts depend on this format -->
    370370<!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">       
    371371<!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.bz2">
Note: See TracChangeset for help on using the changeset viewer.