diff options
| -rw-r--r-- | chapter01/changelog.xml | 5 | ||||
| -rw-r--r-- | chapter06/pkgmgt.xml | 39 |
2 files changed, 44 insertions, 0 deletions
diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index 841f7b084..c37bfc57a 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -41,6 +41,11 @@ <para>2009-05-23</para> <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 <ulink url="&lfs-ticket-root;2404">#2404</ulink>.</para> diff --git a/chapter06/pkgmgt.xml b/chapter06/pkgmgt.xml index 3b8d1aa95..64385c8e9 100644 --- a/chapter06/pkgmgt.xml +++ b/chapter06/pkgmgt.xml @@ -224,6 +224,14 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen> package management for LFS systems is located at <ulink 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> <sect3> @@ -241,4 +249,35 @@ make DESTDIR=/usr/pkg/libfoo/1.1 install</userinput></screen> </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> |