diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index b6e636cc0..d7d27981f 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -37,6 +37,16 @@
-->
+
+ 2012-08-12
+
+
+ [bdubbs] - Update to udev (systemd)-188. Fixes
+ #3152.
+
+
+
+
2012-08-06
diff --git a/chapter06/systemd.xml b/chapter06/systemd.xml
index b31b0de6b..843f702df 100644
--- a/chapter06/systemd.xml
+++ b/chapter06/systemd.xml
@@ -54,6 +54,15 @@
Install the package:
make -f udev-lfs-&systemd-version;/Makefile.lfs install
+
+ Finally set up the persistent network udev rules. This task will be
+ explained in detail in . Note that the
+ /sys and /proc filesystems must be mounted in the
+ chroot environment as explained at the beginning of this chapter for the
+ following script to work.
+
+bash udev-lfs-&systemd-version;/init-net-rules.sh
diff --git a/chapter07/network.xml b/chapter07/network.xml
index 3f476d550..f5dd1faa8 100644
--- a/chapter07/network.xml
+++ b/chapter07/network.xml
@@ -23,7 +23,7 @@
symlinks from all run-level directories (/etc/rc.d/rc*.d).
-
+
Creating stable names for network interfaces
If there is only one network interface in the system to be
@@ -41,18 +41,19 @@
avoid this, Udev comes with a script and some rules to assign stable names
to network cards based on their MAC address.
- Pre-generate the rules to ensure the same names get assigned to the
- same devices at every boot, including the first:
-
-for NIC in /sys/class/net/* ; do
- INTERFACE=${NIC##*/} udevadm test --action=add $NIC
-done
-
- Now, inspect the /etc/udev/rules.d/70-persistent-net.rules
- file, to find out which name was assigned to which network device:
+ The rules were pre-generated in the build instructions for
+ udev (systemd) in the last chapter. Inspect the
+ /etc/udev/rules.d/70-persistent-net.rules file, to
+ find out which name was assigned to which network device:
cat /etc/udev/rules.d/70-persistent-net.rules
+ In some cases such as when MAC addresess have been assigned to
+ a network card manually or in a virtual envirnment such as Xen,
+ the network rules file may not have been generated because addresses
+ are not consistently assigned. In these cases, just continue to
+ the next section.
+
The file begins with a comment block followed by two lines for each
NIC. The first line for each NIC is a commented description showing its
hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
diff --git a/packages.ent b/packages.ent
index 617e33401..0aac3e2b1 100644
--- a/packages.ent
+++ b/packages.ent
@@ -524,10 +524,10 @@
-
-
+
+
-
+
@@ -540,10 +540,10 @@
-
-
+
+
-
+