release-notes/en_US Installer.xml, 1.1, 1.2 Java.xml, 1.1, 1.2 Kernel.xml, 1.1, 1.2
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Wed Apr 12 13:34:21 UTC 2006
Author: kwade
Update of /cvs/docs/release-notes/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv10201
Modified Files:
Installer.xml Java.xml Kernel.xml
Log Message:
These files should now be fixed from the Wiki.
Index: Installer.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Installer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Installer.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Installer.xml 12 Apr 2006 13:34:18 -0000 1.2
@@ -16,50 +16,20 @@
installation program) and installing Fedora Core in general.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/rightsidebar/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Downloading Large
- Files</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- If you intend to download the Fedora Core DVD ISO image,
- keep in mind that not all file downloading tools can
- accommodate files larger than 2GB in size.
- <code>wget</code>
- 1.9.1-16 and above,
- <code>curl</code>
- and
- <code>ncftpget</code>
- do not have this limitation, and can successfully
- download files larger than 2GB.
- <emphasis role='strong'>BitTorrent</emphasis> is another
- method for downloading large files. For information
- about obtaining and using the torrent file, refer to
- <ulink url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
- .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <title>Downloading Large Files</title>
+ <para>
+ If you intend to download the Fedora Core DVD ISO image, keep in mind
+ that not all file downloading tools can accommodate files larger than
+ 2GB in size. <code>wget</code> 1.9.1-16 and above, <code>curl</code> and
+ <code>ncftpget</code> do not have this limitation, and can successfully
+ download files larger than 2GB. <emphasis
+ role='strong'>BitTorrent</emphasis> is another method for downloading
+ large files. For information about obtaining and using the torrent file,
+ refer to <ulink
+ url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
+ </para>
+ </tip>
</section>
<section>
@@ -91,7 +61,9 @@
<code>mediacheck</code>
, boot with the following option:
</para>
-<screen>linux ide=nodma \n</screen>
+<screen>
+linux ide=nodma
+</screen>
<para>
Use the
<code>sha1sum</code>
@@ -99,43 +71,15 @@
This test accurately identifies discs that are not valid or
identical to the ISO image files.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>BitTorrent Automatically
- Verifies File Integrity</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- If you use
- <emphasis role='strong'>BitTorrent</emphasis>, any
- files you download are automatically validated. If
- your file completes downloading, you do not need to
- check it. Once you burn your CD, however, you should
- still use
- <code>mediacheck</code>
- .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <note>
+ <title>BitTorrent Automatically Verifies File Integrity</title>
+ <para>
+ If you use <emphasis role='strong'>BitTorrent</emphasis>, any files
+ you download are automatically validated. If your file completes
+ downloading, you do not need to check it. Once you burn your CD,
+ however, you should still use <code>mediacheck</code> .
+ </para>
+ </note>
</listitem>
<listitem>
<para>
@@ -153,53 +97,24 @@
<code>Esc</code>
key is pressed.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/rightsidebar/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>
- <code>Memtest86</code>
- Availability</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- You must boot from Installation Disc 1 or a rescue
- CD in order to use this feature.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <title><code>Memtest86</code> Availability</title>
+ <para>
+ You must boot from Installation Disc 1 or a rescue CD in order to
+ use this feature.
+ </para>
+ </tip>
</listitem>
<listitem>
<para>
- Fedora Core supports graphical FTP and HTTP installations.
- However, the installer image must either fit in RAM or appear
- on local storage such as Installation Disc 1. Therefore, only
- systems with more than 192MiB of RAM, or which boot from
- Installation Disc 1, can use the graphical installer. Systems
- with 192MiB RAM or less will fall back to using the text-based
- installer automatically. If you prefer to use the text-based
- installer, type
- <code>linux text</code>
- at the
- <code>boot:</code>
- prompt.
+ Fedora Core supports graphical FTP and HTTP installations. However,
+ the installer image must either fit in RAM or appear on local storage
+ such as Installation Disc 1. Therefore, only systems with more than
+ 192MiB of RAM, or which boot from Installation Disc 1, can use the
+ graphical installer. Systems with 192MiB RAM or less will fall back to
+ using the text-based installer automatically. If you prefer to use the
+ text-based installer, type <code>linux text</code> at the
+ <code>boot:</code> prompt.
</para>
</listitem>
</itemizedlist>
@@ -229,58 +144,24 @@
<ulink url='http://fedoraproject.org/wiki/DmraidStatus'>http://fedoraproject.org/wiki/DmraidStatus</ulink>
.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/alert.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>/!\</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Do not boot only half of a
- <code>dmraid</code>
- RAID1 (mirror)</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Various situations may occur that cause
- <code>dmraid</code>
- to break the mirror, and if you boot in read/write
- mode into only one of the mirrored disks, it
- causes the disks to fall out of sync. No symptoms
- arise, since the primary disk is reading and
- writing to itself. But if you attempt to
- re-establish the mirror without first
- synchronizing the disks, you could corrupt the
- data and have to reinstall from scratch without a
- chance for recovery.
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- If the mirror is broken, you should be able to
- resync from within the RAID chipset BIOS or by
- using the
- <code>dd</code>
- command. Reinstallation is always an option.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <warning>
+ <title>Do not boot only half of a <code>dmraid</code> RAID1
+ (mirror)</title>
+ <para>
+ Various situations may occur that cause <code>dmraid</code> to
+ break the mirror, and if you boot in read/write mode into only one
+ of the mirrored disks, it causes the disks to fall out of sync. No
+ symptoms arise, since the primary disk is reading and writing to
+ itself. But if you attempt to re-establish the mirror without
+ first synchronizing the disks, you could corrupt the data and have
+ to reinstall from scratch without a chance for recovery.
+ </para>
+ <para>
+ If the mirror is broken, you should be able to resync from within
+ the RAID chipset BIOS or by using the <code>dd</code> command.
+ Reinstallation is always an option.
+ </para>
+ </warning>
</listitem>
<listitem>
<para>
@@ -386,7 +267,9 @@
</para>
<itemizedlist>
<listitem>
-<screen>pci=off ide1=0x180,0x386 \n</screen>
+<screen>
+pci=off ide1=0x180,0x386
+</screen>
</listitem>
</itemizedlist>
<para>
@@ -429,54 +312,21 @@
<itemizedlist>
<listitem>
<para>
- Before you upgrade, back up the system completely. In
- particular, preserve
- <code>/etc</code>
- ,
- <code>/home</code>
- , and possibly
- <code>/opt</code>
- and
- <code>/usr/local</code>
- if customized packages are installed there. You may wish to
- use a multi-boot approach with a "clone" of the old
- installation on alternate partition(s) as a fallback. In
- that case, creating alternate boot media such as GRUB boot
- floppy.
- </para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>System Configuration
- Backups</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Backups of configurations in
- <code>/etc</code>
- are also useful in reconstructing system settings
- after a fresh installation.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ Before you upgrade, back up the system completely. In particular,
+ preserve <code>/etc</code> , <code>/home</code> , and possibly
+ <code>/opt</code> and <code>/usr/local</code> if customized packages
+ are installed there. You may wish to use a multi-boot approach with
+ a "clone" of the old installation on alternate partition(s) as a
+ fallback. In that case, creating alternate boot media such as GRUB
+ boot floppy.
+ </para>
+ <note>
+ <title>System Configuration Backups</title>
+ <para>
+ Backups of configurations in <code>/etc</code> are also useful in
+ reconstructing system settings after a fresh installation.
+ </para>
+ </note>
</listitem>
<listitem>
<para>
@@ -484,7 +334,9 @@
</para>
<itemizedlist>
<listitem>
-<screen>rpm -qa --last > RPMS_by_Install_Time.txt \n</screen>
+<screen>
+rpm -qa --last > RPMS_by_Install_Time.txt
+</screen>
</listitem>
</itemizedlist>
<para>
Index: Java.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Java.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Java.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Java.xml 12 Apr 2006 13:34:18 -0000 1.2
@@ -7,7 +7,7 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Java">
<title>Java and java-gcj-compat</title>
<para>
@@ -17,50 +17,22 @@
programs that are written in the Java programming language.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/rightsidebar/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Fedora Core Does Not Include
- Java</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- Java is a trademark of Sun Microsystems. is an entirely
- free software stack that is
- <emphasis role='strong'>not</emphasis> Java, but may run
- Java software.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <note>
+ <title>Fedora Core Does Not Include Java</title>
+ <para>
+ Java is a trademark of Sun Microsystems. is an entirely free software
+ stack that is <emphasis role='strong'>not</emphasis> Java, but may run
+ Java software.
+ </para>
+ </note>
<para>
- The 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 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.
</para>
<para>
@@ -77,44 +49,16 @@
for more information on the free Java environment in Fedora.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Include location and version
- information in bug reports</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- When making a bug report, be sure to include the output
- from these commands:
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- <code> which java && java -version && which javac && javac -version </code>
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <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>
+<screen>
+which java && java -version && which javac && javac -version
+</screen>
+ </tip>
<section>
<title>Handling Java and Java-like Packages</title>
@@ -132,21 +76,14 @@
</para>
<para>
- Once installed properly, the
- <code>root</code>
- user should be able to switch between
- <code>java</code>
- and
- <code>javac</code>
- implementations using the
- <code>alternatives</code>
- command:
+ Once installed properly, the <code>root</code> user should be able to
+ switch between <code>java</code> and <code>javac</code> implementations
+ using the <code>alternatives</code> command:
</para>
-
- <itemizedlist>
- <listitem>\n<screen>alternatives --config java \nalternatives --config javac</screen>
- </listitem>
- </itemizedlist>
+<screen>
+alternatives --config java
+alternatives --config javac
+</screen>
</section>
<section>
@@ -169,39 +106,14 @@
provides.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/rightsidebar/img/alert.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>/!\</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Mixing Packages from Fedora
- and JPackage</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <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>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <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>
</section>
</section>
</article>
Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/en_US/Kernel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Kernel.xml 10 Apr 2006 17:22:58 -0000 1.1
+++ Kernel.xml 12 Apr 2006 13:34:18 -0000 1.2
@@ -7,12 +7,12 @@
<title>Temp</title>
</articleinfo>
- <section>
+ <section id="sn-Kernel">
<title>Linux Kernel</title>
<para>
This section covers changes and important information regarding
- the kernel in Fedora Core .
+ the kernel in Fedora Core 5.
</para>
<section>
@@ -35,8 +35,9 @@
To obtain a list of these patches, download the source RPM
package and run the following command against it:
</para>
- \n
-<screen>rpm -qpl kernel-<version>.src.rpm\n</screen>
+<screen>
+rpm -qpl kernel-<version>.src.rpm
+</screen>
</section>
<section>
@@ -46,8 +47,9 @@
To retrieve a log of changes to the package, run the following
command:
</para>
- \n
-<screen>rpm -q --changelog kernel-<version>\n</screen>
+<screen>
+rpm -q --changelog kernel-<version>
+</screen>
<para>
If you need a user friendly version of the changelog, refer to
<ulink url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.kernelnewbies.org/LinuxChanges</ulink>.
@@ -114,71 +116,28 @@
<code>/usr/src/kernels/<version>-[xen0|xenU|kdump]-<arch>/</code>
tree. Use the following command:
</para>
- \n
-<screen>su -c 'yum install kernel-{xen0,xenU,kdump}-devel'\n</screen>
+<screen>
+su -c 'yum install kernel-{xen0,xenU,kdump}-devel'
+</screen>
<para>
Select one or more of these flavors, separated by commas and no
spaces, as appropriate. Enter the root password when prompted.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>x86_64 Default Kernel Provides
- SMP</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- There is no separate SMP kernel available for the
- x86_64 architecture in Fedora Core .
- </para>
- </td>
- </tr>
- </table>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>PowerPC Kernel
- Support</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- There is no support for Xen or kdump for the PowerPC
- architecture in Fedora Core .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <title>x86_64 Default Kernel Provides SMP</title>
+ <para>
+ There is no separate SMP kernel available for the x86_64 architecture
+ in Fedora Core 5.
+ </para>
+ </tip>
+ <tip>
+ <title>PowerPC Kernel Support</title>
+ <para>
+ There is no support for Xen or kdump for the PowerPC architecture in
+ Fedora Core 5.
+ </para>
+ </tip>
</section>
<section>
@@ -233,12 +192,11 @@
Core packages. Install the appropriate kernel sources, as shown
earlier, and then run the following command:
</para>
- \n
-<screen>su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux'\n</screen>
+<screen>
+su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux'
+</screen>
<para>
- Enter the
- <code>root</code>
- password when prompted.
+ Enter the <code>root</code> password when prompted.
</para>
</section>
@@ -252,42 +210,15 @@
available, as described in this kernel flavors section.
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
- </imageobject>
- <textobject>
- <phrase>{i}</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Instructions Refer to Current
- Kernel</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <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:
- <code>uname -r</code>
- .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <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: <code>uname -r</code> .
+ </para>
+ </note>
<para>
Users who require access to Fedora Core original kernel sources
@@ -296,79 +227,46 @@
steps:
</para>
- <itemizedlist>
- <listitem>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase><!></phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Do Not Build Packages as
- Super-user</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <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
- <code>/usr/src/linux</code>
- in their kernel instructions. If you use these
- instructions, simply substitute
- <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version></code>
- .
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <caution>
+ <title>Do Not Build Packages as Super-user (root)</title>
+ <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 <code>/usr/src/linux</code> in their kernel instructions. If
+ you use these instructions, simply substitute
+ <code>~/rpmbuild/BUILD/kernel-<version>/linux-<version></code> .
+ </para>
+ </caution>
<orderedlist numeration='arabic'>
<listitem>
<para>
Prepare a RPM package building environment in your home
directory. Run the following commands:
</para>
- <itemizedlist>
- <listitem>\n<screen>su -c 'yum install fedora-rpmdevtools yum-utils'\nfedora-buildrpmtree\n</screen>
+<screen>
+su -c 'yum install fedora-rpmdevtools yum-utils'
+fedora-buildrpmtree
+</screen>
<para>
Enter the
<code>root</code>
password when prompted.
</para>
- </listitem>
- </itemizedlist>
+
+
</listitem>
<listitem>
<para>
- Enable the appropriate
- <code>source</code>
- repository definition. In the case of the kernel released
- with Fedora Core 5, enable
- <code>core-source</code>
- by editing the file
- <code>/etc/yum.repos.d/fedora-core.repo</code>
- , setting the option
- <code>enabled=1</code>
- . In the case of update or testing kernels, enable the
- <code>source</code>
- definitions in
- <code>/etc/yum.repos.d/fedora-updates.repo</code>
- or
- <code>/etc/yum.repos.d/fedora-updates-testing.repo</code>
- as appropriate.
+ Enable the appropriate <code>source</code> repository definition. In
+ the case of the kernel released with Fedora Core 5, enable
+ <code>core-source</code> by editing the file
+ <code>/etc/yum.repos.d/fedora-core.repo</code>, setting the option
+ <code>enabled=1</code>. In the case of update or testing kernels,
+ enable the <code>source</code> definitions in
+ <code>/etc/yum.repos.d/fedora-updates.repo</code> or
+ <code>/etc/yum.repos.d/fedora-updates-testing.repo</code> as
+ appropriate.
</para>
</listitem>
<listitem>
@@ -377,15 +275,12 @@
<code>kernel-<version>.src.rpm</code>
file:
</para>
- <itemizedlist>
- <listitem>\n<screen>yumdownloader --source kernel\n</screen>
- <para>
- Enter the
- <code>root</code>
- password when prompted.
- </para>
- </listitem>
- </itemizedlist>
+<screen>
+yumdownloader --source kernel
+</screen>
+ <para>
+ Enter the <code>root</code> password when prompted.
+ </para>
</listitem>
<listitem>
<para>
@@ -393,60 +288,35 @@
<code>kernel-<version>.src.rpm</code>
using the command:
</para>
- <itemizedlist>
- <listitem>\n<screen>rpm -Uvh kernel-<version>.src.rpm`\n</screen>
+<screen>
+rpm -Uvh kernel-<version>.src.rpm
+</screen>
<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.
+ <code>${HOME}/rpmbuild/SOURCES</code> and
+ <code>${HOME}/rpmbuild/SPECS</code>, where <code>${HOME}</code>
+ is your home directory.
</para>
- <table>
- <caption/>
- <tr>
- <td>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>(!)</phrase>
- </textobject>
- </inlinemediaobject>
- <emphasis role='strong'>Space Required</emphasis>
- </para>
- </td>
- </tr>
- <tr>
- <td>
- <para>
- The full kernel building process may require
- several gigabytes of extra space on the file
- system containing your home directory.
- </para>
- </td>
- </tr>
- </table>
- </listitem>
- </itemizedlist>
+ <tip>
+ <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>
+ </tip>
</listitem>
<listitem>
<para>
Prepare the kernel sources using the commands:
</para>
- <itemizedlist>
- <listitem>\n<screen>cd ~/rpmbuild/SPECS\nrpmbuild -bp --target $(uname -m) kernel-2.6.spec\n</screen>
- <para>
- The kernel source tree is located in the
- <code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code>
- directory.
- </para>
- </listitem>
- </itemizedlist>
+<screen>
+cd ~/rpmbuild/SPECS
+rpmbuild -bp --target $(uname -m) kernel-2.6.spec
+</screen>
+ <para>
+ The kernel source tree is located in the
+ <code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code> directory.
+ </para>
</listitem>
<listitem>
<para>
@@ -459,69 +329,54 @@
. Issue the following command to place the desired
configuration file in the proper place for building:
</para>
- <itemizedlist>
- <listitem>\n<screen>cp configs/<desired-config-file> .config\n</screen>
- <para>
- You can also find the
- <code>.config</code>
- file that matches your current kernel configuration in
- the
- <code>/lib/modules/<version>/build/.config</code>
- file.
- </para>
- </listitem>
- </itemizedlist>
+<screen>
+cp configs/<desired-config-file> .config
+</screen>
+ <para>
+ You can also find the <code>.config</code> file that matches your
+ current kernel configuration in the
+ <code>/lib/modules/<version>/build/.config</code> file.
+ </para>
</listitem>
<listitem>
<para>
- Every kernel gets a name based on its version number. This
- is the value the
- <code>uname -r</code>
- command displays. The kernel name is defined by the first
- four lines of the kernel
- <code>Makefile</code>
- . The
- <code>Makefile</code>
- has been changed to generate a kernel with a
- <emphasis>different</emphasis> name from that of the running
- kernel. To be accepted by the running kernel, a module must
- be 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.15-1.1948_FC5</code>
- , change the
- <code>EXTRAVERSION</code>
- definition from this:
- </para>\n<screen>EXTRAVERSION = -prep\n</screen>
- <para>
- to this:
- </para>\n<screen>EXTRAVERSION = -1.1948_FC5\n</screen>
- <para>
- That is, substitute everything from the final dash
- onward.
- </para>
- </listitem>
- </itemizedlist>
+ Every kernel gets a name based on its version number. This is the
+ value the <code>uname -r</code> command displays. The kernel name is
+ defined by the first four lines of the kernel <code>Makefile</code>.
+ The <code>Makefile</code> has been changed to generate a kernel with
+ a <emphasis>different</emphasis> name from that of the running
+ kernel. To be accepted by the running kernel, a module must be
+ compiled for a kernel with the correct name. To do this, you must
+ edit the kernel <code>Makefile</code>.
+ </para>
+ <para>
+ For example, if the <code>uname -r</code> returns the string
+ <code>2.6.15-1.1948_FC5</code> , change the
+ <code>EXTRAVERSION</code> definition from this:
+ </para>
+<screen>
+EXTRAVERSION = -prep
+</screen>
+ <para>
+ to this:
+ </para>
+<screen>
+EXTRAVERSION = -1.1948_FC5
+</screen>
+ <para>
+ That is, substitute everything from the final dash onward.
+ </para>
</listitem>
<listitem>
<para>
Run the following command:
</para>
- <itemizedlist>
- <listitem>\n<screen>make oldconfig\n</screen>
- <para>
- You may then proceed as usual.
- </para>
- </listitem>
- </itemizedlist>
+<screen>
+make oldconfig
+</screen>
+ <para>
+ You may then proceed as usual.
+ </para>
</listitem>
</orderedlist>
</section>
@@ -546,25 +401,26 @@
<code>yum</code>
.
</para>
- \n
-<screen>su -c 'yum install kernel-devel'\n</screen>
+<screen>
+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:
+ </para>
+<screen>
+obj-m := foo.o
+
+KDIR := /lib/modules/$(shell uname -r)/build
+PWD := $(shell pwd)
+
+default:
+ $(MAKE) -C $(KDIR) M=$(PWD) modules
+</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:
- </para>
- \n
-<screen>obj-m := foo.o\n\nKDIR := /lib/modules/$(shell uname -r)/build\nPWD := $(shell pwd)\n\ndefault:\n$(MAKE) -C $(KDIR) M=$(PWD) modules\n</screen>
- <para>
- Issue the
- <code>make</code>
- command to build the
- <code>foo.ko</code>
- module.
+ Issue the <code>make</code> command to build the <code>foo.ko</code>
+ module.
</para>
</section>
@@ -607,7 +463,7 @@
<td>
<para>
The GFS kernel modules are not built for the PowerPC
- architecture in Fedora Core .
+ architecture in Fedora Core 5.
</para>
</td>
</tr>
More information about the docs-commits
mailing list