bitkeeper revision 1.1159.1.331 (4186eea7joEjcJmx6sDGXWsAx1cFAA)

Fixes + more formatting.

docs/src/user.tex

@@ -969,11 +969,11 @@ management functions.  A small set of commands may be issued on the
 Xend command line:
 
 \begin{tabular}{ll}
-\verb_# xend start_ & start Xend, if not already running \\
-\verb_# xend stop_  & stop Xend if already running       \\
-\verb_# xend restart_ & restart Xend if running, otherwise start it \\
-\verb_# xend trace_start_ & start Xend, with very detailed debug logging \\
-\verb_# xend status_ & indicates Xend status by its return code
+\verb!# xend start! & start Xend, if not already running \\
+\verb!# xend stop!  & stop Xend if already running       \\
+\verb!# xend restart! & restart Xend if running, otherwise start it \\
+\verb!# xend trace_start! & start Xend, with very detailed debug logging \\
+\verb!# xend status! & indicates Xend status by its return code
 \end{tabular}
 
 A SysV init script called {\tt xend} is provided to start Xend at boot
@@ -1571,7 +1571,7 @@ http://www.cl.cam.ac.uk/Research/SRG/netos/xen/documentation.html}.
 
 \section{Mailing lists}
 
-There are currently two official Xen mailing lists:
+There are currently three official Xen mailing lists:
 
 \begin{description}
 \item[xen-devel@lists.sourceforge.net] Used for development
@@ -1755,7 +1755,8 @@ to update the hwclock, change the console font, update the keytable
 map, start apmd (power management), or gpm (mouse cursor).  Either
 ignore the errors (they should be harmless), or remove them from the
 startup scripts.  Deleting the following links are a good start:
-S24pcmcia S09isdn S17keytable S26apmd S85gpm.
+\path{S24pcmcia}, \path{S09isdn}, \path{S17keytable}, \path{S26apmd},
+\path{S85gpm}.
 
 If you want to use a single root file system that works cleanly for
 domain0 and domains>0, a useful trick is to use different 'init' run
@@ -1766,14 +1767,14 @@ kernel command line.
 
 If you're going to use NFS root files systems mounted either from an
 external server or from domain0 there are a couple of other gotchas.
-The default /etc/sysconfig/iptables rules block NFS, so part way
-through the boot sequence things will suddenly go dead.
+The default \path{/etc/sysconfig/iptables} rules block NFS, so part
+way through the boot sequence things will suddenly go dead.
 
-If you're planning on having a separate NFS /usr partition, the RH9
-boot scripts don't make life easy - they attempt to mount NFS file
+If you're planning on having a separate NFS \path{/usr} partition, the
+RH9 boot scripts don't make life easy - they attempt to mount NFS file
 systems way to late in the boot process. The easiest way I found to do
-this was to have a '/linuxrc' script run ahead of /sbin/init that
-mounts /usr:
+this was to have a \path{/linuxrc} script run ahead of
+\path{/sbin/init} that mounts \path{/usr}:
 
 \begin{verbatim}
  #!/bin/bash
@@ -1783,19 +1784,21 @@ mounts /usr:
  exec /sbin/init "$@" <>/dev/console 2>&1
 \end{verbatim}
 
-The one slight complication with the above is that /sbib/portmap is
-dynamically linked against /usr/lib/libwrap.so.0 Since this is in
-/usr, it won't work. This can be solved by copying the file (and link)
-below the /usr mount point, and just let the file be 'covered' when
-the mount happens.
+The one slight complication with the above is that
+\path{/sbin/portmap} is dynamically linked against
+\path{/usr/lib/libwrap.so.0} Since this is in \path{/usr}, it won't
+work. This can be solved by copying the file (and link) below the /usr
+mount point, and just let the file be 'covered' when the mount
+happens.
 
-In some installations, where a shared read-only /usr is being used, it
-may be desirable to move other large directories over into the
-read-only /usr. For example, you might replace /bin /lib and /sbin
-with links into /usr/root/bin /usr/root/lib and /usr/root/sbin
-respectively. This creates other problems for running the /linuxrc
-script, requiring bash, portmap, mount, ifconfig, and a handful of
-other shared libraries to be copied below the mount point - little
+In some installations, where a shared read-only \path{/usr} is being
+used, it may be desirable to move other large directories over into
+the read-only \path{/usr}. For example, you might replace \path{/bin},
+\path{/lib} and \path{/sbin} with links into \path{/usr/root/bin},
+\path{/usr/root/lib} and \path{/usr/root/sbin} respectively. This
+creates other problems for running the \path{/linuxrc} script,
+requiring bash, portmap, mount, ifconfig, and a handful of other
+shared libraries to be copied below the mount point - a little
 statically linked C program would solve this problem.