Changeset 33f0959

Timestamp:

05/23/2009 11:32:30 AM (15 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, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

63f6e21

Parents:

f32421a

Message:

Expand package management discussion and add a section
on deploying an LFS system to another host.

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

Files:

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

chapter01/changelog.xml

@@ -42 +42 @@
       <itemizedlist>
         <listitem>
+          <para>[bdubbs] - Expand package management discussion and
+          add a section on deploying an LFS system to another host. Fixes
+          <ulink url="&lfs-ticket-root;2073">#2073</ulink>.</para>
+        </listitem>
+        <listitem>
           <para>[matthew] - Shorten the command used to adjust the linker in
           Chapter 6.  Thanks to Chris Staub for the improvement.  Fixes

chapter06/pkgmgt.xml

@@ -225 +225 @@
       url="&hints-root;fakeroot.txt"/>.</para>
 
+      <para>Creation of package files that include dependency information is
+      complex and is beyond the scope of LFS.</para>
+
+      <para>Slackware uses a <command>tar</command> based system for package 
+      archives.  This system purposely does not handle package dependencies
+      as more complex package managers do.  For details of Slackware package
+      management, see <ulink
+      url="http://www.slackbook.org/html/package-management.html"/>.</para>
     </sect3>
 
@@ -242 +250 @@
   </sect2>
 
+  <sect2>
+    <title>Deploying LFS on Multiple Systems</title>
+
+    <para>One of the advantages of a 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
+    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
+    it.  From that point, a few configuration files will have to be changed.
+    Configuration files that may need to be updated include: 
+    <filename>/etc/hosts</filename>,
+    <filename>/etc/fstab</filename>,
+    <filename>/etc/passwd</filename>,
+    <filename>/etc/group</filename>,
+    <filename>/etc/shadow</filename>,
+    <filename>/etc/ld.so.conf</filename>,
+    <filename>/etc/scsi_id.config</filename>,
+    <filename>/etc/sysconfig/network</filename> and
+    <filename>/etc/sysconfig/network-devices/ifconfig.eth0/ipv4</filename>.    
+    </para>
+
+    <para>A custom kernel may need to be built for the new system depending on
+    differences in system hardware and the original kernel
+    configuration.</para>
+
+    <para>Finally the new system has to be made bootable via <xref
+    linkend="ch-bootable-grub"/>.</para>
+
+  </sect2>
+
 </sect1>