aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06
diff options
context:
space:
mode:
authorBruce Dubbs <bdubbs@linuxfromscratch.org>2015-09-26 20:28:40 +0000
committerBruce Dubbs <bdubbs@linuxfromscratch.org>2015-09-26 20:28:40 +0000
commitea23e54ba5150e805b6c0e52b89589f1d413cb4d (patch)
treef44aa54db35c7c432b52a0abb6d8c79752ae82b1 /chapter06
parent3d56263030297ac2a86d273f7eff390ac309b34a (diff)
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
Diffstat (limited to 'chapter06')
-rw-r--r--chapter06/pkgmgt.xml8
1 files changed, 7 insertions, 1 deletions
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>