release-notes/devel/en_US Java.xml,1.11,1.12 Kernel.xml,1.18,1.19

Karsten Wade (kwade) fedora-docs-commits at redhat.com
Wed Apr 4 08:54:18 UTC 2007


Author: kwade

Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv32635

Modified Files:
	Java.xml Kernel.xml 
Log Message:
ready for test4


Index: Java.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Java.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- Java.xml	4 Apr 2007 01:29:33 -0000	1.11
+++ Java.xml	4 Apr 2007 08:54:16 -0000	1.12
@@ -2,105 +2,91 @@
 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
 
 <section id="sn-Java">
-  <articleinfo>
-    <title>Docs/Beats/Java</title>
-  </articleinfo>
-
   <title>Java and java-gcj-compat</title>
 
-  <para></para>
-
   <para>
     This release of Fedora includes a free and open source Java
-    environment called <code>java-gcj-compat</code>. The
-    <code>java-gcj-compat</code> collection includes a tool suite and
+    environment called <package>java-gcj-compat</package>. The
+    <package>java-gcj-compat</package> collection includes a tool suite and
     execution environment that is capable of building and running many
     useful programs that are written in the Java programming language.
   </para>
-
-  <para>
-    [[Admonition("note", "Fedora Does Not Include Java", "Java is a
-    trademark of Sun Microsystems. <code>java-gcj-compat</code> is an
-    entirely free software stack that is
-    <emphasis role='strong'>not</emphasis> Java, but may run Java
-    software.")]]
-  </para>
-
+  <note>
+    <title>Fedora Does Not Include Java</title>
+    <para>
+      Java is a trademark of Sun Microsystems.
+      <package>java-gcj-compat</package> is an entirely free software stack that
+      is <emphasis role='strong'>not</emphasis> Java, but may run Java
+      software.
+    </para>
+  </note>
   <para>
-    The java-gcj infrastructure has three key components: a
-    <emphasis role='strong'>GNU Java</emphasis> runtime
-    (<code>libgcj</code>), the <emphasis role='strong'>Eclipse
-    Java</emphasis> compiler (<code>ecj</code>), and a set of wrappers
-    and links (<code>java-gcj-compat</code>) that present the runtime
-    and compiler to the user in a manner similar to other Java
-    environments.
+    The java-gcj infrastructure has three key components: a GNU Java runtime
+    (<command>libgcj</command>), the <application>Eclipse</application> Java
+    compiler (<command>ecj</command>), and a set of wrappers and links
+    (<package>java-gcj-compat</package>) that present the runtime and compiler
+    to the user in a manner similar to other Java environments.
   </para>
 
   <para>
     The Java software packages in this Fedora release use the
-    <code>java-gcj-compat</code> environment. These packages include
-    <emphasis role='strong'>Open<code></code>Office.org Base</emphasis>,
-    <emphasis role='strong'>Eclipse</emphasis>, and
-    <emphasis role='strong'>Apache Tomcat</emphasis>. Refer to the Java
+    <package>java-gcj-compat</package> environment. These packages include
+    <application>OpenOffice.org Base</application>,
+    <application>Eclipse</application>, and
+    <emphasis rolc=app
+e='strong'>Apache Tomcat</emphasis>. Refer to the Java
     FAQ at
     <ulink url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
-    for more information on the <code>java-gcj-compat</code> free Java
+    for more information on the <package>java-gcj-compat</package> free Java
     environment in Fedora.
   </para>
-
-  <para>
-    [[Admonition("important", "Include Location and Version Information
-    in Bug Reports", "When making a bug report, be sure to include the
-    output from these commands:")]]
+  <important>
+    <title>Include Location and Version Information in Bug Reports</title>
+    <para>
+      When making a bug report, be sure to include the
+      output from these commands:
   </para>
-
-  <para/>
-
 <screen><![CDATA[which java && java -version && which javac && javac -version 
 ]]></screen>
+  </important>
 
-  <para/>
-
-  <section>
+  <section id="sn-Handling-Java-and-Java-like-Packages">
     <title>Handling Java and Java-like Packages</title>
     <para>
-      In addition to the <code>java-gcj-compat</code> free software
+      In addition to the <package>java-gcj-compat</package> free software
       stack, Fedora lets you install multiple Java implementations and
-      switch between them using the <code>alternatives</code> command
+      switch between them using the <command>alternatives</command> command
       line tool. However, every Java system you install must be packaged
       using the JPackage Project packaging guidelines to take advantage
-      of <code>alternatives</code>. Once these packages are installed
-      properly, the <code>root</code> user may switch between
-      <code>java</code> and <code>javac</code> implementations using the
-      <code>alternatives</code> command:
+      of <command>alternatives</command>. Once these packages are installed
+      properly, the root user may switch between
+      <command>java</command> and <command>javac</command> implementations using the
+      <command>alternatives</command> command:
     </para>
-    <para/>
 <screen><![CDATA[alternatives --config java  
 alternatives --config javac
 ]]></screen>
-    <para/>
   </section>
 
-  <section>
+  <section id="sn-Handling-Java-Applets">
     <title>Handling Java Applets</title>
     <para>
       This release of Fedora includes a preview release of
-      <code>gcjwebplugin</code>, a Firefox plugin for Java applets.
-      <code>gcjwebplugin</code> is not enabled by default because
-      although the security implementation in GNU Classpath is being
-      actively developed, it is not mature enough to run untrusted
-      applets safely. That said, the AWT and Swing implementations in
-      GNU Classpath are now sufficiently mature that they can run many
-      applets deployed on the web. Adventurous users who want to try
-      <code>gcjwebplugin</code> can read
-      <code>/usr/share/doc/libgcj-4.1.2/README.libgcjwebplugin.so</code>,
-      as installed by the <code>libgcj</code> rpm. The README explains
-      how to enable the plugin and the risks associated with doing so.
+      <package>gcjwebplugin</package>, a Firefox plugin for Java applets.
+      <package>gcjwebplugin</package> is not enabled by default because although
+      the security implementation in GNU Classpath is being actively developed,
+      it is not mature enough to run untrusted applets safely. That said, the
+      AWT and Swing implementations in GNU Classpath are now sufficiently mature
+      that they can run many applets deployed on the web. Adventurous users who
+      want to try <package>gcjwebplugin</package> can read
+      <filename>/usr/share/doc/libgcj-4.1.2/README.libgcjwebplugin.so</filename>, 
+      as installed by the <package>libgcj</package> package. The
+      <filename>README</filename> explains how to enable the plugin and the
+      risks associated with doing so.
     </para>
-    <para/>
   </section>
 
-  <section>
+  <section id="sn-Fedora-and-the-JPackage-Java-Packages">
     <title>Fedora and the JPackage Java Packages</title>
     <para>
       Fedora includes many packages derived from the JPackage Project,
@@ -113,40 +99,41 @@
       <ulink url='http://jpackage.org'>http://jpackage.org</ulink> for
       more information on the project and the software it provides.
     </para>
+    <warning>
+      <title>Mixing Packages from Fedora and JPackage</title>
+      <para>
+	Research package compatibility before you install software from both the
+	Fedora and JPackage repositories on the same system. Incompatible
+	packages may cause complex issues.
+      </para>
+    </warning>    
     <para>
-      [[Admonition("warning", "Mixing Packages from Fedora and
-      JPackage", "Research package compatibility before you install
-      software from both the Fedora and JPackage repositories on the
-      same system. Incompatible packages may cause complex issues.")]]
-    </para>
-    <para>
-      Refer to the latest release notes pertaining to Eclipse
-      <ulink url='http://fedoraproject.org/wiki/Docs/Beats/Devel/Tools/Eclipse'>here</ulink>.
-    </para>
+      Refer to the latest release notes pertaining to Eclipse at
+      <ulink url='http://fedoraproject.org/wiki/Docs/Beats/Devel/Tools/Eclipse'>http://fedoraproject.org/wiki/Docs/Beats/Devel/Tools/Eclipse</ulink>.
     <para/>
   </section>
 
-  <section>
+  <section id="sn-Maven-v2">
     <title>Maven (v2)</title>
     <para>
-      This release of Fedora includes <code>maven2</code>, a Java
+      This release of Fedora includes <package>maven2</package>, a Java
       project management and project comprehension tool. Maven can be
-      invoked by the <code>mvn</code> and <code>mvn-jpp</code> commands.
+      invoked by the <command>mvn</command> and <command>mvn-jpp</command> commands.
       The former makes Maven behave just like upstream Maven, while the
-      latter calls <code>mvn</code> with additional properties that make
+      latter calls <command>mvn</command> with additional properties that make
       off-line building easier.
     </para>
     <para>
-      The <code>maven2</code> package in Fedora is modified to work in a
+      The <package>maven2</package> package in Fedora is modified to work in a
       fully off-line mode. With no additional properties defined (the
-      <code>mvn</code> command), <code>maven2</code> works exactly like
+      <command>mvn</command> command), <command>maven2</command> works exactly like
       upstream Maven. Users may define additional properties to
-      facilitate off-line builds, or call <code>mvn-jpp</code>, a
+      facilitate off-line builds, or call <command>mvn-jpp</command>, a
       wrapper that defines the most commonly used properties for
       off-line building. The properties and their usage details are
       described in the
-      <code>/usr/share/doc/maven2-2.0.4/maven2-jpp-readme.html</code>
-      file, which comes from the <code>maven2-manual</code> package.
+      <filename>/usr/share/doc/maven2-2.0.4/maven2-jpp-readme.html</filename>
+      file, which comes from the <package>maven2-manual</package> package.
     </para>
   </section>
 </section>


Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/devel/en_US/Kernel.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- Kernel.xml	4 Apr 2007 07:13:24 -0000	1.18
+++ Kernel.xml	4 Apr 2007 08:54:16 -0000	1.19
@@ -2,25 +2,15 @@
 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
 
 <section id="sn-Kernel">
-  <articleinfo>
-    <title>Docs/Beats/Kernel</title>
-  </articleinfo>
-
   <title>Linux Kernel</title>
 
-  <para></para>
-
-  <para>
-    [[Admonition("note","Assumptions Based on 2.6.21","This draft of the
-    release notes assume that the final release of Fedora 2.6.21 is
-    based on kernel 2.6.21. This is subject to change.")]]
-  </para>
-
-  <para/>
-
-  <para/>
-
-  <para/>
+  <note>
+    <title>Assumptions Based on 2.6.21</title>
+    <para>
+      This draft of the release notes assume that the final release of Fedora
+      2.6.21 is based on kernel 2.6.21. This is subject to change.
+    </para>
+  </note>
 
   <para>
     This section covers changes and important information regarding the
@@ -28,7 +18,9 @@
   </para>
 
   <itemizedlist>
-    <listitem>Support for KVM virtualization. </listitem>
+    <listitem>
+      <para>Support for KVM virtualization.</para>
+    </listitem>
     <listitem>
       <para>
         Tickless support for x86 32bit, which greatly improves power
@@ -36,14 +28,28 @@
         also be tickless.
       </para>
     </listitem>
-    <listitem>The devicescape wireless network stack, which includes support for several new wireless drivers. </listitem>
-    <listitem>New IDE drivers that use the same libata code as the SATA drivers. <itemizedlist>
-        <listitem>[[Admonition("note","IDE Device Names Changed","The new IDE drivers now cause all IDE drives to have device names like /dev/sdX instead of /dev/hdX.")]] </listitem>
-      </itemizedlist>
+    <listitem>
+      <para>The devicescape wireless network stack, which includes support for
+      several new wireless drivers.</para>
+    </listitem>
+    <listitem>
+      <para>New IDE drivers that use the same libata code as the SATA
+      drivers.</para>
+      <note>
+	<title>IDE Device Names Changed</title>
+	<para>The new IDE drivers now cause all IDE drives to have device names
+	such as /dev/sdX instead of /dev/hdX.</para>
+      </note>
+    </listitem>
+    <listitem>
+      <para>Support for version 2 of the Global File System (GFS2).</para> 
+    </listitem>
+    <listitem>
+      <para>Some elements of the realtime kernel project.</para>
+    </listitem>
+    <listitem>
+      <para>Many bug fixes and other small improvements.</para>
     </listitem>
-    <listitem>Support for version 2 of the Global File System (GFS2). </listitem>
-    <listitem>Some elements of the realtime kernel project. </listitem>
-    <listitem>Many bug fixes and other small improvements. </listitem>
     <listitem>
       <para>
         Changelog for 2.6.21rc1 available here:
@@ -52,15 +58,13 @@
     </listitem>
   </itemizedlist>
 
-  <para/>
-
-  <section>
+  <section id="sn-Version">
     <title>Version</title>
     <para>
       Fedora may include additional patches to the kernel for
       improvements, bug fixes, or additional features. For this reason,
       the Fedora kernel may not be line-for-line equivalent to the
-      so-called <emphasis>vanilla kernel</emphasis> from the kernel.org
+      so-called <firstterm>vanilla kernel</firstterm> from the kernel.org
       web site:
     </para>
     <para>
@@ -73,16 +77,14 @@
     <para/>
 <screen><![CDATA[rpm -qpl kernel-<version>.src.rpm 
 ]]></screen>
-    <para/>
   </section>
 
-  <section>
+  <section id="sn-Changelog">
     <title>Changelog</title>
     <para>
       To retrieve a log of changes to the package, run the following
       command:
     </para>
-    <para/>
 <screen><![CDATA[rpm -q --changelog kernel-<version> 
 ]]></screen>
     <para>
@@ -93,19 +95,15 @@
       The Fedora version kernel is based on the Linus tree.
     </para>
     <para>
-      Customizations made for the Fedora version are available from
-      <ulink url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink>
-      .
+      Customizations made for the Fedora version are available from <ulink
+	url='http://cvs.fedoraproject.org'>http://cvs.fedoraproject.org</ulink>.
     </para>
     <para/>
   </section>
 
-  <section>
+  <section id="sn-Kernel-Flavors">
     <title>Kernel Flavors</title>
     <para>
-      <anchor id='Kernel_Flavors'/>
-    </para>
-    <para>
       Fedora 7 includes the following kernel builds:
     </para>
     <itemizedlist>
@@ -113,13 +111,13 @@
         <para>
           Native kernel, for use in most systems. Configured sources are
           available in the
-          <code>kernel-devel-<version>.<arch>.rpm</code> package.
+          <package>kernel-devel-<version>.<arch>.rpm</package> package.
         </para>
       </listitem>
       <listitem>
         <para>
-          The kernel-PAE, for use in 32-bit x86 systems with > 4GB of
-          RAM, or with CPUs that have a 'NX (No eXecute)' feature. This
+          The kernel-PAE, for use in 32-bit x86 systems with > 4GB of
+          RAM, or with CPUs that have an 'NX (No eXecute)' feature. This
           kernel support both uniprocessor and multi-processor systems.
         </para>
       </listitem>
@@ -127,7 +125,7 @@
         <para>
           Virtualization kernel for use with the Xen emulator package.
           Configured sources are available in the
-          <code>kernel-xen-devel-<version>.<arch>.rpm</code>
+          <package>kernel-xen-devel-<version>.<arch>.rpm</package>
           package.
         </para>
       </listitem>
@@ -135,7 +133,7 @@
         <para>
           The kdump kernel for use with kexec/kdump capabilities.
           Configured sources are available in the
-          <code>kernel-kdump-devel-<version>.<arch>.rpm</code>
+          <package>kernel-kdump-devel-<version>.<arch>.rpm</package>
           package.
         </para>
       </listitem>
@@ -143,7 +141,7 @@
     <para>
       You may install kernel headers for all kernel flavors at the same
       time. The files are installed in the
-      <code>/usr/src/kernels/<version>-[PAE|xen|kdump]-<arch>/</code>
+      <package>/usr/src/kernels/<version>-[PAE|xen|kdump]-<arch>/</package>
       tree. Use the following command:
     </para>
     <para/>
@@ -153,26 +151,30 @@
       Select one or more of these flavors, separated by commas and no
       spaces, as appropriate. Enter the root password when prompted.
     </para>
-    <para>
-      [[Admonition("note","32bit Kernel Includes Kdump","The 32bit
-      kernel is now relocatable, so kdump functionality is included.
-      64bit still requires installation of the -kdump kernel.")]]
-    </para>
-    <para>
-      [[Admonition("note","Default Kernel Provides SMP","There is no
-      separate SMP kernel available for Fedora on i386, x86_64, and
-      ppc64. Multiprocessor support is provided by the native
-      kernel.")]]
-    </para>
-    <para>
-      [[Admonition("note", "PowerPC Kernel Support", "There is no
-      support for Xen or kdump for the PowerPC architecture in Fedora.
-      32-bit PowerPC does still have a separate SMP kernel.")]]
-    </para>
-    <para/>
+    <note>
+      <title>32bit Kernel Includes Kdump</title>
+      <para>
+	The 32bit kernel is now relocatable, so kdump functionality is included.
+	64bit still requires installation of the <package>-kdump</package> kernel.
+      </para>
+    </note>
+    <note>
+      <title>Default Kernel Provides SMP</title>
+      <para>
+	There is no separate SMP kernel available for Fedora on i386, x86_64,
+	and ppc64. Multiprocessor support is provided by the native kernel.
+      </para>
+    </note>
+    <note>
+      <title>PowerPC Kernel Support</title>
+      <para>
+	There is no support for Xen or kdump for the PowerPC architecture in
+	Fedora. 32-bit PowerPC does still have a separate SMP kernel.
+      </para>
+    </note>
   </section>
 
-  <section>
+  <section id="sn-Reporting-Bugs">
     <title>Reporting Bugs</title>
     <para>
       Refer to
@@ -182,137 +184,116 @@
       <ulink url='http://bugzilla.redhat.com'>http://bugzilla.redhat.com</ulink>
       for reporting bugs that are specific to Fedora.
     </para>
-    <para/>
   </section>
 
-  <section>
+  <section id="sn-Following-Generic-Textbooks">
     <title>Following Generic Textbooks</title>
     <para>
       Many of the tutorials, examples, and textbooks about Linux kernel
       development assume the kernel sources are installed under the
-      <code>/usr/src/linux/</code> directory. If you make a symbolic
+      <filename>/usr/src/linux/</filename> directory. If you make a symbolic
       link, as shown below, you should be able to use those learning
       materials with the Fedora packages. Install the appropriate kernel
       sources, as shown earlier, and then run the following command:
     </para>
-    <para/>
 <screen><![CDATA[su -c 'ln -s /usr/src/kernels/<version>.<release>-<arch> /usr/src/linux' 
 ]]></screen>
     <para>
-      Enter the <code>root</code> password when prompted.
+      Enter the root password when prompted.
     </para>
-    <para/>
   </section>
 
-  <section>
+  <section id="sn-Preparing-for-Kernel-Development">
     <title>Preparing for Kernel Development</title>
     <para>
-      Fedora 7 does not include the kernel-source package provided by
-      older versions since only the kernel-devel package is required now
-      to build external modules. Configured sources are available, as
-      described in the kernel flavors section.
-    </para>
-    <para>
-      [[Admonition("note", "Instructions Refer to Current Kernel", "To
-      simplify the following directions, we have assumed that you want
-      to configure the kernel sources to match your currently-running
-      kernel. In the steps below, the expression <version> refers to
-      the kernel version shown by the command: <code>uname -r</code>."]]
+      Fedora 7 does not include the <package>kernel-source</package> package
+      provided by older versions since only the <package>kernel-devel</package>
+      package is required now to build external modules. Configured sources are
+      available, as described in the kernel flavors section.
     </para>
+    <note>
+      <title>Instructions Refer to Current Kernel</title>
+      <para>
+	To simplify the following directions, we have assumed that you want to
+	configure the kernel sources to match your currently-running kernel. In
+	the steps below, the expression <version> refers to the kernel
+	version shown by the command: <command>uname -r</command>.
+      </para>
+    </note>  
     <para>
-      Users who require access to Fedora original kernel sources can
-      find them in the kernel .src.rpm package. To create an exploded
+      Users who require access to Fedora original kernel sources can find them
+      in the kernel <package>.src.rpm</package> package. To create an exploded
       source tree from this file, perform the following steps:
     </para>
+    <note>
+      <title>Do Not Build Packages as Super-user (root)</title>
     <para>
-      [[Admonition("note", "Do Not Build Packages as Super-user (root)",
-      "Building packages as the superuser is inherently dangerous and is
-      not required, even for the kernel. These instructions allow you to
-      install the kernel source as a normal user. Many general
-      information sites refer to <code>/usr/src/linux</code> in their
-      kernel instructions. If you use these instructions, simply
-      substitute
-      <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></code>."]]
-    </para>
-    <orderedlist numeration='arabic'>
-      <listitem>Prepare an RPM package building environment in your home directory.  Run the following commands: </listitem>
-    </orderedlist>
-    <para/>
+	Building packages as the superuser is inherently dangerous and is not
+	required, even for the kernel. These instructions allow you to install
+	the kernel source as a normal user. Many general information sites refer
+	to <filename>/usr/src/linux</filename> in their kernel instructions. If
+	you use these instructions, simply substitute
+	<filename>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></filename>."]]
+      </para>
+    </note>    
+    <procedure>
+      <step>
+	<para>Prepare an RPM package building environment in your home
+	directory.  Run the following commands:</para> 
 <screen><![CDATA[su -c 'yum install rpmdevtools yum-utils' 
 rpmdev-setuptree
 ]]></screen>
-    <itemizedlist>
-      <listitem>
         <para>
-          Enter the <code>root</code> password when prompted.
+          Enter the root password when prompted.
         </para>
-      </listitem>
-    </itemizedlist>
-    <orderedlist numeration='arabic'>
-      <listitem>
+      </step>
+      <step>
         <para>
           Download the <code>kernel-<version>.src.rpm</code> file.
           Enable any appropriate source repositories, such as Core,
           Updates, or Testing, with the <code>-e</code> switch:
         </para>
-      </listitem>
-    </orderedlist>
-    <para/>
 <screen><![CDATA[yumdownloader -e core-source -e updates-source --source kernel-<version>
 ]]></screen>
-    <itemizedlist>
-      <listitem>
         <para>
-          Enter the <code>root</code> password when prompted.  If you do not
+          Enter the root password when prompted.  If you do not
 	  specify the version, the latest kernel available in Fedora is
 	  downloaded.
         </para>
-      </listitem>
-    </itemizedlist>
-    <orderedlist numeration='arabic'>
-      <listitem>
+      </step>
+      <step>
         <para>
           Install <code>kernel-<version>.src.rpm</code> using the
           command:
         </para>
-      </listitem>
-    </orderedlist>
-    <para/>
 <screen><![CDATA[su -c 'rpm -Uvh kernel-<version>.src.rpm' 
 ]]></screen>
-    <itemizedlist>
-      <listitem>
         <para>
           This command writes the RPM contents into
           <code>${HOME}/rpmbuild/SOURCES</code> and
           <code>${HOME}/rpmbuild/SPECS</code>, where
           <code>${HOME}</code> is your home directory.
         </para>
-      </listitem>
-    </itemizedlist>
-    <para>
-      [[Admonition("note", "Space Required", "The full kernel building
-      process may require several gigabytes of extra space on the file
-      system containing your home directory."]]
-    </para>
-    <orderedlist numeration='arabic'>
-      <listitem>Prepare the kernel sources using the commands: </listitem>
-    </orderedlist>
-    <para/>
+	<note>
+	  <title>Space Required</title>
+	  <para>
+	    The full kernel building process may require several gigabytes of
+	    extra space on the file system containing your home directory.
+	  </para>
+	</note>
+      </step>
+      <step>
+	<para>Prepare the kernel sources using the commands:</para>
 <screen><![CDATA[cd ~/rpmbuild/SPECS 
 rpmbuild -bp --target $(uname -m) kernel-2.6.spec
 ]]></screen>
-    <itemizedlist>
-      <listitem>
         <para>
           The kernel source tree is located in the
           <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version>.<arch></code>
           directory.
         </para>
-      </listitem>
-    </itemizedlist>
-    <orderedlist numeration='arabic'>
-      <listitem>
+      </step>
+      <step>
         <para>
           The configurations for the specific kernels shipped in Fedora
           7 are in the
@@ -322,13 +303,10 @@
           Issue the following command to place the desired configuration
           file in the proper place for building:
         </para>
-      </listitem>
-    </orderedlist>
-    <para/>
 <screen><![CDATA[cp configs/<desired-config-file> .config 
 ]]></screen>
-    <orderedlist numeration='arabic'>
-      <listitem>
+      </step>
+      <step>
         <para>
           Every kernel gets a name based on its version number. This is
           the value the <code>uname -r</code> command displays. The
@@ -340,69 +318,56 @@
           compiled for a kernel with the correct name. To do this, you
           must edit the kernel <code>Makefile</code>.
         </para>
-        <itemizedlist>
-          <listitem>
-            <para>
-              For example, if the <code>uname -r</code> returns the
-              string <code>2.6.17-1.2345_FC6</code>, change the
-              <code>EXTRAVERSION</code> definition from this:
-            </para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-    </orderedlist>
-    <para/>
+	<para>
+	  For example, if the <code>uname -r</code> returns the
+	  string <code>2.6.17-1.2345_FC6</code>, change the
+	  <code>EXTRAVERSION</code> definition from this:
+	</para>
 <screen><![CDATA[EXTRAVERSION = -prep 
 ]]></screen>
-    <itemizedlist>
-      <listitem>to this: </listitem>
-    </itemizedlist>
-    <para/>
+	<para>to this: </para>
 <screen><![CDATA[EXTRAVERSION = -1.2345_FC6 
 ]]></screen>
-    <itemizedlist>
-      <listitem>That is, substitute everything from the final dash onward. </listitem>
-    </itemizedlist>
-    <orderedlist numeration='arabic'>
-      <listitem>Run the following command: </listitem>
-    </orderedlist>
-    <para/>
+	<para>That is, substitute everything from the final dash onward.</para>
+      </step>
+      <step>
+	<para>Run the following command: </para>
 <screen><![CDATA[make oldconfig 
 ]]></screen>
-    <itemizedlist>
-      <listitem>You may then proceed as usual. </listitem>
-    </itemizedlist>
-    <para>
-      [[Admonition("note","Building Kernel Binary RPMs","Normally,
-      kernels for Fedora are built using the <code>rpmbuild</code>
-      utility and a specfile. Your results may vary if you use the
-      kernel's built-in <code>make rpm</code> target.")]]
-    </para>
-    <para/>
+	<para>You may then proceed as usual.</para>
+      </step>
+    </procedure>
+    <note>
+      <title>Building Kernel Binary RPMs</title>
+      <para>
+	Normally, kernels for Fedora are built using the
+	<command>rpmbuild</command> utility and a specfile. Your results may
+	vary if you use the kernel's built-in <command>make rpm</command>
+	target.
+      </para>
+    </note>
   </section>
 
-  <section>
+  <section id="sn-Building-Only-Kernel-Modules">
     <title>Building Only Kernel Modules</title>
     <para>
-      An exploded source tree is not required to build a kernel module,
-      such as your own device driver, against the currently in-use
-      kernel. Only the <code>kernel-devel</code> package is required to
-      build external modules. If you did not select it during
-      installation, use <emphasis role='strong'>Pirut</emphasis> to
-      install it (via <emphasis>Applications > Add/Remove
-      Software</emphasis>) or use <code>yum</code> to install it. Run
-      the following command to install the <code>kernel-devel</code>
-      package using <code>yum</code>.
+      An exploded source tree is not required to build a kernel module, such as
+      your own device driver, against the currently in-use kernel. Only the
+      <package>kernel-devel</package> package is required to build external
+      modules. If you did not select it during installation, use
+      <application>Pirut</application> to install it (via
+      <guimenu>Applications</guimenu><guimenuitem>Add/Remove
+	Software</guimenuitem>) or use <command>yum</command> to install it. Run
+      the following command to install the <package>kernel-devel</package>
+      package using <command>yum</command>.
     </para>
-    <para/>
 <screen><![CDATA[su -c 'yum install kernel-devel' 
 ]]></screen>
     <para>
-      For example, to build the <code>foo.ko</code> module, create the
-      following <code>Makefile</code> in the directory containing the
-      <code>foo.c</code> file:
+      For example, to build the <filename>foo.ko</filename> module, create the
+      following <filename>Makefile</filename> in the directory containing the
+      <filename>foo.c</filename> file:
     </para>
-    <para/>
 <screen><![CDATA[obj-m := foo.o 
 
 KDIR  := /lib/modules/$(shell uname -r)/build
@@ -412,8 +377,8 @@
     $(MAKE) -C $(KDIR) M=$(PWD) modules
 ]]></screen>
     <para>
-      Issue the <code>make</code> command to build the
-      <code>foo.ko</code> module.
+      Issue the <command>make</command> command to build the
+      <filename>foo.ko</filename> module.
     </para>
   </section>
 </section>




More information about the Fedora-docs-commits mailing list