Updated url's so in txt version when there's no hyperlink, the address

is still available


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@770 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

9 files changed, 39 insertions, 29 deletions

diff --git a/chapter01/contactinfo.xml b/chapter01/contactinfo.xml
index 6d45203ae..8dad8a3db 100644
--- a/chapter01/contactinfo.xml
+++ b/chapter01/contactinfo.xml
@@ -3,8 +3,9 @@
 
 <para>
 Direct all emails to the 
+lfs-discuss mailing list at
 <ulink url="mailto:lfs-discuss@linuxfromscratch.org">
-lfs-discuss</ulink> mailing list preferably.
+lfs-discuss@linuxfromscratch.org</ulink> preferably.
 </para>
 
 <para>
diff --git a/chapter03/creatingpart.xml b/chapter03/creatingpart.xml
index f35257e74..f12cedbd7 100644
--- a/chapter03/creatingpart.xml
+++ b/chapter03/creatingpart.xml
@@ -5,9 +5,10 @@
 First, let me tell you that it is possible to build LFS on only one partition,
 which is where your original distribution is installed. This is not recommended
 if it is the first time you try LFS, but may be useful if you are short on disk
-space. If you feel brave, take a look at the <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/one-partition-hint.txt">one
-partition hint</ulink>.
+space. If you feel brave, take a look at the one partition hint at 
+<ulink 
+url="http://archive.linuxfromscratch.org/lfs-hints/one-partition-hint.txt">
+http://archive.linuxfromscratch.org/lfs-hints/one-partition-hint.txt</ulink>.
 </para>
 
 <para>
diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml
index c01c874d2..094398e2f 100644
--- a/chapter06/aboutdebug.xml
+++ b/chapter06/aboutdebug.xml
@@ -61,8 +61,9 @@ removing those symbols a lot of disk space can be regained.
 
 <para>
 You might find additional information in the optimization hint which can 
-be found in <ulink url="http://archive.linuxfromscratch.org/lfs-hints">
-http://archive.linuxfromscratch.org/lfs-hints/</ulink>.
+be found at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/optimization.txt">
+http://archive.linuxfromscratch.org/lfs-hints/optimization.txt</ulink>.
 </para>
 
 </sect1>
diff --git a/chapter06/introduction.xml b/chapter06/introduction.xml
index b72b22964..3c3c68ee6 100644
--- a/chapter06/introduction.xml
+++ b/chapter06/introduction.xml
@@ -12,9 +12,10 @@ possible confusion and errors.
 </para>
 
 <para>
-Now would be a good time to take a look at the <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/optimization.txt">optimization
-hint</ulink> if you plan on using compiler optimization for the packages
+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
diff --git a/chapter06/lilo-inst.xml b/chapter06/lilo-inst.xml
index 449c21cee..790a3d62a 100644
--- a/chapter06/lilo-inst.xml
+++ b/chapter06/lilo-inst.xml
@@ -3,9 +3,10 @@
 
 <para>
 We have chosen Lilo because we feel confortable with it, but you may wish to
-take a look elsewhere. Someone has written a <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/grub-howto.txt">hint on
-GRUB</ulink>, an alternative boot loader.
+take a look elsewhere. Someone has written a hint on GRUB at<ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/grub-howto.txt">
+http://archive.linuxfromscratch.org/lfs-hints/grub-howto.txt</ulink>,
+ an alternative boot loader.
 </para>
 
 <para>
@@ -33,8 +34,9 @@ yet. We will complete the installation of lilo in chapter 8.
 
 <para>
 Maybe you'll be interested to know that someone wrote a hint on how to get a
-logo instead the the standard LILO prompt or menu. Take a look at it <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/bootlogo.txt">here</ulink>.
+logo instead the the standard LILO prompt or menu. Take a look at it at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/bootlogo.txt">
+http://archive.linuxfromscratch.org/lfs-hints/bootlogo.txt</ulink>.
 </para>
 
 </sect2>
diff --git a/chapter06/man-inst.xml b/chapter06/man-inst.xml
index cc1024048..d29d95edf 100644
--- a/chapter06/man-inst.xml
+++ b/chapter06/man-inst.xml
@@ -14,8 +14,9 @@ Before Man is installed, the man patch file needs to be unpacked.
 </literallayout></blockquote>
 
 <para>
-You may want to take a look at the <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/man.txt">man hint</ulink>
+You may want to take a look at the man hint at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/man.txt">
+http://archive.linuxfromscratch.org/lfs-hints/man.txt</ulink> 
 which deals with formatting and compression issues for man pages.
 </para>
 
diff --git a/chapter07/introduction.xml b/chapter07/introduction.xml
index faaea0835..74b49b8f4 100644
--- a/chapter07/introduction.xml
+++ b/chapter07/introduction.xml
@@ -12,9 +12,9 @@ intact, setting up networking and starting the daemons that the system uses.
 <para>
 We will be using SysV style init scripts. We have chosen this style because it
 is widely used and we feel confortable with it. If you want to try something
-else, someone has written an LFS-Hint on <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/bsd-init.txt">BSD style init
-scripts</ulink>.
+else, someone has written an LFS-Hint on BSD style init scripts at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/bsd-init.txt">
+http://archive.linuxfromscratch.org/lfs-hints/bsd-init.txt</ulink>.
 </para>
 
 </sect1>
diff --git a/chapter07/setclock.xml b/chapter07/setclock.xml
index d0ad1f837..05147f38d 100644
--- a/chapter07/setclock.xml
+++ b/chapter07/setclock.xml
@@ -89,9 +89,11 @@ the value <emphasis>0</emphasis> (zero).
 </para>
 
 <para>
-Now, you may want to take a look at a very good hint explaining <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/time.txt">how we deal with
-time on LFS</ulink>. It explains issues such as timezones, UTC, and the TZ
+Now, you may want to take a look at a very good hint explaining how we
+deal with time on LFS at 
+<ulink url="http://archive.linuxfromscratch.org/lfs-hints/time.txt">
+http://archive.linuxfromscratch.org/lfs-hints/time.txt</ulink>. 
+It explains issues such as timezones, UTC, and the TZ
 environment variable.
 </para>
 
diff --git a/chapter09/theend.xml b/chapter09/theend.xml
index 59c71cfc8..6cc83a077 100644
--- a/chapter09/theend.xml
+++ b/chapter09/theend.xml
@@ -74,13 +74,14 @@ active:
 
 <para>
 If you are wondering: "Well, where to go now?" you'll be glad to hear that
-someone has written an <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/afterlfs.txt">LFS-Hint
-</ulink>
-on that subject. On a same note, if you are not only newbie to LFS, but also
-newbie to Linux in general, you may find the <ulink
-url="http://archive.linuxfromscratch.org/lfs-hints/newbie.txt">newbie
-hint</ulink> very interesting.
+someone has written an LFS hint on the subject at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/afterlfs.txt">
+http://archive.linuxfromscratch.org/lfs-hints/afterlfs.txt</ulink>.
+On a same note, if you are not only newbie to LFS, but also
+newbie to Linux in general, you may find the newbie hint at <ulink
+url="http://archive.linuxfromscratch.org/lfs-hints/newbie.txt">
+http://archive.linuxfromscratch.org/lfs-hints/newbie.txt</ulink>
+ very interesting.
 </para>
 
 <para>