Changeset 4cdfb1b


Ignore:
Timestamp:
12/11/2003 05:13:51 PM (20 years ago)
Author:
Igor Živković <igor@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
545734c
Parents:
8a84d1c
Message:

corrected few typos and formatting in DHCP section

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1623 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • connect/dhcp/bootscripts.xml

    r8a84d1c r4cdfb1b  
    8787chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</command></userinput></screen>
    8888
    89 <warning><para>
    90 This script, in it's current state, <emphasis>will</emphasis> cause an
    91 error at shutdown.  ATM, It is best to just live with the error.  The
    92 network scripts for LFS and BLFS are currently being revised.  In the
    93 interim, you can use a simple workaround to rid yourself of the error.
    94 Move K80network in your stop scripts to K49network.  You must be
    95 absolutely certain, however, that you have all network filesystems
    96 unmounted before this script is executed.
    97 </para></warning>
     89<warning><para>This script, in its current state,
     90<emphasis>will</emphasis> cause an error at shutdown. At the moment, it
     91is best to just live with the error. The network scripts for
     92<acronym>LFS</acronym> and <acronym>BLFS</acronym> are currently being
     93revised. In the interim, you can use a simple workaround to rid yourself
     94of the error. Move your <filename>K80network</filename> stop scripts to
     95<filename>K49network</filename>. You must be absolutely certain,
     96however, that you have all network filesystems unmounted before this
     97script is executed.</para></warning>
    9898
    9999</sect2>
Note: See TracChangeset for help on using the changeset viewer.