[gentoo-doc-cvs] cvs commit: genkernel.xml

[Camille Huot]

cam         05/09/04 23:18:51

  Modified:    xml/htdocs/doc/en genkernel.xml
  Log:
  Fixed typo in mount arguments order + some "international" style corrections.

Revision  Changes    Path
1.25      +28 -26    xml/htdocs/doc/en/genkernel.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/genkernel.xml?rev=1.25&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/genkernel.xml?rev=1.25&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/genkernel.xml.diff?r1=1.24&r2=1.25&cvsroot=gentoo

Index: genkernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- genkernel.xml	4 Sep 2005 23:04:25 -0000	1.24
+++ genkernel.xml	4 Sep 2005 23:18:51 -0000	1.25
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v 1.24 2005/09/04 23:04:25 cam Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v 1.25 2005/09/04 23:18:51 cam Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/genkernel.xml">
@@ -26,8 +26,8 @@
 
 <license/>
 
-<version>1.4.1</version>
-<date>2005-08-11</date>
+<version>1.4.2</version>
+<date>2005-09-05</date>
 
 <chapter>
 <title>Introduction</title>
@@ -179,7 +179,7 @@
     command line.
   </li>
   <li>
-    <b>--<c>no-</c>save-config</b>: Saves [or does not save] the kernel
+    <b>--<c>no-</c>save-config</b>: Saves <e>[or does not save]</e> the kernel
     configuration to a file in the <path>/etc/kernels/</path> directory for
     later use.
   </li>
@@ -328,9 +328,9 @@
     (1) to the number of CPUs used by the system. So, for a system with one
     CPU, the appropriate flag is <c>-j2</c>; a system with two CPUs will use
     the <c>-j3</c> flag, and so on. <e>(A system with one processor that
-    supports Hyper-Threading™ (HT) Technology can use the</e><c>-j3</c>
-    <e>flag, provided Symmetric Multi-Processing (SMP) support is enabled in
-    the kernel.)</e>
+    supports Hyper-Threading&trade; (HT) Technology can use the
+    </e><c>-j3</c><e> flag, provided Symmetric Multi-Processing (SMP) support is
+    enabled in the kernel.)</e>
   </li>
 </ul>
 
@@ -360,8 +360,8 @@
     <path>/var/log/genkernel.log</path> by default.
   </li>
   <li>
-    <b>--no-color</b>: Activates [or deactivates] colored output of debugging
-    information (reported by genkernel) using escape sequences.
+    <b>--no-color</b>: Activates <e>[or deactivates]</e> colored output of
+    debugging information (reported by genkernel) using escape sequences.
   </li>
 </ul>
 
@@ -425,9 +425,9 @@
     link="http://evms.sourceforge.net/">Enterprise Volume Management
     System</uri> (EVMS2), if available. Be sure to install the evms package on
     your system with <c>USE=static emerge evms2</c> before using this
-    (genkernel) flag. <e>(Omitting the </e><c>USE=static</c> <e>flag during
-    package installation will fail to include the necessary static binaries.)
-    </e>
+    (genkernel) flag. <e>(Omitting the </e><c>USE=static</c><e> flag during
+    package installation will fail to include the necessary static
+    binaries.)</e>
   </li>
   <li>
     <b>--dmraid</b>: Includes support for <uri
@@ -438,11 +438,11 @@
   </li>
   <li>
     <b>--linuxrc=/path/to/your/linuxrc</b>: Specifies a user-created
-    <e>linuxrc</e> — a script that is initialized during the start-up stage of
-    the kernel, prior to the actual boot process. (A default linuxrc script
-    should be in the <path>/usr/share/genkernel/</path> directory.) This script
-    allows you to boot into a small, modularized kernel and load the drivers
-    that are needed (as modules) by the system.
+    <e>linuxrc</e> &mdash; a script that is initialized during the start-up
+    stage of the kernel, prior to the actual boot process. (A default linuxrc
+    script should be in the <path>/usr/share/genkernel/</path> directory.) This
+    script allows you to boot into a small, modularized kernel and load the
+    drivers that are needed (as modules) by the system.
   </li>
   <li>
     <b>--cachedir=/path/to/alt/dir/</b>: Overrides the default cache location
@@ -500,7 +500,9 @@
   <li><c>initrd</c>: Only builds the initrd image</li>
   <li><c>bzImage</c>: Only builds the kernel image</li>
   <li><c>kernel</c>: Only builds the kernel image and modules</li>
-  <li><c>all</c>: Builds all stages — the initrd, kernel image and modules.</li>
+  <li>
+    <c>all</c>: Builds all stages &mdash; the initrd, kernel image and modules.
+  </li>
 </ul>
 
 <p>
@@ -586,7 +588,7 @@
     kernel's source tree. Setting this option to 'no' creates a cascade effect
     &#8212; it is equivalent to genkernel's <c>--no-clean</c> flag, which
     disables the <c>make clean</c> command and implies genkernel's
-    <c>--no-mrproper</c> flag &#8212; essentially nullifying the <c>make
+    <c>--no-mrproper</c> flag &mdash; essentially nullifying the <c>make
     mrproper</c> command.
   </li>
   <li>
@@ -619,10 +621,10 @@
   </li>
   <li>
     <b>DEBUGLEVEL=<c>[0|1|2|3|4|5]</c></b>: This option is for adjusting the
-    verbosity of the output produced by genkernel — setting this option to '0'
-    with <c>--debuglevel=0</c> will suppress all output produced by genkernel;
-    setting this option to '5' with <c>--debuglevel=5</c> provides the user
-    with all output produced by genkernel.
+    verbosity of the output produced by genkernel &mdash; setting this option to
+    '0' with <c>--debuglevel=0</c> will suppress all output produced by
+    genkernel; setting this option to '5' with <c>--debuglevel=5</c> provides
+    the user with all output produced by genkernel.
   </li>
 </ul>
 
@@ -700,7 +702,7 @@
 and the <c>IP: DHCP support</c> options. This avoids an unnecessary layer of
 complexity since the IP address and the NFS path to the Installation CD can be
 configured on a DHCP server. Of course, this means the kernel command line
-will remain constant for any machine — which is very important for
+will remain constant for any machine &mdash; which is very important for
 <e>etherbooting</e>.
 </p>
 
@@ -737,7 +739,7 @@
 <pre caption="Creating a compressed tarball containing the kernel modules">
 <comment>(Create a tar.gz containing all the modules)</comment>
 # <i>cd /</i>
-# <i> tar -cf /tmp/modules-X.Y.Z.tar.gz /lib/modules/X.Y.Z/</i>
+# <i>tar -cf /tmp/modules-X.Y.Z.tar.gz /lib/modules/X.Y.Z/</i>
 </pre>
 
 <p>
@@ -784,7 +786,7 @@
 
 <pre caption="Preparing the NFS share">
 <comment>(This assumes that /nfs/livecd is a exported NFS share)</comment>
-# <i>mount /mnt/cdrom /tmp/gentoo-livecd.iso -o loop</i>
+# <i>mount /tmp/gentoo-livecd.iso /mnt/cdrom -o loop</i>
 # <i>cp -p /mnt/cdrom /nfs/livecd</i>
 # <i>umount /mnt/cdrom</i>
 



-- 
gentoo-doc-cvs@g.o mailing list