| 1 | <sect1 id="ch09-theend">
|
|---|
| 2 | <title>The End</title>
|
|---|
| 3 | <?dbhtml filename="theend.html" dir="chapter09"?>
|
|---|
| 4 |
|
|---|
| 5 | <para>Well done! You have finished installing your LFS system. It may have
|
|---|
| 6 | been a long process, but we hope it was worth it. We wish you a lot of fun
|
|---|
| 7 | with your new shiny custom built Linux system.</para>
|
|---|
| 8 |
|
|---|
| 9 | <para>Now would be a good time to strip all debug symbols from
|
|---|
| 10 | the binaries on your LFS system. If you are not a programmer and don't plan
|
|---|
| 11 | on debugging your software, then you will be happy to know that you can
|
|---|
| 12 | reclaim a few tens of megs by removing debug symbols. This process causes
|
|---|
| 13 | no inconvenience other than not being able to debug the software fully
|
|---|
| 14 | anymore, which is not an issue if you don't know how to debug.</para>
|
|---|
| 15 |
|
|---|
| 16 | <para>Disclaimer: 98% of the people who use the command mentioned below don't
|
|---|
| 17 | experience any problems. But do make a backup of your LFS system before
|
|---|
| 18 | you run this command. There's a slight chance it may backfire on you and
|
|---|
| 19 | render your system unusable (mostly by destroying your kernel modules
|
|---|
| 20 | and dynamic & shared libraries). This is caused more often by typos
|
|---|
| 21 | than by a problem with the command used.</para>
|
|---|
| 22 |
|
|---|
| 23 | <para>Having said that, the --strip-debug option we use to strip is quite
|
|---|
| 24 | harmless under normal circumstances. It doesn't strip anything vital from
|
|---|
| 25 | the files. It also is quite safe to use --strip-all on regular programs
|
|---|
| 26 | (don't use that on libraries - they will be destroyed), but it's not as
|
|---|
| 27 | safe, and the space you gain is not all that much. But if you're tight on
|
|---|
| 28 | disk space every little bit helps, so decide for yourself. Please refer to
|
|---|
| 29 | the strip man page for other strip options you can use. The general idea
|
|---|
| 30 | is to not run strip on libraries (other than --strip-debug), just to be
|
|---|
| 31 | on the safe side.</para>
|
|---|
| 32 |
|
|---|
| 33 | <para>If you are planning to go ahead and perform the strip, special care is
|
|---|
| 34 | needed to ensure you're not running any binaries that are about to be stripped
|
|---|
| 35 | -- including the active bash shell. Therefore you'll need to exit the chroot
|
|---|
| 36 | environemnt and reenter it using a modified chroot command:</para>
|
|---|
| 37 |
|
|---|
| 38 | <screen><userinput>logout
|
|---|
| 39 | chroot $LFS /tools/bin/env -i \
|
|---|
| 40 | HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
|
|---|
| 41 | PATH=/bin:/usr/bin:/sbin:/usr/sbin \
|
|---|
| 42 | /tools/bin/bash --login</userinput></screen>
|
|---|
| 43 |
|
|---|
| 44 | <para>Now run the following command:</para>
|
|---|
| 45 |
|
|---|
| 46 | <screen><userinput>/tools/bin/find /{,usr/,usr/local/}{bin,sbin,lib} -type f \
|
|---|
| 47 | -exec /tools/bin/strip --strip-debug '{}' ';'</userinput></screen>
|
|---|
| 48 |
|
|---|
| 49 | <para>Quite a number of files will be reported as having their file format not
|
|---|
| 50 | recognized. Most of these are scripts instead of binaries. These warnings can
|
|---|
| 51 | be safely ignored.</para>
|
|---|
| 52 |
|
|---|
| 53 | <para>It's a good idea to create an /etc/lfs file. By
|
|---|
| 54 | having this file it is very easy for you (and for us if you are going to ask
|
|---|
| 55 | for help with something at some point) to find out which LFS version
|
|---|
| 56 | you have installed on your system. Create the /etc/lfs file by
|
|---|
| 57 | running the following command:</para>
|
|---|
| 58 |
|
|---|
| 59 | <screen><userinput>echo &version; > /etc/lfs</userinput></screen>
|
|---|
| 60 |
|
|---|
| 61 | </sect1>
|
|---|
| 62 |
|
|---|
