From ea23e54ba5150e805b6c0e52b89589f1d413cb4d Mon Sep 17 00:00:00 2001
From: Bruce Dubbs <bdubbs@linuxfromscratch.org>
Date: Sat, 26 Sep 2015 20:28:40 +0000
Subject: [PATCH] Add additional discussion about copying an LFS system from
 one machine to another.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@10954 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter01/changelog.xml | 10 ++++++++++
 chapter06/pkgmgt.xml    |  8 +++++++-
 general.ent             |  4 ++--
 3 files changed, 19 insertions(+), 3 deletions(-)

diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index 4232897f7..29d1426b0 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -36,6 +36,16 @@
     </listitem>
 -->
 
+    <listitem>
+      <para>2015-09-26</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Add additional discussion about copying an LFS 
+          system from one machine to another.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2015-09-17</para>
       <itemizedlist>
diff --git a/chapter06/pkgmgt.xml b/chapter06/pkgmgt.xml
index b4734aba0..a451f2162 100644
--- a/chapter06/pkgmgt.xml
+++ b/chapter06/pkgmgt.xml
@@ -250,7 +250,7 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
 
     <para>One of the advantages of an LFS system is that there are no files that
     depend on the position of files on a disk system.  Cloning an LFS build to
-    another computer with an architecture similar to the base system is as
+    another computer with the same architecture as the base system is as
     simple as using <command>tar</command> on the LFS partition that contains
     the root directory (about 250MB uncompressed for a base LFS build), copying
     that file via network transfer or CD-ROM to the new system and expanding
@@ -271,6 +271,12 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen>
     differences in system hardware and the original kernel
     configuration.</para>
 
+    <note><para>There have been some reports of issues when copying between 
+    similar but not identical architectures.  For instance the instruction set
+    for Intel architectures is not identical with AMD processors and later
+    versions of some processors may have instructions not available in
+    earlier versions.</para></note>
+
     <para>Finally the new system has to be made bootable via <xref
     linkend="ch-bootable-grub"/>.</para>
 
diff --git a/general.ent b/general.ent
index 9b6e5a39d..f8053faea 100644
--- a/general.ent
+++ b/general.ent
@@ -1,7 +1,7 @@
-<!ENTITY version         "SVN-20150917">
+<!ENTITY version         "SVN-20150926">
 <!ENTITY short-version   "svn">  <!-- Used below in &blfs-book;. Change to x.y for release 
                                       but not -rc releases -->
-<!ENTITY releasedate     "September 17, 2015">
+<!ENTITY releasedate     "September 26, 2015">
 <!ENTITY copyrightdate   "1999-2015"><!-- jhalfs needs a literal dash, not &ndash; -->
 <!ENTITY milestone       "7.8">
 <!ENTITY generic-version "development"> <!-- Use "development", "testing", or "x.y[-pre{x}]" -->