source: chapter08/revisedchroot.xml@ 37e35d2

multilib-10.1
Last change on this file since 37e35d2 was 37e35d2, checked in by Thomas Trepl <thomas@…>, 4 years ago

Update to new lfs structure

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/multilib@11986 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 3.2 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-system-revisedchroot">
9 <?dbhtml filename="revisedchroot.html"?>
10
11 <title>Cleaning Up</title>
12
13 <para>Finally, clean up some extra files left around from running tests:</para>
14
15<screen><userinput>rm -rf /tmp/*</userinput></screen>
16
17 <para>Now log out and reenter the chroot environment with an updated
18 chroot command. From now on, use this updated chroot command any time
19 you need to reenter the chroot environment after exiting:</para>
20
21<screen role="nodump"><userinput>logout
22
23chroot "$LFS" /usr/bin/env -i \
24 HOME=/root TERM="$TERM" \
25 PS1='(lfs chroot) \u:\w\$ ' \
26 PATH=/bin:/usr/bin:/sbin:/usr/sbin \
27 /bin/bash --login</userinput></screen>
28
29 <para>Here the <parameter>+h</parameter> option is not used anymore, since
30 all the previous programs have been replaced: hashing is therefore
31 possible.</para>
32
33 <para>If the virtual kernel file systems have been unmounted, either manually
34 or through a reboot, ensure that the virtual kernel file systems are mounted
35 when reentering the chroot. This process was explained in <xref
36 linkend="ch-tools-bindmount"/> and <xref
37 linkend="ch-tools-kernfsmount"/>.</para>
38
39 <para>There were several static libraries that were not suppressed earlier
40 in the chapter in order to satisfy the regression tests in several packages. These
41 libraries are from binutils, bzip2, e2fsprogs, flex, libtool, and zlib. If desired,
42 remove them now:</para>
43
44<screen><userinput>rm -f /usr/lib/lib{bfd,opcodes}.a
45rm -f /usr/lib/libctf{,-nobfd}.a
46rm -f /usr/lib/libbz2.a
47rm -f /usr/lib/lib{com_err,e2p,ext2fs,ss}.a
48rm -f /usr/lib/libltdl.a
49rm -f /usr/lib/libfl.a
50rm -f /usr/lib/libz.a</userinput><userinput arch="ml_32,ml_all">
51rm -f &usr-lib-m32;/libbz2.a
52rm -f &usr-lib-m32;/libltdl.a
53rm -f &usr-lib-m32;/libz.a</userinput><userinput arch="ml_x32,ml_all">
54rm -f &usr-lib-mx32;/libbz2.a
55rm -f &usr-lib-mx32;/libltdl.a
56rm -f &usr-lib-mx32;/libz.a</userinput></screen>
57
58 <para>There are also several files installed in the /usr/lib and /usr/libexec
59 directories with a file name extention of .la. These are "libtool archive"
60 files. As already said, they are only useful when linking with static
61 libraries. They are unneeded, and potentially harmful, when using dynamic
62 shared libraries, specially when using also non-autotools build systems.
63 To remove them, run:</para>
64
65<screen><userinput>find /usr/lib /usr/libexec -name \*.la -delete</userinput><userinput arch="ml_32,ml_all">
66find &usr-lib-m32; -name \*.la -delete</userinput><userinput arch="ml_x32,ml_all">
67find &usr-lib-mx32; -name \*.la -delete</userinput></screen>
68
69 <para>For more information about libtool archive files, see the <ulink
70 url="&blfs-book;/introduction/la-files.html">BLFS section "About Libtool
71 Archive (.la) files"</ulink>.</para>
72
73 <para>Finally, remove the temporary 'tester' user account created at the
74 beginning of the previous chapter.</para>
75
76<screen><userinput>userdel -r tester</userinput></screen>
77</sect1>
Note: See TracBrowser for help on using the repository browser.