aboutsummaryrefslogtreecommitdiffstats
path: root/chapter08/fstab.xml
diff options
context:
space:
mode:
authorGreg Schafer <greg@linuxfromscratch.org>2003-10-09 23:22:07 +0000
committerGreg Schafer <greg@linuxfromscratch.org>2003-10-09 23:22:07 +0000
commit21ba4e3570c1c2524b0733d492ced9634b259353 (patch)
treef5124d2e6106d2e29e5b32f79b56a90defabdbd9 /chapter08/fstab.xml
parent1a7aecc6119f540e24a4e8da1b583a625b5690c1 (diff)
Internal markup reworking to fix the extraneous whitespace problem in the "tidy generated" web site pages. Essentially replace all ocurrences of <para><screen> with <screen> (and of course the matching closing tags).
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2958 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter08/fstab.xml')
-rw-r--r--chapter08/fstab.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter08/fstab.xml b/chapter08/fstab.xml
index b89afd0c2..c52daee44 100644
--- a/chapter08/fstab.xml
+++ b/chapter08/fstab.xml
@@ -7,7 +7,7 @@ determine where partitions are to be mounted by default, which file systems
must be checked and in which order. Create a new file systems table like
this:</para>
-<para><screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"</userinput>
# Begin /etc/fstab
# filesystem mount-point fs-type options dump fsck-order
@@ -19,7 +19,7 @@ devpts /dev/pts devpts gid=4,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
# End /etc/fstab
-<userinput>EOF</userinput></screen></para>
+<userinput>EOF</userinput></screen>
<para>Of course, replace <filename>xxx</filename>, <filename>yyy</filename>
and <filename>fff</filename> with the values appropriate for your system --
@@ -43,7 +43,7 @@ kernel source tree.</para>
<filename>fstab</filename> file. One example is a line to use if you intend to
use USB devices:</para>
-<para><screen>usbfs /proc/bus/usb usbfs defaults 0 0</screen></para>
+<screen>usbfs /proc/bus/usb usbfs defaults 0 0</screen>
<para>This option will of course only work if you have the relevant support
compiled into your kernel.</para>