diff options
| author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-08-29 20:08:18 +0000 |
|---|---|---|
| committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2001-08-29 20:08:18 +0000 |
| commit | 70364ce147a973ed066fb15f926119bd38e1e2f4 (patch) | |
| tree | 3a52fee49095f9fd23d26525a9f8cbbf4904f298 /chapter09 | |
| parent | 2bdc67d17847ca6c6eddee2c1af0f3c80a2aad64 (diff) | |
text updates
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1116 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter09')
| -rw-r--r-- | chapter09/reboot.xml | 4 | ||||
| -rw-r--r-- | chapter09/theend.xml | 17 |
2 files changed, 10 insertions, 11 deletions
diff --git a/chapter09/reboot.xml b/chapter09/reboot.xml index 39669eeb3..0fab58ee5 100644 --- a/chapter09/reboot.xml +++ b/chapter09/reboot.xml @@ -2,8 +2,8 @@ <title>Rebooting the system</title> <para>Now that all software has been installed, bootscripts have been created, -it's time to reboot the computer. Before we reboot let's exit the -chroot'ed environment first and unmount the LFS partition by running:</para> +it's time to reboot the computer. Before we reboot let's unmount +$LFS/proc and the LFS partition itself by running:</para> <para><screen><userinput>umount $LFS/proc &&</userinput> <userinput>umount $LFS</userinput></screen></para> diff --git a/chapter09/theend.xml b/chapter09/theend.xml index 7733c795d..d8bcbc4d1 100644 --- a/chapter09/theend.xml +++ b/chapter09/theend.xml @@ -10,18 +10,18 @@ the binaries on your LFS system. If you are not a programmer and don't plan on debugging your software, then you will be happy to know that you can reclaim a few tens of megs by removing debug symbols. This process causes no inconvenience other than not being able to debug the software fully -anymore, which is not an issue if you don't know how to debug. You can -remove the symbols by executing the following command:</para> +anymore, which is not an issue if you don't know how to debug.</para> <para>Disclaimer: 98% of the people who use the command mentioned below don't experience any problems. But do make a backup of your LFS system before you run this command. There's a slight chance it may backfire on you and render your system unusable (mostly by destroying your kernel modules -and dynamic & shared libraries).</para> +and dynamic & shared libraries). This is more often caused by typo's +than by a problem with the command used.</para> -<para>Having that said, the --strip-debug option to strip is quite harmless -under normal circumstances. It doesn't strip anything vital from the -files. It also is quite safe to use --strip-all on regular programs +<para>Having said that, the --strip-debug option we use to strip is quite +harmless under normal circumstances. It doesn't strip anything vital from +the files. It also is quite safe to use --strip-all on regular programs (don't use that on libraries - they will be destroyed) but it's not as safe and the space you gain is not all that much. But if you're tight on disk space every little bit helps, so decide yourself. Please refer to @@ -32,9 +32,8 @@ on the safe side.</para> <para><screen><userinput>find $LFS/{,usr,usr/local}/{bin,sbin,lib} -type f \</userinput> <userinput> -exec /usr/bin/strip --strip-debug '{}' ';'</userinput></screen></para> -<para>If you plan to ever upgrade to a newer LFS version in the future it -will be a good idea to create the $LFS/etc/lfs-&version; file. By having -this file it is very easy for you (and for us if you are going to ask +<para>It may be a good idea to create the $LFS/etc/lfs-&version; file. By +having this file it is very easy for you (and for us if you are going to ask for help with something at some point) to find out which LFS version you have installed on your system. This can just be a null-byte file by running:</para> |