Changeset ea23e54

Timestamp:

09/26/2015 08:28:40 PM (8 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 7.10, 7.10-rc1, 7.8, 7.9, 7.9-rc1, 7.9-rc2, 8.0, 8.0-rc1, 8.1, 8.1-rc1, 8.1-rc2, 8.2, 8.2-rc1, 8.3, 8.3-rc1, 8.3-rc2, 8.4, 8.4-rc1, 9.0, 9.0-rc1, 9.1, 9.1-rc1, BOOK.old, arm, bdubbs/gcc13, cross-chap5, ml-11.0, multilib, nosym, old-trunk, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/git-transition, xry111/glibc-2.34, xry111/glibc-2.37, xry111/kcfg-revise, xry111/lfs-next, xry111/pip3, xry111/queue-11.3, xry111/rust-wip-20221008, xry111/tester-nohack, xry111/usr-move

Children:

63d555b5

Parents:

3d56263

Message:

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

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter06/pkgmgt.xml (modified) (2 diffs)
• general.ent (modified) (1 diff)

chapter01/changelog.xml

@@ -38 +38 @@
 
     <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>

chapter06/pkgmgt.xml

@@ -251 +251 @@
     <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
@@ -272 +272 @@
     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>

general.ent

@@ -1 @@
-<!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">