- 12/11/2003 05:13:51 PM (18 years ago)
- 10.0, 10.1, 11.0, 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, ken/refactor-virt, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, v5_1, v5_1-pre1, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
- 1 edited
r8a84d1c r4cdfb1b 87 87 chmod 755 /etc/sysconfig/network-devices/ifdown-eth0</command></userinput></screen> 88 88 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> 90 <emphasis>will</emphasis> cause an error at shutdown. At the moment, it 91 is best to just live with the error. The network scripts for 92 <acronym>LFS</acronym> and <acronym>BLFS</acronym> are currently being 93 revised. In the interim, you can use a simple workaround to rid yourself 94 of the error. Move your <filename>K80network</filename> stop scripts to 95 <filename>K49network</filename>. You must be absolutely certain, 96 however, that you have all network filesystems unmounted before this 97 </para></warning> 98 98 99 99 </sect2>
Note: See TracChangeset for help on using the changeset viewer.