Update LFS target architectures.

Fix a url in pkgmgfor LFS.
Tweak a debian udev script for LFS.


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

chapter06/pkgmgt.xml

@@ -218,7 +218,7 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
       <para>This approach is used by most of the package managers found in the
       commercial distributions. Examples of package managers that follow this
       approach are RPM (which, incidentally, is required by the <ulink
-      url="http://www.linux-foundation.org/en/Specifications">Linux
+      url="http://refspecs.linuxfoundation.org/lsb.shtml">Linux
       Standard Base Specification</ulink>), pkg-utils, Debian's apt, and
       Gentoo's Portage system.  A hint describing how to adopt this style of
       package management for LFS systems is located at <ulink

prologue/architecture.xml

@@ -10,13 +10,9 @@
 
   <title>LFS Target Architectures</title>
 
-<para>The primary target architecture of LFS is the 32-bit Intel CPU. If you
-have not built an LFS system before, you should probably start with that
-target. The 32-bit architecture is the most widely supported Linux system and
-is most compatible with both open source and proprietary software.</para>
-
-<para>On the other hand, the instructions in this book are known to work, with
-some modifications, with both Power PC and 64-bit AMD/Intel CPUs. To build a
+<para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
+and x86_64 (64-bit) CPUs.  On the other hand, the instructions in this book are
+also known to work, with some modifications, with the Power PC CPU. To build a
 system that utilizes one of these CPUs, the main prerequisite, in addition to
 those on the next few pages, is an existing Linux system such as an earlier LFS
 installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution that targets
@@ -47,14 +43,15 @@ instructions needed for a straightforward base Linux system.  You can refer to
 the <ulink url="http://trac.cross-lfs.org/">Cross Linux From Scratch</ulink>
 project for this advanced topic.</para>
 
-<para>There is one last comment about 64-bit systems. There are some packages
-that cannot currently be built in a "pure" 64-bit system or require specialized
-build instructions. Generally, these packages have some embedded 32-bit
-specific assembly language instructions that fail when building on a 64-bit
-system.  This includes some Xorg drivers from <ulink
-url="http://www.linuxfromscratch.org/blfs/view/svn/">Beyond Linux From Scratch
-(BLFS)</ulink>. Many of these problems can be worked around, but may require
-some specialized procedures or patches.</para>
+<para>There is one last comment about 64-bit systems. There are some older
+packages that cannot currently be built in a "pure" 64-bit system or require
+specialized build instructions. Generally, these packages have some embedded
+32-bit specific assembly language instructions that fail when building on a
+64-bit system.  This includes some Xorg drivers for some legacy video cards at
+<ulink url="http://xorg.freedesktop.org/releases/individual/driver/">
+http://xorg.freedesktop.org/releases/individual/driver/</ulink>. Many of these
+problems can be worked around, but may require some specialized procedures or
+patches.</para>
 
 </sect1>
 

udev-lfs/contrib/debian/write_cd_aliases

@@ -1,12 +1,21 @@
 #!/bin/sh -e
 
+# Updated for LFS by B. Dubbs, 2012-09-23
+# Fix RULES_LOCK location
+
+
 RULES_FILE="/etc/udev/rules.d/82-persistent-cd.rules"
 
 ##############################################################################
 lock_rules_file() {
-  RULES_LOCK="/dev/.udev/.lock-${RULES_FILE##*/}"
+  RULES_LOCK="/run/udev/lock-${RULES_FILE##*/}"
 
-  retry=30
+  if [ ! -d /run/udev/ ]; then
+    echo "write_cd_aliases: /run/udev does not exist!" >&2
+    exit 2
+  fi
+
+  retry=10
   while ! mkdir $RULES_LOCK 2> /dev/null; do
     if [ $retry -eq 0 ]; then
        echo "Cannot lock $RULES_FILE!" >&2