aboutsummaryrefslogtreecommitdiffstats
path: root/chapter06/pkgmgt.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter06/pkgmgt.xml')
-rw-r--r--chapter06/pkgmgt.xml8
1 files changed, 7 insertions, 1 deletions
diff --git a/chapter06/pkgmgt.xml b/chapter06/pkgmgt.xml
index 4810bab78..64387f5b4 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
@@ -268,6 +268,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 an Intel architecture is not identical with an AMD processor and later
+ versions of some processors may have instructions that are unavailable in
+ earlier versions.</para></note>
+
<para>Finally the new system has to be made bootable via <xref
linkend="ch-bootable-grub"/>.</para>