docs/123974: [patch] Fix Markups in FAQ, Question 3.23

[Gabor PALI]

>Number:         123974
>Category:       docs
>Synopsis:       [patch] Fix Markups in FAQ, Question 3.23
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 25 10:50:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Gabor PALI
>Release:        FreeBSD 6.3-STABLE i386
>Organization:
>Environment:
System: FreeBSD disznohal 6.3-STABLE FreeBSD 6.3-STABLE #4: Fri Apr 4 23:29:43 CEST 2008 dezzy at disznohal:/usr/obj/usr/src/sys/GENERIC_ i386

>Description:
	Some markups are missing or misused in the FreeBSD FAQ, Question
	3.23. ``Why do I get a "panic: can't mount root" error when rebooting
	the system after installation?''. I send you a small patch to fix
	them.


>How-To-Repeat:

>Fix:

--- books.faq.patch.11.diff begins here ---
Index: book.sgml
===================================================================
RCS file: /doc/en_US.ISO8859-1/books/faq/book.sgml,v
retrieving revision 1.811
diff -u -r1.811 book.sgml
--- book.sgml	12 Apr 2008 20:13:12 -0000	1.811
+++ book.sgml	25 May 2008 08:21:58 -0000
@@ -1888,11 +1888,11 @@
             systems, with the hard disks arranged as the master or
             single device on separate IDE controllers, with FreeBSD
             installed on the secondary IDE controller. The boot blocks
-            think the system is installed on ad0 (the second BIOS
+            think the system is installed on <devicename>ad0</devicename> (the second BIOS
             disk) while the kernel assigns the first disk on the
-            secondary controller device, ad2. After the device
+            secondary controller device, <devicename>ad2</devicename>. After the device
             probing, the kernel tries to mount what the boot blocks
-            think is the boot disk, ad0, while it is really ad2, and
+            think is the boot disk, <devicename>ad0</devicename>, while it is really <devicename>ad2</devicename>, and
             fails.</para>
 
           <para>To fix the problem, do one of the following:</para>
@@ -1905,10 +1905,10 @@
                   drop you into the boot loader.</para>
 
                 <para>Then type
-                  <literal>
+                  <userinput>
                   set
                   root_disk_unit="<replaceable>disk_number</replaceable>"
-                  </literal>. <replaceable>disk_number</replaceable>
+                  </userinput>. <replaceable>disk_number</replaceable>
                   will be <literal>0</literal> if FreeBSD is installed
                   on the master drive on the first IDE controller,
                   <literal>1</literal> if it is installed on the slave
@@ -1918,13 +1918,13 @@
                   installed on the slave of the second IDE
                   controller.</para>
 
-                <para>Then type <literal>boot</literal>, and your
+                <para>Then type <userinput>boot</userinput>, and your
                   system should boot correctly.</para>
 
                 <para>To make this change permanent (i.e, so you do not
                   have to do this every time you reboot or turn on
-                  your FreeBSD machine), put the line <literal>
-                  root_disk_unit="<replaceable>disk_number</replaceable>"</literal>
+                  your FreeBSD machine), put the line <userinput>
+                  root_disk_unit="<replaceable>disk_number</replaceable>"</userinput>
                   in <filename>/boot/loader.conf.local
                   </filename>.</para>
               </listitem>
--- books.faq.patch.11.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: