diff options
author | Mark Hymers <markh@linuxfromscratch.org> | 2001-07-22 19:45:10 +0000 |
---|---|---|
committer | Mark Hymers <markh@linuxfromscratch.org> | 2001-07-22 19:45:10 +0000 |
commit | b822811980a5f82726cb641cbeff66be9eb6d92a (patch) | |
tree | 27c4db3c62aaea065b053e43c39b2ba44c04a05f /chapter06/introduction.xml | |
parent | 46f5461af92bc70c62bbb92895032b930954d835 (diff) |
XML changes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@827 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06/introduction.xml')
-rw-r--r-- | chapter06/introduction.xml | 15 |
1 files changed, 5 insertions, 10 deletions
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml index 3c3c68ee6..f915875aa 100644 --- a/chapter06/introduction.xml +++ b/chapter06/introduction.xml @@ -1,26 +1,21 @@ <sect1 id="ch06-introduction"> <title>Introduction</title> -<para> -The installation of all the software is pretty straightforward and +<para>The installation of all the software is pretty straightforward and you will probably think it's so much easier and shorter to give the generic installation instructions for each package and only explain how to install something if a certain package requires an alternate installation method. Although I agree on that, I choose to give the full instructions for each and every package. This is simply to avoid any -possible confusion and errors. -</para> +possible confusion and errors.</para> -<para> -Now would be a good time to take a look at the optimization hint at <ulink -url="http://archive.linuxfromscratch.org/lfs-hints/optimization.txt"> -http://archive.linuxfromscratch.org/lfs-hints/optimization.txt</ulink> +<para>Now would be a good time to take a look at the optimization hint at <ulink +url="http://archive.linuxfromscratch.org/lfs-hints/optimization.txt">http://archive.linuxfromscratch.org/lfs-hints/optimization.txt</ulink> if you plan on using compiler optimization for the packages installed in the following chapter. Compiler optimization can make a program run faster, but may also cause some compilation problems. If you run into problems after having used optimization, always try it without optimizing to see if you -can reproduce the problem. -</para> +can reproduce the problem.</para> </sect1> |