gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-05 22:04:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

text updates

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1116 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-08-29 20:08:18 +00:00
parent 2bdc67d178
commit 70364ce147
2 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter09/reboot.xml
View File

@ -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 &amp;&amp;</userinput>
<userinput>umount $LFS</userinput></screen></para>

17
chapter09/theend.xml
View File

@ -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 &amp; shared libraries).</para>
and dynamic &amp; 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>&nbsp;&nbsp;&nbsp;-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>