aboutsummaryrefslogtreecommitdiffstats
path: root/chapter01
diff options
context:
space:
mode:
authorManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-05-29 20:00:54 +0000
committerManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-05-29 20:00:54 +0000
commit55851d6ef3b438d78359c9ea0ba861069bedeeb1 (patch)
treed9f97db0df5856fb68fd325a4885b9edbf2d5c90 /chapter01
parentd44a965cfe95996da670a7f053cb30222e41b36f (diff)
Tagging corrections in chapters 1 to 4.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3725 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter01')
-rw-r--r--chapter01/administrativa.xml10
-rw-r--r--chapter01/askforhelp.xml10
2 files changed, 10 insertions, 10 deletions
diff --git a/chapter01/administrativa.xml b/chapter01/administrativa.xml
index c21d010d0..2b63714cd 100644
--- a/chapter01/administrativa.xml
+++ b/chapter01/administrativa.xml
@@ -26,8 +26,8 @@ consult the FAQ (Frequently Asked Questions) at
IRC (Internet Relay Chat) network. Before you utilize this mode of support, we
ask that you've at least checked the LFS FAQ (see above) and the mailing list
archives (see below) for the answer to your question. You can find the IRC
-network at <emphasis>irc.linuxfromscratch.org</emphasis> or
-<emphasis>irc.linux-phreak.net</emphasis> port 6667. The support channel is
+network at <uri>irc.linuxfromscratch.org</uri> or
+<uri>irc.linux-phreak.net</uri> port 6667. The support channel is
named #LFS-support.</para>
</sect2>
@@ -36,7 +36,7 @@ named #LFS-support.</para>
<sect2 id="ch-scatter-maillists" xreflabel="Chapter 1 - Mailing lists">
<title>Mailing lists</title>
-<para>The <emphasis>linuxfromscratch.org</emphasis> server is hosting a number
+<para>The <uri>linuxfromscratch.org</uri> server is hosting a number
of mailing lists used for the development of the LFS project. These lists
include, among others, the main development and support lists.</para>
@@ -49,12 +49,12 @@ their archive locations, and so on, visit <ulink url="&lfs-root;mail.html"/>.</p
<sect2 id="ch-scatter-newsserver">
<title>News server</title>
-<para>All the mailing lists hosted at <emphasis>linuxfromscratch.org</emphasis>
+<para>All the mailing lists hosted at <uri>linuxfromscratch.org</uri>
are also accessible via the NNTP server. All messages posted to a mailing list
are copied to the corresponding newsgroup, and vice versa.</para>
<para>The news server can be reached at
-<emphasis>news.linuxfromscratch.org</emphasis>.</para>
+<uri>news.linuxfromscratch.org</uri>.</para>
</sect2>
diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml
index 747a74b92..16517e54f 100644
--- a/chapter01/askforhelp.xml
+++ b/chapter01/askforhelp.xml
@@ -33,9 +33,9 @@ LFS,</para></listitem>
<listitem><para>whether you have deviated from the book at all.</para></listitem>
</itemizedlist>
-<para>(Note that saying that you've deviated from the book doesn't mean
+<note><para>Saying that you've deviated from the book doesn't mean
that we won't help you. After all, LFS is about choice. It'll just
-help us to see other possible causes of your problem.)</para>
+help us to see other possible causes of your problem.</para></note>
</sect2>
@@ -59,7 +59,7 @@ the ./configure script and the make run can be useful. Don't blindly
include the whole thing but, on the other hand, don't include too little.
As an example, here is some screen output from make:</para>
-<screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
+<screen><computeroutput>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
@@ -73,12 +73,12 @@ make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
-make: *** [all-recursive-am] Error 2</screen>
+make: *** [all-recursive-am] Error 2</computeroutput></screen>
<para>In this case, many people just include the bottom section where it
says:</para>
-<screen>make [2]: *** [make] Error 1</screen>
+<screen><computeroutput>make [2]: *** [make] Error 1</computeroutput></screen>
<para>and onwards. This isn't enough for us to diagnose the problem because it
only tells us that <emphasis>something</emphasis> went wrong, not