release-notes/en Virtualization.xml, NONE, 1.1 ArchSpecific.xml, 1.1, 1.2 ArchSpecificPPC.xml, 1.1, 1.2 ArchSpecificx86.xml, 1.1, 1.2 ArchSpecificx86_64.xml, 1.1, 1.2 BackwardsCompatibility.xml, 1.1, 1.2 Colophon.xml, 1.1, 1.2 DatabaseServers.xml, 1.1, 1.2 Desktop.xml, 1.1, 1.2 DevelTools.xml, 1.2, 1.3 DevelToolsGCC.xml, 1.1, 1.2 Entertainment.xml, 1.1, 1.2 Extras.xml, 1.1, 1.2 Feedback.xml, 1.1, 1.2 FileServers.xml, 1.1, 1.2 FileSystems.xml, 1.1, 1.2 I18n.xml, 1.1, 1.2 Installer.xml, 1.1, 1.2 Java.xml, 1.1, 1.2 Kernel.xml, 1.1, 1.2 Legacy.xml, 1.1, 1.2 Multimedia.xml, 1.1, 1.2 Networking.xml, 1.1, 1.2 OverView.xml, 1.1, 1.2 PackageChanges.xml, 1.1, 1.2 PackageNotes.xml, 1.2, 1.3 Printing.xml, 1.1, 1.2 ProjectOverview.xml, 1.1, 1.2 Samba.xml, 1.2, 1.3 Security.xml, 1.1, 1.2 SecuritySELinux.xml, 1.1, 1.2 ServerTools.xml, 1.1, 1.2 SystemDaemons.xml, 1.1, 1.2 WebServers.xml, 1.1, 1.2 Welcome.xml, 1.1, 1.2 Xorg.xml, 1.1, 1.2 PackageNotesJava.xml, 1.1, NONE
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Tue Feb 28 17:25:33 UTC 2006
Author: kwade
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13626
Modified Files:
ArchSpecific.xml ArchSpecificPPC.xml ArchSpecificx86.xml
ArchSpecificx86_64.xml BackwardsCompatibility.xml Colophon.xml
DatabaseServers.xml Desktop.xml DevelTools.xml
DevelToolsGCC.xml Entertainment.xml Extras.xml Feedback.xml
FileServers.xml FileSystems.xml I18n.xml Installer.xml
Java.xml Kernel.xml Legacy.xml Multimedia.xml Networking.xml
OverView.xml PackageChanges.xml PackageNotes.xml Printing.xml
ProjectOverview.xml Samba.xml Security.xml SecuritySELinux.xml
ServerTools.xml SystemDaemons.xml WebServers.xml Welcome.xml
Xorg.xml
Added Files:
Virtualization.xml
Removed Files:
PackageNotesJava.xml
Log Message:
This is the FC 5 GOLD content from the Wiki, fresh off the press. I'll tag it with release-notes-FC-5-GOLD-for-ISO as well as a trans tag.
--- NEW FILE Virtualization.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Virtualization</title>
<para>Virtualization in Fedora Core is based on <emphasis role='strong'>Xen</emphasis>. Xen 3.0 is integrated within Fedora Core in the installer. Refer to <ulink url='http://fedoraproject.org/wiki/Tools/Xen'>http://fedoraproject.org/wiki/Tools/Xen</ulink> for more information about Xen. </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'>No PowerPC Support</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Xen is not supported on the PowerPC architecture in Fedora Core . </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</section>
</article>
Index: ArchSpecific.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ArchSpecific.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecific.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ArchSpecific.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,18 +1,17 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ArchSpecific">
- <title>Archictecture Specific</title>
+ <section>
+ <title>Docs/Beats/ArchSpecific</title>
<para>This section provides notes that are specific to the supported hardware architectures of Fedora Core. </para>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="ArchSpecificPPC.xml" xpointer="element(sn-ArchSpecificPPC)" />
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="ArchSpecificx86.xml" xpointer="element(sn-ArchSpecificx86)" />
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="ArchSpecificx86_64.xml"
- xpointer="element(sn-ArchSpecificx86_64)"/>
+ <para>
+ </para>
+ <para>
+ </para>
+ <para>
+ </para>
</section>
</article>
Index: ArchSpecificPPC.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ArchSpecificPPC.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificPPC.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ArchSpecificPPC.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,107 +1,84 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ArchSpecificPPC">
+ <section>
<title>PPC Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the PPC hardware platform. </para>
<section>
<title>PPC Hardware Requirements</title>
- <para>This section lists the minimum PowerPC (PPC) hardware needed to install Fedora Core 4. </para>
- <itemizedlist>
- <listitem>
- <para> Minimum: PowerPC G3 / POWER4 </para>
- </listitem>
- <listitem>
- <para> Fedora Core 5 supports only the “New World†generation of Apple Power Macintosh, shipped circa 1999 onwards. </para>
- </listitem>
- <listitem>
- <para> Fedora Core also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines. </para>
- </listitem>
- <listitem>
- <para> Recommended for text-mode: 233 MHz G3 or better, 64MiB RAM. </para>
- </listitem>
- <listitem>
- <para> Recommended for graphical: 400 MHz G3 or better, 128MiB RAM. </para>
- </listitem>
- </itemizedlist>
<section>
- <title>Hard Disk Space Requirements</title>
- <para>This section lists the disk space required to install Fedora Core . </para>
- <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
- <para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
- <para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
- </section>
- </section>
- <section>
- <title>PPC Installation Notes</title>
+ <title>Processor and Memory</title>
<itemizedlist>
<listitem>
- <para>
- <inlinemediaobject>
- <imageobject>
- <imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
- </imageobject>
- <textobject>
- <phrase>/!\</phrase>
- </textobject>
- </inlinemediaobject> Currently FC5 Test Release CD 1 and Rescue ISOs do not boot on Mac hardware. See below on booting using boot.iso. </para>
+ <para> Minimum CPU: PowerPC G3 / POWER4 </para>
+ </listitem>
+ <listitem>
+ <para> Fedora Core supports only the “New World†generation of Apple Power Macintosh, shipped from circa 1999 onward. </para>
</listitem>
- </itemizedlist>
- <itemizedlist>
<listitem>
- <para>The DVD or first CD of the installation set of Fedora Core is set to be bootable on supported hardware. In addition, a bootable CD images can be found in the images/ directory of the DVD or first CD. These will behave differently according to the hardware: </para>
+ <para> Fedora Core also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines. </para>
</listitem>
<listitem>
+ <para> Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM. </para>
+ </listitem>
+ <listitem>
+ <para> Recommended for graphical: 400 MHz G3 or better, 256MiB RAM. </para>
+ </listitem>
+ </itemizedlist>
+ <section>
+ <title>Hard Disk Space Requirements</title>
+ <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after installation is complete. However, additional disk space is required during installation to support the installation environment. This additional disk space corresponds to the size of <code>/Fedora/base/stage2.img</code> (on Installtion Disc 1) plus the size of the files in <code>/var/lib/rpm</code> on the installed system. </para>
+ <para>In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space. </para>
+ <para>Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
+ </section>
+ </section>
+ <section>
+ <title>The Apple keyboard</title>
+ <para>The <code>Option</code> key on Apple systems is equivalent to the <code>Alt</code> key on the PC. Where documentation and the installer refer to the <code>Alt</code> key, use the <code>Option</code> key. For some key combinations you may need to use the <code>Option</code> key in conjunction with the <code>Fn</code> key, such as <code>Option</code>-<code>Fn</code>-<code>F3</code> to switch to virtual terminal tty3. </para>
+ </section>
+ <section>
+ <title>PPC Installation Notes</title>
+ <para>Fedora Core Installation Disc 1 is bootable on supported hardware. In addition, a bootable CD image appears in the <code>images/</code> directory of this disc. These images will behave differently according to your system hardware: </para>
+ <itemizedlist>
+ <listitem>
<para> Apple Macintosh </para>
+ <para>The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. </para>
+ <para>The default <code>gnome-power-manager</code> package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the <code>apmud</code> package in Fedora Extras. Following installation, you can install <code>apmud</code> with the following command: </para>
<itemizedlist>
<listitem>
- <para>The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the apmud package, which is in Fedora Extras. Fedora Extras for Fedora Core is configured by default for yum. Following installation, apmud can be installed by running yum install apmud. </para>
+ <screen>su -c 'yum install apmud' </screen>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> 64-bit IBM eServer pSeries (POWER4/POWER5) </para>
- <itemizedlist>
- <listitem>
- <para>After using Open<emphasis role='strong'/>Firmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer. </para>
- </listitem>
- </itemizedlist>
+ <para>After using Open<emphasis role='strong'/>Firmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer. </para>
</listitem>
<listitem>
<para> 32-bit CHRP (IBM RS/6000 and others) </para>
- <itemizedlist>
- <listitem>
- <para>After using Open<emphasis role='strong'/>Firmware to boot the CD, select the 'linux32' boot image at the 'boot:' prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work. </para>
- </listitem>
- </itemizedlist>
+ <para>After using Open<emphasis role='strong'/>Firmware to boot the CD, select the <code>linux32</code> boot image at the <code>boot:</code> prompt to start the 32-bit installer. Otherwise, the 64-bit installer starts, which does not work. </para>
</listitem>
<listitem>
<para> Genesi Pegasos II </para>
+ <para>At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, you can use the network boot image. At the Open<emphasis role='strong'/>Firmware prompt, enter the command: </para>
<itemizedlist>
<listitem>
- <para>At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the Open<emphasis role='strong'/>Firmware prompt, enter the command: </para>
- <itemizedlist>
- <listitem>
- <screen>boot cd: /images/netboot/ppc32.img </screen>
- </listitem>
- </itemizedlist>
- <para>You also need to configure Open<emphasis role='strong'/>Firmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, you need to set the boot-device and boot-file environment variables appropriately. </para>
+ <screen>boot cd: /images/netboot/ppc32.img </screen>
</listitem>
</itemizedlist>
+ <para>You must also configure Open<emphasis role='strong'/>Firmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, set the <code>boot-device</code> and <code>boot-file</code> environment variables appropriately. </para>
</listitem>
<listitem>
<para> Network booting </para>
- <itemizedlist>
- <listitem>
- <para>There are combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the install tree. These are intended for network booting with TFTP, but can be used in many ways. </para>
- <para>yaboot supports tftp booting for IBM eServer pSeries and Apple Macintosh, the use of yaboot is encouraged over the netboot images. </para>
- </listitem>
- </itemizedlist>
+ <para>You can find combined images containing the installer kernel and ramdisk in the <code>images/netboot/</code> directory of the installation tree. These are intended for network booting with TFTP, but can be used in many ways. </para>
+ <para>
+ <code>yaboot</code> supports TFTP booting for IBM eServer pSeries and Apple Macintosh. The Fedora Project encourages the use of <code>yaboot</code> over the <code>netboot</code> images. </para>
</listitem>
</itemizedlist>
</section>
</section>
+ </section>
</article>
Index: ArchSpecificx86.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ArchSpecificx86.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificx86.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ArchSpecificx86.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,23 +1,21 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ArchSpecificx86">
+ <section>
<title>x86 Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the x86 hardware platform. </para>
<section>
<title>x86 Hardware Requirements</title>
- <para>The following information represents the minimum hardware requirements necessary to successfully install Fedora Core . </para>
- <para>The compatibility/availability of other hardware components (such as video and network cards) may be required for specific installation modes and/or post-installation usage. </para>
+ <para>In order to use specific features of Fedora Core during or after installation, you may need to know details of other hardware components such as video and network cards. </para>
<section>
- <title>CPU Requirements</title>
- <para>This section lists the CPU specifications required by Fedora Core . </para>
- <para>The following CPU specifications are stated in terms of Intel processors. Other processors (notably, offerings from AMD, Cyrix, and VIA) that are compatible with and equivalent to the following Intel processors may also be used with Fedora Core. </para>
+ <title>Processor and Memory Requirements</title>
+ <para>The following CPU specifications are stated in terms of Intel processors. Other processors, such as those from AMD, Cyrix, and VIA that are compatible with and equivalent to the following Intel processors, may also be used with Fedora Core. </para>
<itemizedlist>
<listitem>
- <para> Minimum: Pentium-class — Fedora Core is optimized for Pentium 4 CPUs, but also supports earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III, and including AMD and VIA variants). This approach has been taken because Pentium-class optimizations actually result in reduced performance for non-Pentium-class processors, and Pentium 4 scheduling is sufficiently different (while making up the bulk of today's processors) to warrant this change. </para>
+ <para> Minimum: Pentium-class — Fedora Core is optimized for Pentium 4 CPUs, but also supports earlier CPUs such as Pentium, Pentium Pro, Pentium II, Pentium III, and compatible AMD and VIA processors. Fedora takes this approach because Pentium-class optimizations actually result in reduced performance for non-Pentium class processors. In addition, scheduling for Pentium 4 processors, which make up the bulk of today's processors, is sufficiently different to warrant this change. </para>
</listitem>
<listitem>
<para> Recommended for text-mode: 200 MHz Pentium-class or better </para>
@@ -31,35 +29,23 @@
<listitem>
<para> Intel processors with Intel® Extended Memory 64 Technology (Intel® EM64T) </para>
</listitem>
+ <listitem>
+ <para> Minimum RAM for text-mode: 128MiB </para>
+ </listitem>
+ <listitem>
+ <para> Minimum RAM for graphical: 192MiB </para>
+ </listitem>
+ <listitem>
+ <para> Recommended for graphical: 256MiB </para>
+ </listitem>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
- <para>This section lists the disk space required to install Fedora Core . </para>
- <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
- <para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
- <para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
- </section>
- <section>
- <title>Memory Requirements</title>
- <para>This section lists the memory required to install Fedora Core . </para>
- <para>This list is for 32-bit x86 systems: </para>
- <itemizedlist>
- <listitem>
- <para> Minimum for text-mode: 64MB </para>
- </listitem>
- <listitem>
- <para> Minimum for graphical: 192MB </para>
- </listitem>
- <listitem>
- <para> Recommended for graphical: 256MB </para>
- </listitem>
- </itemizedlist>
+ <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of <code>/Fedora/base/stage2.img</code> on Installation Disc 1 plus the size of the files in <code>/var/lib/rpm</code> on the installed system. </para>
+ <para>In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space. </para>
+ <para>Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
</section>
</section>
</section>
- <section>
- <title>x86 Installation Notes</title>
- <para>Installer package screen selection interface is being redesigned in the Fedora development version. Fedora Core does not provide an option to select the installation type such as Personal Desktop, Workstation, Server and custom. </para>
- </section>
</section>
</article>
Index: ArchSpecificx86_64.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ArchSpecificx86_64.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificx86_64.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ArchSpecificx86_64.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,43 +1,54 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ArchSpecificx86_64">
+ <section>
<title>x86_64 Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the x86_64 hardware platform. </para>
<section>
<title>x86_64 Hardware Requirements</title>
- <para>The following information represents the minimum hardware requirements necessary to successfully install Fedora Core . </para>
- <para>The compatibility/availability of other hardware components (such as video and network cards) may be required for specific installation modes and/or post-installation usage. </para>
+ <para>In order to use specific features of Fedora Core during or after installation, you may need to know details of other hardware components such as video and network cards. </para>
<section>
- <title>Hard Disk Space Requirements</title>
- <para>This section lists the disk space required to install Fedora Core . </para>
- <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
- <para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
- <para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
+ <title>Memory Requirements</title>
+ <para>This list is for 64-bit x86_64 systems: </para>
+ <itemizedlist>
+ <listitem>
+ <para> Minimum RAM for text-mode: 128MiB </para>
+ </listitem>
+ <listitem>
+ <para> Minimum RAM for graphical: 256MiB </para>
+ </listitem>
+ <listitem>
+ <para> Recommended RAM for graphical: 512MiB </para>
+ </listitem>
+ </itemizedlist>
<section>
- <title>Memory Requirements</title>
- <para>This section lists the memory required to install Fedora Core . </para>
- <para>This list is for 64-bit x86_64 systems: </para>
- <itemizedlist>
- <listitem>
- <para> Minimum for text-mode: 128MB </para>
- </listitem>
- <listitem>
- <para> Minimum for graphical: 256MB </para>
- </listitem>
- <listitem>
- <para> Recommended for graphical: 512MB </para>
- </listitem>
- </itemizedlist>
+ <title>Hard Disk Space Requirements</title>
+ <para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of <code>/Fedora/base/stage2.img</code> on Installation Disc 1 plus the size of the files in <code>/var/lib/rpm</code> on the installed system. </para>
+ <para>In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space. </para>
+ <para>Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
</section>
</section>
- </section>
<section>
- <title>x86_64 Installation Notes</title>
- <para>No differences installing for x86_64. </para>
+ <title>RPM Multiarch Support on x86_64</title>
+ <para>
+ <emphasis role='strong'>RPM</emphasis> supports parallel installation of multiple architectures of the same package. A default package listing such as <code>rpm -qa</code> might appear to include duplicate packages, since the architecture is not displayed. Instead, use the <code>repoquery</code> command, part of the <code>yum-utils</code> package in Fedora Extras, which displays architecture by default. To install <code>yum-utils</code>, run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install yum-utils' </screen>
+ </listitem>
+ </itemizedlist>
+ <para>To list all packages with their architecture using <code>rpm</code>, run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n" </screen>
+ <para>
+ </para>
+ </listitem>
+ </itemizedlist>
</section>
</section>
+ </section>
</article>
Index: BackwardsCompatibility.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/BackwardsCompatibility.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- BackwardsCompatibility.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ BackwardsCompatibility.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,12 +1,20 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
- <title>Backwards Compatibility</title>
+ <title>Temp</title>
</articleinfo>
- <section id="sn-BackwardsCompatibility">
+ <section>
+ <title>Docs/Beats/BackwardsCompatibility</title>
+ <section>
<title>Backwards Compatibility</title>
- <para>Fedora includes several system libraries and software for compatibility with older software. These software are part of the "Legacy Software Development" group which are not installed by default. Users who require this functionality can select this group during installation or run the following the command post-installation. </para>
- <screen>yum groupinstall "Legacy Software Development"</screen>
+ <para>Fedora Core provides legacy system libraries for compatibility with older software. This software is part of the <emphasis role='strong'>Legacy Software Development</emphasis> group, which is not installed by default. Users who require this functionality may select this group either during installation, or after the installation process is complete. To install the package group on a Fedora system, use <emphasis>Applications=>Add/Remove Software</emphasis>, <emphasis role='strong'>Pirut</emphasis> or enter the following command in a terminal window: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum groupinstall "Legacy Software Development"'</screen>
+ </listitem>
+ </itemizedlist>
+ <para>Enter the password for the <code>root</code> account when prompted. </para>
+ </section>
</section>
</article>
Index: Colophon.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Colophon.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Colophon.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Colophon.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,26 +1,47 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Colophon">
- <title>Colophon</title>
- <note>
- <title>Draft</title>
- <para>
- This is a draft, so it is incomplete and imperfect.
- </para>
- </note>
+ <section>
+ <title>Docs/Beats/Colophon</title>
+ <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'>Draft</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> This is a draft, so it is an incomplete and imperfect list. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
<section>
<title>About the Colophon</title>
- <para>As we use the term, colophon means: </para>
+ <para>As we use the term, a <emphasis>colophon</emphasis>: </para>
<itemizedlist>
<listitem>
- <para> A way to recognize contributors, while providing accountability. </para>
+ <para> recognizes contributors and provides accountability, and </para>
</listitem>
<listitem>
- <para> Explain tools and production methods. </para>
+ <para> explains tools and production methods. </para>
</listitem>
</itemizedlist>
</section>
@@ -29,94 +50,97 @@
<itemizedlist>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/AndrewMartynov'>Andrew Martynov</ulink> (translator, Russian) </para>
+ <ulink url='/AndrewMartynov'>AndrewMartynov</ulink> (translator, Russian) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/AnthonyGreen'>Anthony Green</ulink> (beat writer) </para>
+ <ulink url='/AnthonyGreen'>AnthonyGreen</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/BobJensen'>Bob Jensen</ulink> (beat writer) </para>
+ <ulink url='/BobJensen'>BobJensen</ulink> (beat writer, editor, co-publisher) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/DaveMalcolm'>Dave Malcolm</ulink> (beat writer) </para>
+ <ulink url='/DaveMalcolm'>DaveMalcolm</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/DavidWoodhouse'>David Woodhouse</ulink> (beat writer) </para>
+ <ulink url='/DavidWoodhouse'>DavidWoodhouse</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink
- url='http://fedoraproject.org/wiki/FrancescoTombolini'>Francesco Tombolini</ulink> (translator, Italian) </para>
+ <ulink url='/FrancescoTombolini'>FrancescoTombolini</ulink> (translator, Italian) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/GavinHenry'>Gavin Henry</ulink> (beat writer) </para>
+ <ulink url='/GavinHenry'>GavinHenry</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/JensPetersen'>Jens Petersen</ulink> (beat writer) </para>
+ <ulink url='/JensPetersen'>JensPetersen</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/JoeOrton'>Joe Orton</ulink> (beat writer) </para>
+ <ulink url='/JoeOrton'>JoeOrton</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/JoshBressers'>Josh Bressers</ulink> (beat writer) </para>
+ <ulink url='/JoshBressers'>JoshBressers</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/KarstenWade'>Karsten Wade</ulink> (beat writer, editor, publisher) </para>
+ <ulink url='/KarstenWade'>KarstenWade</ulink> (beat writer, editor, co-publisher) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/LuyaTshimbalanga'>Luya Tshimbalanga</ulink> (beat writer) </para>
+ <ulink url='/LuyaTshimbalanga'>LuyaTshimbalanga</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/PatrickBarnes'>Patrick Barnes</ulink> (beat writer, editor) </para>
+ <ulink url='/PatrickBarnes'>PatrickBarnes</ulink> (beat writer, editor) </para>
</listitem>
- <listitem>
- <para>
- <ulink url="http://fedoraproject.org/wiki/PaulWFrields">Paul W. Frields</ulink> (tools, editor) </para>
- </listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/RahulSundaram'>RahulSundaram</ulink> (beat writer, editor) </para>
+ <ulink url='/PaulWFrields'>PaulWFrields</ulink> (tools, editor) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/SekineTatsuo'>SekineTatsuo</ulink> (translator, Japanese) </para>
+ <ulink url='/RahulSundaram'>RahulSundaram</ulink> (beat writer, editor) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/SteveDickson'>SteveDickson</ulink> (beat writer) </para>
+ <ulink url='/SekineTatsuo'>SekineTatsuo</ulink> (translator, Japanese) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/StuartElliss'>StuartElliss</ulink> (editor) </para>
+ <ulink url='/SteveDickson'>SteveDickson</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/ThomasGraf'>ThomasGraf</ulink> (beat writer) </para>
+ <ulink url='/StuartEllis'>StuartEllis</ulink> (editor) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/TommyReynolds'>TommyReynolds</ulink> (tools) </para>
+ <ulink url='/ThomasGraf'>ThomasGraf</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/YoshinariTakaoka'>YoshinariTakaoka</ulink> (translator, tools) </para>
+ <ulink url='/TommyReynolds'>TommyReynolds</ulink> (tools) </para>
</listitem>
<listitem>
<para>
- <ulink url='http://fedoraproject.org/wiki/YuanYijun'>YuanYijun</ulink> (translator, Simplified Chinese) </para>
+ <ulink url='/YoshinariTakaoka'>YoshinariTakaoka</ulink> (translator, tools) </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url='/YuanYijun'>YuanYijun</ulink> (translator, Simplified Chinese) </para>
</listitem>
</itemizedlist>
</section>
+ <section>
+ <title>Production Methods</title>
+ <para>Beat writers produce the release notes directly on the Fedora Project Wiki. They collaborate with other subject matter experts during the test release phase of Fedora Core to explain important changes and enhancements. The editorial team ensures consistency and quality of the finished beats, and ports the Wiki material to <ulink url='/DocBook'>DocBook</ulink> XML in a revision control repository. At this point, the team of translators produces other language versions of the release notes, and then they become available to the general public as part of Fedora Core. The publication team also makes them, and subsequent errata, available via the Web. </para>
+ </section>
</section>
</article>
Index: DatabaseServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/DatabaseServers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DatabaseServers.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ DatabaseServers.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,16 +1,47 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-DatabaseServers">
- <title>Database Servers</title>
-<!-- <para>This page is a stub for content. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. </para>
- <para>Beat writers: this is where you want to fill in with instructions -->
-<!-- about how to post relevant information. Any questions that come up can -->
-<!-- be taken to a bugzilla report for discussion to resolution, or to -->
-<!-- fedora-docs-list for wider discussions. </para> -->
- <para><emphasis>No changes of note.</emphasis></para>
+ <section>
+ <title>Docs/Beats/DatabaseServers</title>
+ <section>
+ <title>MySQL</title>
+ <para>Fedora now provides <emphasis role='strong'>MySQL</emphasis> 5.0. For a list of the enhancements provided by this version, refer to <ulink url='http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html'>http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html</ulink>. </para>
+ <para>For more information on upgrading databases from previous releases of <emphasis role='strong'>MySQL</emphasis>, refer to the <emphasis role='strong'>MySQL</emphasis> web site at <ulink url='http://dev.mysql.com/doc/refman/5.0/en/upgrade.html'>http://dev.mysql.com/doc/refman/5.0/en/upgrade.html</ulink>. </para>
+ </section>
+ <section>
+ <title>PostgreSQL</title>
+ <para>This release of Fedora includes <emphasis role='strong'>PostgreSQL</emphasis> 8.1. For more information on this new version, refer to <ulink url='http://www.postgresql.org/docs/whatsnew/'>http://www.postgresql.org/docs/whatsnew/</ulink>. </para>
+ <itemizedlist>
+ <listitem>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/star_on.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>{*}</phrase>
+ </textobject>
+ </inlinemediaobject>
+ <emphasis role='strong'>Upgrading Databases</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Fedora Core 4 provided version 8.0 of PostgreSQL. If you upgrade an existing Fedora system with a PostgreSQL database, you must upgrade the database to access the data. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>To upgrade a database from a previous version of PostgreSQL, follow the procedure described at <ulink url='http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html'>http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html</ulink>. </para>
+ </section>
</section>
</article>
Index: Desktop.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Desktop.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Desktop.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Desktop.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,32 +1,52 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Desktop">
- <title>Desktop</title>
- <para>GNOME 2.13.2 and KDE 3.5 Release Candidate 2 has been included in Fedora Core 5 test 2. GNOME 2.14 (or a release candidate) is scheduled to be available as part of Fedora Core 5. </para>
- <para>The current test release has GNOME 2.12.1, together with some previews of technology from the forthcoming GNOME 2.14. Feedback on these packages is especially appreciated. </para>
- <itemizedlist>
- <listitem>
- <para> gnome-power-manager: GNOME Power Manager is a session daemon for the GNOME desktop environment that makes it easy to manage your laptop or desktop system. It takes advantage of HAL (which provides a hardware abstraction layer) and DBUS ( Inter Process Communication software) written and maintained by Fedora Core developers. </para>
- </listitem>
- <listitem>
- <para> gnome-screensaver: Provides a integrated user interface to screensavers and the lock screen dialog. </para>
- </listitem>
- <listitem>
- <para> memory optimizations in the fontconfig and shared-mime-info packages. These now use shared memory-mapped caches for this data. </para>
- </listitem>
- </itemizedlist>
- <para>GNOME 2.12 has removed the terminal option from the desktop context menu. nautilus-open-terminal in Fedora Extras repository provides a enhanced replacement for those who require it. You can install it using the following command. </para>
- <screen>yum install nautilus-open-terminal</screen>
- <para>Screensavers except the one providing a blank screen are not installed by default from Fedora Core 4 onwards. Many of the screensavers are found to be offensive or known to abruptly terminate the graphical interface, in particular some of the OpenGL animated ones provided within xscreensaver-gl-extras package. Some of them also provide a unexpected suprise to users. Users who need it can install it using the following command. </para>
- <screen>yum install xscreensaver-extras xscreensaver-gl-extras</screen>
- <note>
- <title>system-config-mouse Removed</title>
- <para>
-system-config-mouse configuration utility has been dropped from this release since synaptic and 3 button mouse configuration is being done automatically during installation and serial mice are not formally supported in Fedora Core anymore. </para>
- </note>
+ <section>
+ <title>Fedora Desktop</title>
+ <para>GNOME 2.14 (or a release candidate) and KDE 3.5.1 are included in Fedora Core . The following list includes notable changes to the desktop interface in this release. </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>gnome-power-manager</emphasis>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>The <emphasis role='strong'>GNOME Power Manager</emphasis> is a session daemon for the GNOME desktop environment that makes it easy to manage your laptop or desktop system. It takes advantage of HAL (which provides a hardware abstraction layer) and DBUS (Inter Process Communication software) written and maintained by Fedora Core developers. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>gnome-screensaver</emphasis>
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>The <emphasis role='strong'>GNOME Screensaver</emphasis> provides a integrated user interface to screensavers and the lock screen dialog. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para> Memory optimizations in the fontconfig and shared-mime-info packages. These now use shared memory-mapped caches for this data. </para>
+ </listitem>
+ <listitem>
+ <para> Starting with GNOME 2.12, the terminal option has been removed from the desktop context menu. The <code>nautilus-open-terminal</code> package in Fedora Extras provides a enhanced replacement for those who require it. You can install it with the following command. </para>
+ <itemizedlist>
+ <listitem>
+ <screen>yum install nautilus-open-terminal</screen>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para> In Fedora Core 5, only a small assortment of screensavers is installed by default. Some users find certain screensavers unpleasant, and other screensavers may abruptly terminate the graphical interface. This tends to happen more often with OpenGL animated screensavers provided within the <code>xscreensaver-gl-extras</code> package, when used with poorly-supported video hardware. To install these extra screensavers, run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>yum install xscreensaver-extras xscreensaver-gl-extras</screen>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
</section>
</article>
Index: DevelTools.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/DevelTools.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- DevelTools.xml 17 Feb 2006 00:49:51 -0000 1.2
+++ DevelTools.xml 28 Feb 2006 17:25:26 -0000 1.3
@@ -1,10 +1,10 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-DevelTools">
+ <section>
<title>Developer Tools</title>
<para>This section covers various developer tools. </para>
<para>
@@ -21,14 +21,12 @@
<title>Eclipse Development Environment</title>
<itemizedlist>
<listitem>
- <para> Eclipse 3.1M6 has been compiled as a native application. </para>
+ <para> Eclipse 3.1M6 is compiled as a native application. </para>
</listitem>
<listitem>
<para> The C Development Tool (CDT) has been included. </para>
</listitem>
</itemizedlist>
</section>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="DevelToolsGCC.xml" xpointer="element(sn-DevelToolsGCC)" />
</section>
</article>
Index: DevelToolsGCC.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/DevelToolsGCC.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DevelToolsGCC.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ DevelToolsGCC.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,26 +1,26 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-DevelToolsGCC">
+ <section>
<title>GCC Compiler Collection</title>
- <para>This release of Fedora has been built using GCC 4.1, which is included with the distribution. </para>
+ <para>This release of Fedora has been built with GCC 4.1 as the system compiler, which is included with the distribution. </para>
<section>
<title>Caveats</title>
<itemizedlist>
<listitem>
- <para> GDB 6.1 or newer is needed to debug binaries unless compiled using the <command>-fno-var-tracking</command> compilation option. </para>
+ <para> You need GDB 6.1 or newer to debug binaries, unless they are compiled using the <code>-fno-var-tracking</code> compilation option. </para>
</listitem>
<listitem>
- <para> The <command>-fwritable-strings</command> option is no longer accepted. </para>
+ <para> The <code>-fwritable-strings</code> option is no longer accepted. </para>
</listitem>
<listitem>
- <para> English-language diagnostic messages now use Unicode quotes; if you cannot read this, set your <command>LC_CTYPE</command> environment variable to <command>C</command> or change your terminal emulator. </para>
+ <para> English-language diagnostic messages now use Unicode quotes. If you cannot read this, set your <code>LC_CTYPE</code> environment variable to <code>C</code> or change your terminal emulator. </para>
</listitem>
<listitem>
- <para> The <command>specs</command> file is no longer installed on most systems. Ordinary users will not notice, but developers who need to alter the file can use the <command>-dumpspecs</command> option to generate the file for editing. </para>
+ <para> The <code>specs</code> file is no longer installed on most systems. Ordinary users will not notice, but developers who need to alter the file can use the <code>-dumpspecs</code> option to generate the file for editing. </para>
</listitem>
</itemizedlist>
<section>
@@ -38,13 +38,13 @@
<title>Language Extensions</title>
<itemizedlist>
<listitem>
- <para> A sentinel attribute has been added so that the compiler will now issue a warning if a function such as <command>execl(char *path, const char *arg, ...)</command>, which requires a NULL list terminator is missing the NULL. </para>
+ <para> The new sentinel attribute causes the compiler to issue a warning if a function such as <code>execl(char *path, const char *arg, ...)</code>, which requires a NULL list terminator, is missing the NULL. </para>
</listitem>
<listitem>
- <para> The <command>cast-as-lvalue</command>, <command>conditional-expression-as-lvalue</command>, and <command>compund-expression-as-lvalue</command> extensions have been removed. </para>
+ <para> The <code>cast-as-lvalue</code>, <code>conditional-expression-as-lvalue</code>, and <code>compund-expression-as-lvalue</code> extensions have been removed. </para>
</listitem>
<listitem>
- <para> The <command>#pragma pack()</command> semantics have been brought closer to those used by other compilers. </para>
+ <para> The <code>#pragma pack()</code> semantics are now closer to those used by other compilers. </para>
</listitem>
<listitem>
<para> Taking the address of a variable declared with the register modifier now generates an error instead of a warning. </para>
@@ -53,10 +53,10 @@
<para> Arrays of incomplete element types now generate an error. This implies no forward reference to structure definitions. </para>
</listitem>
<listitem>
- <para> The basic compiler, without any optimization (<command>-O0</command>), has been measured as much as 25% faster in real-world code. </para>
+ <para> The basic compiler, without any optimization (<code>-O0</code>), has been measured as much as 25% faster in real-world code. </para>
</listitem>
<listitem>
- <para> Libraries may now contain function-scope static variables in multi-threaded programs. The <command>-fno-threadsafe-statics</command> can be used by embedded developers to turn off this feature, but ordinary users should never do this. </para>
+ <para> Libraries may now contain function-scope static variables in multi-threaded programs. Embedded developers can use the <code>-fno-threadsafe-statics</code> to turn off this feature, but ordinary users should never do this. </para>
</listitem>
</itemizedlist>
</section>
Index: Entertainment.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Entertainment.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Entertainment.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Entertainment.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,16 +1,11 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Entertainment">
+ <section>
<title>Games and Entertainment</title>
- <para>Fedora Core and Fedora Extras provide a selection of games that cover a variety of genres. By default, Fedora Core includes a small package of games for GNOME (called <command>gnome-games</command>). For a list of other games that are available for installation through <command>yum</command>, open a terminal and enter the following command: </para>
- <screen>yum groupinfo "Games and Entertainment"</screen>
- <para>For help using <command>yum</command> to install the assorted game packages, refer to the guide available at: </para>
- <para>
- <ulink url='http://fedora.redhat.com/docs/yum/'>http://fedora.redhat.com/docs/yum/</ulink>
- </para>
+ <para>Fedora Core and Fedora Extras provide a selection of games that cover a variety of genres. By default, Fedora Core includes a small package of games for GNOME (called <code>gnome-games</code>). To install other games available from Fedora Core and Fedora Extras, select <emphasis>Applications</emphasis>><emphasis>Add/Remove Software</emphasis> from the main desktop menu. </para>
</section>
</article>
Index: Extras.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Extras.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Extras.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Extras.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,17 +1,143 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Extras">
- <title>Fedora Extras Repository</title>
- <para>Fedora Extras is part of the larger Fedora Project and is a volunteer-based community effort to create a repository of packages that compliment Fedora Core. The Fedora Extras repository is enabled by default. </para>
- <para>You can lean more about Fedora Extras from
- <ulink url='http://fedoraproject.org/wiki/Extras'>http://fedoraproject.org/wiki/Extras</ulink>.
- </para>
- <para>If you would like to install any software available from Fedora extras you can use yum. </para>
- <screen>yum install <packagename></screen>
- <para>Where <packagename> is the name of the package you want to install. For example, if you wanted to install the abiword package, the command <code>yum install abiword</code> automatically installs the package and all dependencies. </para>
+ <section>
+ <title>Fedora Extras</title>
+ <section>
+ <title>Using the Repository</title>
+ <para>Fedora Extras provides a repository of packages that complement Fedora Core. This volunteer-based community effort is part of the larger Fedora Project. </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'>Fedora Extras are Available by Default</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Fedora systems automatically use both the Fedora Core and Fedora Extras repositories to install and update software. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>To install software from either the Core or Extras repositories, choose <emphasis>Applications > Add/Remove Software</emphasis>. Enter the <code>root</code> password when prompted. Select the software you require from the list, and choose <emphasis>Apply</emphasis>. </para>
+ <para>Alternatively, you may install software with the <code>yum</code> command-line utility. For example, this command automatically installs the <code>abiword</code> package, and all of the dependencies that are required: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install abiword' </screen>
+ </listitem>
+ </itemizedlist>
+ <para>Enter the <code>root</code> password when prompted. </para>
+ </section>
+ <section>
+ <title>About Fedora Extras</title>
+ <para>As of the release of Fedora Core 5, there are approximately 2,000 packages in Fedora Extras, built from 1,350 source packages. The following list includes some popular and well-known applications that are maintained by community members in Fedora Extras: </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <code>abiword</code> - elegant word-processing application </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>balsa</code> - lightweight e-mail reader </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>bash-completion</code> - advanced command-line completion for power users </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>bluefish</code> - HTML editor </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>clamav</code> - open source anti-virus scanner for servers and desktops </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>fuse</code> - tool for attaching non-standard devices and network services as directories </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>fwbuilder</code> - graphical utility for building Linux and Cisco firewall rulesets </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>gaim-guifications</code> - enhancements to the Gaim Instant Messenger </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>gdesklets</code> - widgets for the GNOME desktop </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>gnumeric</code> - powerful spreadsheet application </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>inkscape</code> - illustration and vector drawing application </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>koffice</code> - complete office suite for the KDE desktop </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>mail-notification</code> - alerts you as new mail arrives </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>mediawiki</code> - the Wikipedia solution for collaborative websites </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>nautilus-open-terminal</code> - extension to the GNOME file manager </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>pan</code> - the Usenet news reader </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>revelation</code> - password management utility </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>scribus</code> - desktop publishing (DTP) application </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>xfce</code> - lightweight desktop environment </para>
+ </listitem>
+ <listitem>
+ <para>
+ <code>xmms</code> - the popular audio player </para>
+ </listitem>
+ <listitem>
+ <para> lots of Perl and Python tools and libraries </para>
+ </listitem>
+ <listitem>
+ <para> ...and much more! </para>
+ </listitem>
+ </itemizedlist>
+ <para>Is your favorite open source application missing from Fedora Extras? Package the application as an RPM, and submit it for review to Fedora Extras. After a successful review, import it to Extras and you can maintain it there. If you don't know how to create RPM packages, there are many other ways to get involved in Fedora Extras and help drive it forward. </para>
+ <para>To learn more about how to use Fedora Extras or how to get involved, refer to <ulink url='http://fedoraproject.org/wiki/Extras'>http://fedoraproject.org/wiki/Extras</ulink>. </para>
+ </section>
</section>
</article>
Index: Feedback.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Feedback.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Feedback.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Feedback.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,31 +1,54 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Feedback">
- <title>Feedback</title>
- <para>Thanks for your interest in helping us with the release notes by providing feedback. This section explains how you can give that feedback. </para>
- <section>
- <title>Release Notes Feedback Procedure</title>
- <para>If you feel that these release notes could be improved in some way, you can provide feedback directly to the beat writers. Here are several ways, in order of preference: </para>
- <itemizedlist>
- <listitem>
- <para> Edit content directly at <ulink url='/Docs/Beats'>Docs/Beats</ulink>
- </para>
- </listitem>
- <listitem>
- <para> Email <ulink url='mailto:relnotes at fedoraproject.org'>relnotes at fedoraproject.org</ulink>
- </para>
- </listitem>
- <listitem>
- <para> Fill out this <ulink url='http://tinyurl.com/8lryk'>pre-filled bug request template</ulink>
- </para>
- </listitem>
- </itemizedlist>
- <para>A <ulink url='/DocsProject/ReleaseNotes/Beats'>release note beat</ulink> is an area of the release notes that is the responsibility of one or more content contributors to oversee. </para>
- <para>Thank you (in advance) for your feedback! </para>
- </section>
+ <section>
+ <title>Providing Feedback for Release Notes</title>
+ <itemizedlist>
+ <listitem>
+ <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'>Feedback for Release Notes Only</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> This section concerns feedback on the release notes themselves. To provide feedback on Fedora software or other system elements, please refer to <ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>Thanks for your interest in giving feedback for these release notes. If you feel these release notes could be improved in any way, you can provide your feedback directly to the beat writers. Here are several ways to do so, in order of preference: </para>
+ <itemizedlist>
+ <listitem>
+ <para> Edit content directly at <ulink url='http://fedoraproject.org/wiki/Docs/Beats'>http://fedoraproject.org/wiki/Docs/Beats</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Fill out a bug request using this template: <ulink url='http://tinyurl.com/8lryk'>http://tinyurl.com/8lryk</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Email <ulink url='mailto:relnotes at fedoraproject.org'>relnotes at fedoraproject.org</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>A release note beat is an area of the release notes that is the responsibility of one or more content contributors to oversee. For more ifnormation about beats, refer to <ulink url='http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats'>http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats</ulink>. </para>
+ <para>Thank you (in advance) for your feedback! </para>
</section>
</article>
Index: FileServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/FileServers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FileServers.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ FileServers.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,23 +1,44 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-FileServers">
+ <section>
<title>File Servers</title>
- <para>This section refers to file transfer and sharing servers. Please refer to the Web Servers and Samba sections for information on HTTP (Web) file transfer and Samba (Windows) file sharing. </para>
+ <para>This section refers to file transfer and sharing servers. Refer to <ulink url='http://fedoraproject.org/wiki/Docs/Beats/WebServers'>http://fedoraproject.org/wiki/Docs/Beats/WebServers</ulink> and <ulink url='http://fedoraproject.org/wiki/Docs/Beats/Samba'>http://fedoraproject.org/wiki/Docs/Beats/Samba</ulink> for information on HTTP (Web) file transfer and Samba (Windows) file sharing services. </para>
<section>
<title>Netatalk (Macintosh Compatibility)</title>
- <para>This section contains information related to Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the <ulink url='/AppleTalk'>AppleTalk</ulink> network protocols. </para>
- <warning>
- <title>
-Upgrading from Netatalk version 1 to version 2 may result in data loss. </title>
- <para>Version 2 of Netatalk uses a different method to store file resource forks from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. </para>
- </warning>
- <para>Upgrade information is available directly from the Netatalk site at <ulink url='http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>.
- </para>
- <para>The documentation is also included in the netatalk package. Refer to either <command>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html</command>, or <command>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf</command> (numbered page 25, document page 33). </para>
+ <para>Fedora includes version 2 of Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the AppleTalk network protocols. </para>
+ <itemizedlist>
+ <listitem>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>/!\</phrase>
+ </textobject>
+ </inlinemediaobject>
+ <emphasis role='strong'>Use Caution When Upgrading</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> You may experience data loss when upgrading from Netatalk version 1 to version 2. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>Version 2 of Netatalk stores file resource forks using a different method from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. Refer to the upgrade information available directly from the Netatalk site at <ulink url='http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>. </para>
+ <para>The documentation is also included in the <code>netatalk</code> package. Refer to either <code>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html</code> or <code>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf</code> (numbered page 25, document page 33). </para>
</section>
</section>
</article>
Index: FileSystems.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/FileSystems.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FileSystems.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ FileSystems.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,16 +1,36 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-FileSystems">
- <title>File Systems</title>
-<!-- <para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
- <para>Beat writers: this is where you want to fill in with instructions -->
-<!-- about how to post relevant information. Any questions that come up can -->
-<!-- be taken to a bugzilla report for discussion to resolution, or to -->
-<!-- fedora-docs-list for wider discussions. </para> -->
- <para><emphasis>No changes to report.</emphasis></para>
+ <section>
+ <title>Docs/Beats/FileSystems</title>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>/!\</phrase>
+ </textobject>
+ </inlinemediaobject> REMOVE ME Before Publishing - Beat Comment </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page.</para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions.</para>
+ </td>
+ </tr>
+ </table>
</section>
</article>
Index: I18n.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/I18n.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- I18n.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ I18n.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,12 +1,77 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-I18n">
+ <section>
<title>Internationalization (i18n)</title>
+ <para>This section includes information related to the support of various languages under Fedora Core. </para>
+ <section>
+ <title>Input Methods</title>
+ <para>SCIM (Simple Common Input Method) has replaced IIIMF as the input method system for Asian and other languages in Fedora Core in this release. SCIM uses <code>Ctrl-Space</code> as the default trigger key to toggle on and off the input method, though it is easy to change the hotkey or add hotkeys with the SCIM setup configuration tool. When <code>scim-anthy</code> is active Japanese users can now use the <code>Zenkaku_Hankaku</code> key to toggle between Japanese and ASCII input. </para>
+ <section>
+ <title>Installation</title>
+ <para>SCIM should be installed and run by default for Asian language desktops. Otherwise the required packages can be installed using the language support section of the package manager or running: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install <SCIM-IMEs>' </screen>
+ </listitem>
+ </itemizedlist>
+ <para>where <code><SCIM-IMEs></code> should be replaced by one or more of the following: </para>
+ <itemizedlist>
+ <listitem>
+ <para>Japanese: <code>scim-anthy</code>
+ </para>
+ <para>Korean: <code>scim-hangul</code>
+ </para>
+ <para>Simplified Chinese: <code>scim-pinyin scim-tables-chinese</code>
+ </para>
+ <para>Traditional Chinese: <code>scim-chewing scim-tables-chinese</code>
+ </para>
+ <para>Indian and other languages: <code>scim-m17n m17n-db-<language></code>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>You also need fonts for the language. The font packages are named <code>fonts-<language></code>, where <code><language></code> is one of <code>arabic</code>, <code>bengali</code>, <code>chinese</code>, <code>gujarati</code>, <code>hebrew</code>, <code>hindi</code>, <code>japanese</code>, <code>korean</code>, <code>punjabi</code>, <code>tamil</code>. </para>
+ <para>If your desktop is not running in an Asian locale, to activate it in your user account, run these commands, then logout and login again to your desktop. </para>
+ <itemizedlist>
+ <listitem>
+ <screen>mkdir ~/.xinput.d ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default</screen>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>SCIM applet and toolbar</title>
+ <para>When SCIM is running, an applet icon appears in the notification area of the desktop panel. The icon is a grey keyboard icon when SCIM is inactive, and an Input Method Engine (IME) icon when it is active. When SCIM is active, by default the SCIM input method toolbar with status information also appears. </para>
+ <para>Clicking the left mouse button on the applet activates a SCIM language switching menu for changing the current Input Method Engine. The menu only appears when an application using the Input Method has focus. Clicking the right mouse button on the applet or SCIM toolbar activates the setup menu. </para>
+ </section>
+ <section>
+ <title>SCIM configuration</title>
+ <para>You can configure SCIM and IMEs using the setup configuration tool available from the setup menu. In the IME general configuration pane, you can select which languages or IMEs appear on the language switching menu. </para>
+ </section>
+ <section>
+ <title>New conversion engines</title>
<para>
-SCIM has replaced IIIMF as the language input framework in Fedora Core in this release. </para>
+ <code>anthy</code>, a new Japanese conversion engine replaces the old Canna server system, and <code>libchewing</code>, a new Traditional Chinese conversion engine, has been added. </para>
+ </section>
+ </section>
+ <section>
+ <title>Fonts</title>
+ <para>Support is now available for synthetic emboldening of fonts that do not have a bold face. </para>
+ <para>New fonts for Chinese have been added: AR PL ShanHeiSun Uni (<code>uming.ttf</code>) and AR PL ZenKai Uni (<code>ukai.ttf</code>). The default font is AR PL ShanHeiSun Uni, which contains embedded bitmaps. If you prefer outline glyphs you can put the following section in your <code>~/.font.conf</code> file: </para>
+ <screen><fontconfig><match target="font"><test name="family" compare="eq"><string>AR PL ShanHeiSun Uni</string></test><edit name="embeddedbitmap" mode="assign"><bool>false</bool></edit></match></fontconfig></screen>
+ <para>
+ </para>
+ </section>
+ <section>
+ <title>gtk2 IM submenu</title>
+ <para>The Gtk2 context menu IM submenu no longer appears by default. You can enable it on the command line with the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>gconftool-2 --type bool --set '/desktop/gnome/interface/show_input_method_menu' true </screen>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
</article>
Index: Installer.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Installer.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Installer.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Installer.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,69 +1,182 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Installer">
+ <section>
<title>Installation-Related Notes</title>
- <para>This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core in general. </para>
- <para> If you intend to download the Fedora Core 5 Test 2 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. For example, wget before version 1.9.1-16 in Fedora will exit with a File size limit exceeded error. </para>
- <para> Wget 1.9.1-16 and above, curl and ncftpget file downloading tools do not have this limitation, and can successfully download files larger than 2GB. </para>
- <para>Bittorrent is another method for downloading large files. For information about obtaining and using the torrent file refer to this website: </para>
+ <para>This section outlines those issues that are related to <emphasis role='strong'>Anaconda</emphasis> (the Fedora Core installation program) and installing Fedora Core in general. </para>
+ <itemizedlist>
+ <listitem>
+ <table>
+ <caption/>
+ <tr>
+ <td>
<para>
- <ulink url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='16' fileref='/wiki/ntheme/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>
+ </section>
<section>
- <title>Installer Notes</title>
+ <title>Anaconda Notes</title>
<itemizedlist>
<listitem>
- <para> The Fedora Core installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type linux mediacheck at the boot: prompt. </para>
- <para>The mediacheck function is highly sensitive, and may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files. For best results with the mediacheck, boot with the option: </para>
- <screen>linux ide=nodma </screen>
- <para>Use the sha1sum utility to verify discs before carrying out an installation. This test accurately identifies discs that are not valid or identical to the ISO image files. </para>
+ <para>
+ <emphasis role='strong'>Anaconda</emphasis> tests the integrity of installation media by default. This function works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. The Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs. Many of the bugs reported are actually due to improperly-burned CDs. To use this test, type <code>linux mediacheck</code> at the <code>boot:</code> prompt. </para>
+ <para>The <code>mediacheck</code> function is highly sensitive, and may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files. For best results with <code>mediacheck</code>, boot with the following option: </para>
+ <screen>linux ide=nodma </screen>
+ <para>Use the <code>sha1sum</code> utility to verify discs before carrying out an installation. 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/ntheme/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>
</listitem>
<listitem>
- <para> Memory testing may be performed prior to installing Fedora Core by entering memtest86 at the boot: prompt. This causes the Memtest86 standalone memory testing software to run. Memtest86 memory testing continues until the Esc key is pressed. </para>
- <note>
- <title>Boot From Installation CD 1</title>
- <para> You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this feature.</para>
- </note>
+ <para> You may perform memory testing before you install Fedora Core by entering <code>memtest86</code> at the <code>boot:</code> prompt. This option runs the <emphasis role='strong'>Memtest86</emphasis> standalone memory testing software in place of <emphasis role='strong'>Anaconda</emphasis>. <emphasis role='strong'>Memtest86</emphasis> memory testing continues until the <code>Esc</code> key is pressed. </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'>
+ <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>
</listitem>
<listitem>
- <para> Fedora Core supports graphical FTP and HTTP installations. However, due to the necessity of containing the installer image in RAM, only systems with more than 128MB of RAM (or systems booted from CD-ROM 1, which contains the installer image) can use the graphical installer. Systems with 128MB or less will continue to use the text-based installer. </para>
+ <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. </para>
</listitem>
</itemizedlist>
<section>
- <title>Changes In The Installer</title>
+ <title>Changes in Anaconda</title>
<itemizedlist>
<listitem>
- <para> Support of yum for dependancy solver backend has been added and additional repositories are expected to be supported during installation in a future release. </para>
+ <para> The installer checks hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropriate in this release. Previous releases installed both variants and used the appropriate one as default. </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role='strong'>Anaconda</emphasis> now supports installation on several IDE software RAID chipsets using <code>dmraid</code>. To disable this feature, add the <code>nodmraid</code> option at the <code>boot:</code> prompt. For more information, refer to <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/ntheme/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>
+ </listitem>
+ <listitem>
+ <para> Serial mice are no longer formally supported in <emphasis role='strong'>Anaconda</emphasis> or Fedora Core. </para>
</listitem>
<listitem>
- <para> The installer checks the hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropriate in this release. Previous releases installed both the variants and used the appropriate one as default. </para>
+ <para> The disk partitioning screen has been reworked to be more user friendly. </para>
</listitem>
<listitem>
- <para> Partition setting has been reworked to be more user friendly </para>
+ <para> The package selection screen has been revamped. The new, simplified screen only displays the optional groups <emphasis>Office and Productivity</emphasis> (enabled by default), <emphasis>Software Development</emphasis>, <emphasis>Web Server</emphasis>, and <emphasis>Virtualization (Xen)</emphasis>. However, you may still fully customize your package selection. Refer to <ulink url='http://fedoraproject.org/wiki/Anaconda/PackageSelection'>http://fedoraproject.org/wiki/Anaconda/PackageSelection</ulink> for more details. </para>
</listitem>
<listitem>
- <para> Remote logging via syslog is supported in this release. pass syslog=host:port (port is optional) at the boot prompt. </para>
+ <para> Firewall and SELinux configuration has been moved to the <emphasis>Setup Agent</emphasis> (<code>firstboot</code>), the final phase of the graphical installation process. </para>
</listitem>
<listitem>
- <para> Firewall/SELinux configuration has been moved to the final installation phase called 'firstboot'. </para>
+ <para> The timezone configuration screen now features zooming areas on the location selection map. </para>
</listitem>
<listitem>
- <para> Rendering of html pages is now done using the gtkhtml widget for better capability. </para>
+ <para> This release supports remote logging via <code>syslog</code>. To use this feature, add the option <code>syslog=host:port</code> at the boot prompt. The <code>:port</code> specifier is optional. </para>
</listitem>
<listitem>
- <para> Kickstart has been refactored into its own package - pykickstart - containing parser and writers. As a result of this change validation and extending kickstart is now much easier. </para>
+ <para>
+ <emphasis role='strong'>Anaconda</emphasis> now renders release notes with the <code>gtkhtml</code> widget for better capability. </para>
</listitem>
<listitem>
- <para> Serial mice is not formally supported in the installer and in Fedora Core anymore. </para>
+ <para> Kickstart has been refactored into its own package, <code>pykickstart</code>, and contains a parser and writers. As a result of this change, validation and extension is now much easier. </para>
</listitem>
<listitem>
- <para> Full support of dmraid (disabled by default). To enable that feature, add this option to the boot command line: </para>
- <screen>dmraid </screen>
- <para>For more information, check the <ulink url='/DmraidStatus'>DmraidStatus</ulink> page. </para>
+ <para>
+ <emphasis role='strong'>Anaconda</emphasis> now uses <code>yum</code> as the backend for solving package dependencies. Additional repositories such as Fedora Extras are expected to be supported during installation in a future release. </para>
</listitem>
</itemizedlist>
</section>
@@ -71,38 +184,62 @@
<title>Installation Related Issues</title>
<itemizedlist>
<listitem>
- <para> Certain hardware configurations (particularly those with LCD displays) may experience problems while starting the Fedora Core installation program. In these instances, restart the installation, and add the "nofb" option to the boot command line. </para>
- <note>
- <title>CJK Language Support</title>
- <para> Chinese, Japanese, and Korean graphical installations started using the "nofb" option will start in English, and then switch to the appropriate language once the graphical phase of the installation process begins. </para>
- </note>
- </listitem>
- <listitem>
<para> Some Sony VAIO notebook systems may experience problems installing Fedora Core from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line: </para>
+ <itemizedlist>
+ <listitem>
<screen>pci=off ide1=0x180,0x386 </screen>
- <para>This option allows the installation to proceed normally; any devices not detected due to the use of this option are configured the first time Fedora Core is booted. </para>
+ </listitem>
+ </itemizedlist>
+ <para>Installation should proceed normally, and any devices not detected are configured the first time Fedora Core is booted. </para>
+ </listitem>
+ <listitem>
+ <para> Not all IDE RAID controllers are supported. If your RAID controller is not yet supported by <code>dmraid</code>, you may combine drives into RAID arrays by configuring Linux software RAID. For supported controllers, configure the RAID functions in the computer BIOS. </para>
</listitem>
</itemizedlist>
</section>
- </section>
<section>
- <title>Upgrading Related Issues</title>
- <para>Refer to <ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink> page for detailedrecommended procedures for upgradation of Fedora. </para>
- <para>In general, fresh installations are to be recommended over upgrades, particularly for systems with software from add-on repositories installed. If third party packages are installed on the system, they might not work as expected. If an upgrade is attempted, the following may be helpful. </para>
+ <title>Upgrade Related Issues</title>
+ <para>Refer to <ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink> for detailed recommended procedures for upgrading Fedora. </para>
+ <para>In general, fresh installations are recommended over upgrades, particularly for systems which include software from third-party repositories. Third-party packages remaining from a previous installation may not work as expected on an upgraded Fedora system. If you decide to perform an upgrade anyway, the following information may be helpful. </para>
<itemizedlist>
<listitem>
- <para> Before upgrading (or installing), back up the system completely. In particular, preserve <emphasis>/etc</emphasis>, <emphasis>/home</emphasis>, and possibly <emphasis>/opt</emphasis> and <emphasis>/usr/local</emphasis> if customized packages are installed there. Using a multi-boot approach with a "clone" of the old installation on alternate partition[s] as a fall-back might be considered. Creating alternate boot media, such as GRUB floppy would be advisable. </para>
- <note>
- <title>Make Backups!</title>
- <para> Backups of configurations in <emphasis>/etc</emphasis> are also very useful in reconstructing system settings after a fresh install.</para>
- </note>
- </listitem>
- <listitem>
- <para> After completing the upgrade, run the command: </para>
+ <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/ntheme/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>
+ </listitem>
+ <listitem>
+ <para> After you complete the upgrade, run the following command: </para>
+ <itemizedlist>
+ <listitem>
<screen>rpm -qa --last > RPMS_by_Install_Time.txt </screen>
- </listitem>
- <listitem>
- <para> Inspect the end of the output for packages that pre-date the upgrade and remove/upgrade those from 3rd party repos, or otherwise deal with them as necessary. </para>
+ </listitem>
+ </itemizedlist>
+ <para>Inspect the end of the output for packages that pre-date the upgrade. Remove or upgrade those packages from third-party repositories, or otherwise deal with them as necessary. </para>
</listitem>
</itemizedlist>
</section>
Index: Java.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Java.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Java.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Java.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,17 +1,117 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Java">
- <title>Java</title>
- <para>A free and open source Java environment is available within this Fedora Core release. </para>
- <para>It has three components: GNU Java runtime ("libgcj"), the Eclipse Java compiler ("ecj"), and a set of wrappers and links ("java-gcj-compat") that present the runtime and compiler to the user in the same way as other Java environments are presented. </para>
- <para>Several major software such as Openoffice.org Base, Eclipse, Apache Tomcat and several other Java software included in this release is compatible with it </para>
- <para>For more information see the FAQ at
- <ulink url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>.
- </para>
- <para>Refer to the <ulink url='/Docs/Beats/PackageNotes/Java'>Docs/Beats/PackageNotes/Java</ulink> page for information about Java packages. </para>
+ <section>
+ <title>Java and java-gcj-compat</title>
+ <para>A free and open source Java environment is available within this Fedora Core release, called . 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>
+ <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'>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>
+ <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. </para>
+ <para>The Java software packages included in this Fedora release use the new, integrated environment . These packages include <emphasis role='strong'>OpenOffice.org Base</emphasis>, <emphasis role='strong'>Eclipse</emphasis>, and <emphasis role='strong'>Apache Tomcat</emphasis>. </para>
+ <para>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 free Java environment in Fedora. </para>
+ <itemizedlist>
+ <listitem>
+ <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'>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>
+ <section>
+ <title>Handling Java and Java-like Packages</title>
+ <para>In addition to the free software stack, Fedora Core is designed to let you install multiple Java implementations and switch between them using the <code>alternatives</code> 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>. </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: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>alternatives --config java alternatives --config javac</screen>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Fedora and the JPackage Java Packages</title>
+ <para>Fedora Core includes many packages derived from the JPackage Project, which provides a Java software repository. These packages have been modified in Fedora to remove proprietary software dependencies and to make use of GCJ's ahead-of-time compilation feature. Fedora users should use the Fedora repositories for updates to these packages, and may use the JPackage repository for packages not provided by Fedora. </para>
+ <para>Refer to the JPackage website at <ulink url='http://jpackage.org'>http://jpackage.org</ulink> for more information on the project and the software that it provides. </para>
+ <itemizedlist>
+ <listitem>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/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>
+ </section>
</section>
</article>
Index: Kernel.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Kernel.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Kernel.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Kernel.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,27 +1,35 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Kernel">
+ <section>
<title>Linux Kernel</title>
- <para>This section is for content related to the kernel. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. If you have any questions about what content might be appropriate for this page or if a sub-page is needed, please contact <ulink url='/SamFolkWilliams'>SamFolkWilliams</ulink> or email the Fedora Documentation Project at <command>fedora-docs-list at redhat.com</command>. </para>
+ <para>This section covers changes and important information regarding the kernel in Fedora Core . </para>
<section>
<title>Version</title>
<para>This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include additional patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the so-called <emphasis>vanilla kernel</emphasis> from the kernel.org web site: </para>
<para>
<ulink url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
</para>
- <para>You may obtain a list of any such patches by using the command on the Fedora Core package: </para>
+ <para>To obtain a list of these patches, download the source RPM package and run the following command against it: </para>
+ <itemizedlist>
+ <listitem>
<screen>rpm -qpl kernel-<version>.src.rpm</screen>
+ </listitem>
+ </itemizedlist>
</section>
<section>
<title>Changelog</title>
- <para>The package changelog can be retrieved using the following command </para>
- <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>. A short and full diff of the kernel is available from <ulink url='http://kernel.org/git'>http://kernel.org/git</ulink>. The Fedora version is based on the Linus tree. </para>
- <para>Customisations made for the Fedora version are available from <ulink url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink> . </para>
+ <para>To retrieve a log of changes to the package, run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>rpm -q --changelog kernel-<version></screen>
+ </listitem>
+ </itemizedlist>
+ <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>. A short and full diff of the kernel is available from <ulink url='http://kernel.org/git'>http://kernel.org/git</ulink>. 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> . </para>
</section>
<section>
<title>Kernel Flavors</title>
@@ -31,95 +39,291 @@
<para>Fedora Core includes the following kernel builds: </para>
<itemizedlist>
<listitem>
- <para> Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPU's or processors. Configured sources are available in the <command>kernel-[smp-]devel-<version>.<arch>.rpm</command> package. </para>
+ <para> Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPUs. Configured sources are available in the <code>kernel-[smp-]devel-<version>.<arch>.rpm</code> package. </para>
+ </listitem>
+ <listitem>
+ <para> Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-hypervisor-devel-<version>.<arch>.rpm</code> package. </para>
</listitem>
<listitem>
- <para> Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the <command>kernel-xen-hypervisor-devel-<version>.<arch>.rpm</command> package. </para>
+ <para> Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-guest-devel-<version>.<arch>.rpm</code> package. </para>
</listitem>
<listitem>
- <para> Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the <command>kernel-xen-guest-devel-<version>.<arch>.rpm</command> package. </para>
+ <para> Kdump kernel for use with kexec/kdump capabilities. Configured sources are available in the <code>kernel-kdump-devel-<version>.<arch>.rpm</code> package. </para>
+ </listitem>
+ </itemizedlist>
+ <para>You may install sources for all kernel flavors at the same time. The files are installed in the <code>/usr/src/kernels/<version>-[xen-hypervisor|xen-guest|kdump]-<arch>/</code> tree. Use the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install kernel-{xen,hypervisor,xen-guest,kdump}-devel'</screen>
</listitem>
+ </itemizedlist>
+ <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>
- <para> Kdump kernel for use with kexec/kdump capabilities. Configured sources are available in the <command>kernel-kdump-devel-<version>.<arch>.rpm</command> package. </para>
+ <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>
- <para>Sources for all kernel flavors may be installed at the same
- time. The files will be installed into the
- <command>/usr/src/kernels/<version>[-xen-hypervisor/xen-guest/kdump]-<arch>/</command>
- tree. Use this command as appropriate: </para>
- <screen>rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-<version>.<arch>.rpm</screen>
- <important>
- <title>Default Kernels in x86_64 Architecture Provide SMP Capability</title>
- <para> There is no separate SMP kernel available for this architecture in Fedora Core . </para>
- </important>
+ </section>
+ <section>
+ <title>Reporting Bugs</title>
+ <para>Refer to <ulink url='http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html'>http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html</ulink> for information on reporting bugs in the Linux kernel. You may also use <ulink url='http://bugzilla.redhat.com'>http://bugzilla.redhat.com</ulink> for reporting bugs which are specific to Fedora. </para>
</section>
<section>
<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 <command>/usr/src/linux/</command> directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the Fedora Core packages. Install the appropriate kernel sources, as shown earlier, and then: </para>
- <screen>ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux</screen>
+ <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 link, as shown below, you should be able to use those learning materials with the Fedora Core packages. Install the appropriate kernel sources, as shown earlier, and then run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux'</screen>
+ </listitem>
+ </itemizedlist>
+ <para>Enter the <code>root</code> password when prompted. </para>
</section>
<section>
<title>Preparing for Kernel Development</title>
<para>Fedora Core does not include the kernel-source package provided by older versions. Instead, configured sources are available, as described in this kernel flavors section. </para>
- <para>Users that require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. </para>
- <para>To create an exploded source tree from this file, perform the following steps: </para>
- <important>
- <title>These Instructions Refer to the Currently-running 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, you must understand that the phrase <version> refers to the kernel version shown by the command: <command>uname -r</command>. </para>
- </important>
- <para>1. Obtain the kernel-<version>.src.rpm file from one of the following sources: </para>
- <itemizedlist>
- <listitem>
- <para> The SRPMS directory on the appropriate SRPMS CD iso image. </para>
- </listitem>
- <listitem>
- <para> The FTP site where you got the kernel package. </para>
- </listitem>
- <listitem>
- <para> By running the following command: </para>
- <screen>yum install yum-utilsyumdownloader --source kernel</screen>
- </listitem>
- </itemizedlist>
- <para>2. Install <command>kernel-<version>.src.rpm</command> using the command: </para>
- <screen>rpm -Uvh kernel-<version>.src.rpm`</screen>
- <para>This writes the RPM contents into <command>/usr/src/redhat/SOURCES</command> and <command>/usr/src/redhat/SPECS</command>. </para>
- <para>3. Prepare the kernel sources using the commands: </para>
- <screen>cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) kernel-2.6.spec</screen>
- <para>The kernel source tree is then located in the <command>/usr/src/redhat/BUILD/kernel-<version>/</command> directory. It is common practice to move the resulting linux-<version> directory to the <command>/usr/src/</command> tree; while not strictly necessary, do this to match the generally-available documentation. </para>
- <screen>
-<command>cd /usr/src/redhat/BUILD/kernel-<version>
-mv linux-<version> /usr/src/
-cd /usr/src
-ln -s ./linux-<version> linux
-cd /usr/src/linux</command>
-</screen>
- <para>4. The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named <command>configs/kernel-<version>-i686-smp.config</command>. Issue the following command to place the desired configuration file in the proper place for building: </para>
- <screen>cp configs/<desired-config-file> .config</screen>
- <para>You can also find the <command>.config</command> file that matches your current kernel configuration in the <command>/lib/modules/<version>/build/.config</command> file. </para>
- <para>5. Every kernel gets a name based on its version number. This is the value the <command>uname -r</command> command displays. The kernel name is defined by the first four lines of the kernel Makefile. To protect the innocent, the Makefile has been changed to generate a kernel with a different name from that of the running kernel. Before a module can be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. To do this, you must edit the kernel Makefile. </para>
- <para>For example, if the <command>uname -r</command> returns the string <command>2.6.11-1.234_FC4</command>, change the <command>EXTRAVERSION</command> definition from this: </para>
- <screen>EXTRAVERSION = -prep</screen>
- <para>to this: </para>
- <screen>EXTRAVERSION = -1.234_FC4</screen>
- <para>that is, substitute everything from the final dash onward. </para>
- <para>6. Issue the following command: </para>
- <screen>make oldconfig</screen>
- <para>You can then proceed as usual. </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>
+ <para>Users who require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the following 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>
+ <orderedlist numeration='arabic'>
+ <listitem>
+ <para>Prepare a RPM package building environment in your home directory. Run the following commands: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install fedora-rpmdevtools'fedora-buildrpmtree</screen>
+ <para>Enter the <code>root</code> password when prompted. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Obtain the <code>kernel-<version>.src.rpm</code> file from one of the following sources: </para>
+ <itemizedlist>
+ <listitem>
+ <para> the SRPMS directory on the appropriate SRPMS CD iso image </para>
+ </listitem>
+ <listitem>
+ <para> the HTTP or FTP site where you got the kernel package </para>
+ </listitem>
+ <listitem>
+ <para> by running the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'yum install yum-utils'su -c 'yumdownloader --source kernel'</screen>
+ </listitem>
+ </itemizedlist>
+ <para>Enter the <code>root</code> password when prompted. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Install <code>kernel-<version>.src.rpm</code> using the command: </para>
+ <itemizedlist>
+ <listitem>
+ <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. </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>
+ </listitem>
+ <listitem>
+ <para>Prepare the kernel sources using the commands: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>cd ~/rpmbuild/SPECSrpmbuild -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>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>The configurations for the specific kernels shipped in Fedora Core are in the <code>configs/</code> directory. For example, the i686 SMP configuration file is named <code>configs/kernel-<version>-i686-smp.config</code>. Issue the following command to place the desired configuration file in the proper place for building: </para>
+ <itemizedlist>
+ <listitem>
+ <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>
+ </itemizedlist>
+ </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>
+ <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>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Run the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>make oldconfig</screen>
+ <para>You may then proceed as usual. </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </orderedlist>
</section>
<section>
<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. For example, to build the <command>foo.ko</command> module, create the following Makefile in the directory containing the <command>foo.c</command> file: </para>
- <screen>
-<computeroutput>obj-m := foo.o
-KDIR := /lib/modules/$(shell uname -r)/build
-PWD := $(shell pwd)
-default:$(MAKE) -C $(KDIR) M=$(PWD) modules</computeroutput>
-</screen>
- <para>Issue the <command>make</command> command to build the <command>foo.ko</command> module. </para>
+ <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. 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>
+ <itemizedlist>
+ <listitem>
+ <screen>obj-m := foo.oKDIR := /lib/modules/$(shell uname -r)/buildPWD := $(shell pwd)default:$(MAKE) -C $(KDIR) M=$(PWD) modules</screen>
+ </listitem>
+ </itemizedlist>
+ <para>Issue the <code>make</code> command to build the <code>foo.ko</code> module. </para>
</section>
<section>
<title>User Space Dependencies on the Kernel</title>
- <para>Fedora Core release has support for clustered storage through the Global File System (GFS). This requires a special kernel that works in conjunction with some user-space utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you cannot simply use the <command>rpm -e kernel-<version></command> command as in earlier distributions because these user space packages depend on the kernel package. You may either list both the kernel package and all of its user space dependent packages on the <command>rpm -e</command> command, or you can use the <command>yum remove kernel-<version></command> command instead. The <command>yum</command> command automatically removes dependent packages, if necessary. </para>
+ <para>Fedora Core has support for clustered storage through the Global File System (GFS). GFS requires special kernel modules that work in conjunction with some user-space utilities, such as management daemons. To remove such a kernel, perhaps after an update, use the <code>su -c 'yum remove kernel-<version>'</code> command instead. The <code>yum</code> command automatically removes dependent packages, if necessary. </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'>PowerPC does not support GFS</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> The GFS kernel modules are not built for the PowerPC architecture in Fedora Core . </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
</section>
</section>
</article>
Index: Legacy.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Legacy.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Legacy.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Legacy.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,44 +1,26 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Legacy">
- <title>Legacy Information</title>
- <section>
- <title>Systemwide Search Changes</title>
- <important>
- <title><command>Slocate</command> Replaced with <command>mlocate</command></title>
- <para> The <command>/usr/bin/{locate,updatedb}</command> implementation <command>slocate</command> was replaced by <command>mlocate</command>. </para>
- <itemizedlist>
- <listitem>
- <para> The <command>locate</command> command should be completely compatible </para>
- </listitem>
- <listitem>
- <para>
- <command>/etc/updatedb.conf</command> is compatible for correct configuration files </para>
- </listitem>
- <listitem>
- <para> Syntax errors that <command>slocate</command> would not detect are now reported </para>
- </listitem>
- <listitem>
- <para> The <command>DAILY_UPDATE</command> variable is not supported </para>
- </listitem>
- <listitem>
- <para> The <command>updatedb</command> command is not compatible, custom scripts using <command>updatedb</command> might have to be changed. </para>
- </listitem>
- </itemizedlist>
- </important>
- </section>
- <section>
- <title>LinuxThreads No Longer Available</title>
- <para>The <command>LinuxThreads</command> library, which was deprecated in Fedora Core 4, is no longer available in this release. <command>NPTL</command> has been the default threading library since Red Hat Linux 9. </para>
- </section>
- <section>
- <title>Legacy Compatability Libraries</title>
- <para>Fedora Core includes legacy system libraries for compatibility with older software. This software is part of the <emphasis role='strong'>Legacy Software Development</emphasis> group that is not installed by default. Users who require this functionality can select this group during installation or run the following command post-installation. </para>
-<screen>yum groupinstall "Legacy Software Development"</screen>
- </section>
- </section>
+ <section>
+ <title>Fedora Legacy - Community Maintenance Project</title>
+ <para>The Fedora Legacy Project is a community-supported open source project to extend the lifecycle of select "maintenance mode" Red Hat Linux and Fedora Core distributions. The Fedora Legacy Project works with the Linux community to provide security and critical bug fix errata packages. This work extends the effective lifetime of older distributions in environments where frequent upgrades are not possible or desirable. For more information about the Fedora Legacy Project, refer to <ulink url='http://fedoraproject.org/wiki/Legacy'>http://fedoraproject.org/wiki/Legacy</ulink>. </para>
+ <para>Currently the Fedora Legacy Project maintains the following distributions and releases in maintenance mode: </para>
+ <itemizedlist>
+ <listitem>
+ <para> Red Hat Linux 7.3 and 9 </para>
+ </listitem>
+ <listitem>
+ <para> Fedora Core 1, 2, and 3 </para>
+ </listitem>
+ </itemizedlist>
+ <para>The Fedora Legacy Project will provide updates for these releases as long as there is community interest. When interest is not sustained further, maintenance mode ends with the second test release for the third subsequent Core release. For example, maintenance mode for Fedora Core 4, if not sustained by the community, ends with the release of Fedora Core 7 test2. This provides an effective supported lifetime (Fedora Core plus Fedora Legacy Support) of about 18 months. </para>
+ <para>The Fedora Legacy Project always needs volunteers to perform quality assurance testing on packages waiting to be published as updates. Refer to <ulink url='http://fedoraproject.org/wiki/Legacy/QATesting'>http://fedoraproject.org/wiki/Legacy/QATesting</ulink> for more information. Also visit our issues list at <ulink url='http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html'>http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html</ulink> for further information and pointers to bugs we have in the queue. </para>
+ <para>If you need help in getting started, visit the project home page on the Wiki at <ulink url='http://fedoraproject.org/wiki/Legacy'>http://fedoraproject.org/wiki/Legacy</ulink>, or the Mentors page at <ulink url='http://fedoraproject.org/wiki/Mentors'>http://fedoraproject.org/wiki/Mentors</ulink>. If you are looking for others ways to participate in Fedora, refer to <ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>. </para>
+ <para>
+ <ulink url='/CategoryLegacy'>CategoryLegacy</ulink>
+ </para>
+ </section>
</article>
Index: Multimedia.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Multimedia.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Multimedia.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Multimedia.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,39 +1,36 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Multimedia">
+ <section>
<title>Multimedia</title>
<para>Fedora Core includes applications for assorted multimedia functions, including playback, recording and editing. Additional packages are available through the Fedora Extras repository. </para>
<section>
<title>Multimedia Players</title>
- <para>By default, Fedora Core installs with <emphasis role='strong'>Rhythm Box</emphasis>, <emphasis role='strong'>Totem</emphasis>, and <emphasis role='strong'>Helix Player</emphasis> for media playback. In addition, many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular <emphasis role='strong'>XMMS</emphasis> package. Both GNOME and KDE also have specific sets of programs that can be used with a variety of formats. Other popular programs, such as Adobe/Macromedia's <emphasis role='strong'>Flash Player</emphasis>, <emphasis role='strong'>Real Player</emphasis>, <emphasis role='strong'>VLC</emphasis>, <emphasis role='strong'>MPlayer</emphasis>, and <emphasis role='strong'>Xine</emphasis>, can also be installed, but are excluded from the Fedora repositories since they are not compatible with Fedora's licensing or are usually distributed with support for restricted formats. For more on this, refer to: the <ulink ur!
l='/http'>//fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software:Excluded Multimedia Software</ulink> section. </para>
- <para>Fedora Core is also equipped to take full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. This means that many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, the old limitation disappears. For more information about ALSA, visit the project website at <ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>.
- </para>
+ <para>The default installation of Fedora Core includes <emphasis role='strong'>Rhythmbox</emphasis>, <emphasis role='strong'>Totem</emphasis>, and <emphasis role='strong'>Helix Player</emphasis> for media playback. Many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular <code>XMMS</code> package. Both GNOME and KDE have a selection of players that can be used with a variety of formats. Additional programs are available from third parties to handle other formats. </para>
+ <para>Fedora Core also takes full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. Many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, this limitation disappears. For more information about ALSA, visit the project website at <ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>. </para>
</section>
<section>
<title>Ogg and Xiph.Org Foundation Formats</title>
- <para>Fedora includes complete support for the Ogg media container format, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. More information on these formats and how to use them can be found at the Xiph.Org Foundation's web site at <ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>.
- </para>
+ <para>Fedora includes complete support for the Ogg media container format, and the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. These freely-distributable formats are not encumbered by patent or license restrictions. They provide powerful and flexible alternatives to more popular, restricted formats. The Fedora Project encourages the use of open source formats in place of restricted ones. For more information on these formats and how to use them, refer to the Xiph.Org Foundation's web site at <ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>. </para>
</section>
<section>
- <title>MP3 & DVD Support</title>
- <para>Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. For more information, refer to <ulink url='http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software'>http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software</ulink>.
- </para>
+ <title>MP3, DVD and Other Excluded Multimedia</title>
+ <para>Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. Fedora also excludes several multimedia application programs due to patent or license restrictions, such as Flash Player and Real Player. For more on this subject, please refer to <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>. </para>
</section>
<section>
- <title>Excluded Multimedia Software</title>
- <anchor id='Excluded_Multimedia_Software'/>
- <para>
- </para>
- <para>Several programs are excluded from Fedora Core and Fedora Extras due to patent or license restrictions. These include programs which provide MP3 and DVD support, Flash Player, and Real Player. For more on this subject, please see <ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>.
- </para>
+ <title>CD and DVD Authoring and Burning</title>
+ <para>Fedora Core and Extras include a variety of tools for easily mastering and burning CDs and DVDs. GNOME users can burn directly from the Nautilus file manager, or choose the <code>gnomebaker</code> or <code>graveman</code> packages from Fedora Extras, or the older <code>xcdroast</code> package from Fedora Core. KDE users can use the robust <code>k3b</code> package for these tasks. Console tools include <code>cdrecord</code>, <code>readcd</code>, <code>mkisofs</code>, and other typical Linux applications. </para>
</section>
<section>
- <title>CD and DVD Authoring and Burning</title>
- <para>Tools are included in Fedora Core and Fedora Extras for easily mastering and burning CDs and DVDs. Tools that can be used from the console include <command>cdrecord</command>, <command>readcd</command>, <command>mkisofs</command>, and other typical Linux applications. For GNOME users, the <command>xcdroast</command> package from Fedora Core and the <command>graveman</command> package from Fedora Extras allows for easy preparation of audio and data discs. For KDE users, the <command>k3b</command> package provides a very robust tool for these tasks. </para>
+ <title>Screencasts</title>
+ <para>You can use Fedora to create and play back <emphasis>screencasts</emphasis>, which are recorded desktop sessions, using open technologies. Fedora Extras 5 includes <code>istanbul</code>, which creates screencasts using the Theora video format. These videos can be played back using one of several players included in Fedora Core. This is the preferred way to submit screencasts to the Fedora Project for either developer or end-user use. For a more comprehensive how-to, refer to <ulink url='http://fedoraproject.org/wiki/ScreenCasting'>http://fedoraproject.org/wiki/ScreenCasting</ulink>. </para>
+ </section>
+ <section>
+ <title>Extended Support through Plugins</title>
+ <para>Most of the media players in Fedora Core and Fedora Extras support the use of plugins to add support for additional media formats and sound output systems. Some use powerful backends, like <code>gstreamer</code>, to handle media format support and sound output. Plugin packages for these backends and for individual applications are available in Fedora Core and Fedora Extras, and additional plugins may be available from third parties to add even greater capabilities. </para>
</section>
</section>
</article>
Index: Networking.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Networking.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Networking.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Networking.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,77 +1,99 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Networking">
+ <section>
<title>Networking</title>
<section>
- <title>Major Kernel Changes 2.6.11 - 2.6.14</title>
+ <title>Major Kernel Changes 2.6.11 - 2.6.15</title>
+ <para>Refer to <ulink url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.kernelnewbies.org/LinuxChanges</ulink> for a list of major changes. Some of them are highlighted below. </para>
<section>
<title>IPv4 Address Promotion</title>
- <para>Starting with version 2.6.12 of the kernel a new feature has been added called <emphasis>named address promotion</emphasis>. It allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. By enabling the new sysctl <command>net.ipv4.conf.all.promote_secondaries</command> (or one of the interface specific variants) this behaviour can be changed to promote one of the secondary addresses to be the new primary address. </para>
+ <para>Starting with version 2.6.12 of the kernel, a new feature has been added called <emphasis>named address promotion</emphasis>. This feature allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. If you enable the new <code>sysctl</code> key <code>net.ipv4.conf.all.promote_secondaries</code>, or one of the interface specific variants, you can change this behavior to promote one of the secondary addresses to be the new primary address. </para>
</section>
<section>
<title>Configurable Source Address for ICMP Errors</title>
- <para>The current behaviour when selecting the source address for ICMP error messages is to use the address of the interface the ICMP error is going to be sent out. Kernel version 2.6.12 introduces a new sysctl <command>net.ipv4.icmp_errors_use_inbound_ifaddr</command> that allows changing this behaviour to use the address of the interface that received the original error-causing packet. </para>
- <para>For example, the kernel receives an ICMP echo request on eth0. Because the new sysctl option is enabled, this causes the ICMP echo reply to be sent out via eth1. The address of eth0 is used when the default behaviour would use the address of eth. </para>
- <para>This may ease network debugging in asynchronous routing setups. </para>
+ <para>By default, when selecting the source address for ICMP error messages, the kernel uses the address of the interface on which the ICMP error is going to be sent. Kernel version 2.6.12 introduces the new <code>sysctl</code> key <code>net.ipv4.icmp_errors_use_inbound_ifaddr</code>. If you enable this option the kernel uses the address of the interface that received the original error-causing packet. </para>
+ <para>Suppose the kernel receives a packet on interface <code>eth0</code> which generates an ICMP error, and the routing table causes the error message to be generated on interface <code>eth1</code>. If the new <code>sysctl</code> option is enabled, the ICMP error message indicates the source address as interface <code>eth0</code>, instead of the default <code>eth1</code>. This feature may ease network debugging in asynchronous routing setups. </para>
</section>
<section>
<title>LC-Trie Based Routing Lookup Algorithm</title>
- <para>A new routing lookup algorithm called <emphasis>trie</emphasis> has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation at the cost of increased memory consumption and complexity. </para>
+ <para>A new routing lookup algorithm called <emphasis>trie</emphasis> has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation, at the cost of increased memory consumption and complexity. </para>
</section>
<section>
<title>Pluggable Congestion Control Algorithm Infrastructure</title>
- <para>TCP congestion control algorithms are now pluggable and thus modular. The legacy New<emphasis role='strong'/>Reno algorithm stays default and acts as the fallback algorithm. The following new congestion control algorithms have been added: </para>
+ <para>TCP congestion control algorithms are now pluggable and thus modular. The legacy New<emphasis role='strong'/>Reno algorithm remains the default, and acts as the fallback algorithm. The following new congestion control algorithms have been added: </para>
<itemizedlist>
<listitem>
- <para> High Speed TCP congestion control. </para>
+ <para> High Speed TCP congestion control </para>
</listitem>
<listitem>
- <para> TCP Hybla congestion avoidance. </para>
+ <para> TCP Hybla congestion avoidance </para>
</listitem>
<listitem>
- <para> H-TCP congestion control. </para>
+ <para> H-TCP congestion control </para>
</listitem>
<listitem>
- <para> Scalable TCP congestion control. </para>
+ <para> Scalable TCP congestion control </para>
+ </listitem>
+ </itemizedlist>
+ <para>All existing congestion control modules have been converted to this new infrastructure, and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links. </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'>Affecting the Congestion Control Algorithm</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> The congestion control algorithm is socket specific, and may be changed via the socket option <code>TCP_CONGESTION</code>. </para>
+ </td>
+ </tr>
+ </table>
</listitem>
</itemizedlist>
- <para>All existing congestion control modules have been converted to this new infrastructure and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links. </para>
- <note>
- <title>
-Affecting the Congestion Control Algorithm </title>
- <para>An interesting addition for developers is that the congestion control algorithm is socket specific and can be changed via the socket option <command>TCP_CONGESTION</command>. </para>
- </note>
</section>
<section>
<title>Queue Avoidance upon Carrier Loss</title>
- <para>When a network driver notices a carrier loss, for example, when the cable is pulled out, the driver stops the queue in front of the driver. This has been causing the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now ceases to accept any packets for queueing for any device that is operationally down, that is, has its queue disabled. </para>
+ <para>When a network driver notices a carrier loss, such as when the cable is pulled out, the driver stops the queue in front of the driver. In the past, this stoppage caused the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now refuses to queue any packets for a device that is operationally down, that is, has its queue disabled. </para>
</section>
<section>
<title>DCCP Protocol Support</title>
- <para>Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental but known to work. Work has begun to make userspace applications aware of this new protocol. </para>
+ <para>Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental, but is known to work. Developers have begun work to make userspace applications aware of this new protocol. </para>
</section>
<section>
<title>Wireless</title>
- <para>A new driver named HostAP has been added to 2.6.14-rc1 allowing the emulation of a wireless access point in software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added. </para>
+ <para>A new HostAP driver appears in the kernel starting in 2.6.14-rc1, which allows the emulation of a wireless access point through software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added. </para>
</section>
<section>
<title>Miscellaneous</title>
<itemizedlist>
<listitem>
- <para> A lot of TCP Segmentation Offloading (TSO) related fixes have been included. </para>
+ <para> Many TCP Segmentation Offloading (TSO) related fixes are included. </para>
</listitem>
<listitem>
- <para> A new textsearch infrastructure has been added useable with the corresponding iptables and extended match. </para>
+ <para> A new textsearch infrastructure has been added, and is usable with corresponding iptables and extended match. </para>
</listitem>
<listitem>
<para> Both the IPv4 and IPv6 multicast joining interface visible by userspace have been reworked and brought up to the latest standards. </para>
</listitem>
<listitem>
- <para> The SNMPv2 MIB counter ipInAddrErrors is finally supported for IPv4. </para>
+ <para> The SNMPv2 MIB counter ipInAddrErrors is supported for IPv4. </para>
</listitem>
<listitem>
<para> Various new socket options proposed in Advanced API (RFC3542) have been added. </para>
@@ -80,22 +102,22 @@
</section>
</section>
<section>
- <title>Userspace Tools</title>
- <para>The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the iproute2 tool now issues a warning if no prefix length is provided to warn about possible unintended deletions: </para>
-<screen>
-<userinput>ip addr list dev eth0</userinput>
-<computeroutput>4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
-inet 10.0.0.3/24 scope global eth0</computeroutput>
-<userinput>su -c 'ip addr del 10.0.0.3 dev eth0'</userinput>
-<computeroutput>Warning: Executing wildcard deletion to stay compatible with old
-scripts. Explicitly specify the prefix length (10.0.0.3/32) to
-avoid this warning. This special behaviour is likely to disappear
-in further releases, fix your scripts!</computeroutput>
-</screen>
+ <title>User Tools</title>
+ <para>The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the <code>iproute2</code> tool now issues a warning if no prefix length is provided, to warn about possible unintended deletions: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>ip addr list dev eth0 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000inet 10.0.0.3/24 scope global eth0</screen>
+ <screen>su -c 'ip addr del 10.0.0.3 dev eth0' Warning: Executing wildcard deletion to stay compatible with oldscripts. Explicitly specify the prefix length (10.0.0.3/32) toavoid this warning. This special behaviour is likely to disappearin further releases, fix your scripts!</screen>
+ </listitem>
+ </itemizedlist>
<para>The correct method of deleting the address and thus avoiding the warning is: </para>
-<screen>su -c 'ip addr del 10.0.0.3/24 dev eth0'</screen>
- <para>Previously, it has not been possible to tell if an interface is down administratively or because no carrier can be found (cable unplugged). The flag <command>NO-CARRIER</command> has been introduced that shows up as a link flag if the link is administratively up but no carrier can be found. </para>
- <para>The ip command now supports a batch mode via the argument <command>-batch</command> that works similar to the tc command to speed up batches of tasks. </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'ip addr del 10.0.0.3/24 dev eth0'</screen>
+ </listitem>
+ </itemizedlist>
+ <para>Previously, it was not possible to tell if an interface was down administratively or because no carrier was found, such as if a cable were unplugged. The new flag <code>NO-CARRIER</code> now appears as a link flag if the link is administratively up but no carrier can be found. </para>
+ <para>The <code>ip</code> command now supports a batch mode via the argument <code>-batch</code>, which works similar to the <code>tc</code> command to speed up batches of tasks. </para>
</section>
</section>
</article>
Index: OverView.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/OverView.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- OverView.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ OverView.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,62 +1,103 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-OverView">
+ <section>
<title>Fedora Core 5 Tour</title>
- <para>Welcome to Fedora. In this new exciting new release, we present you a sneak preview of Fedora Core 5 filled with pictures and videos available at <ulink url='http://fedoraproject.org/wiki/Tours/FedoraCore5'>http://fedoraproject.org/wiki/Tours/FedoraCore5</ulink>. </para>
+ <para>You can find a tour filled with pictures and videos of this exciting new release at <ulink url='http://fedoraproject.org/wiki/Tours/FedoraCore5'>http://fedoraproject.org/wiki/Tours/FedoraCore5</ulink>. </para>
<section>
<title>What Has Changed Since Fedora Core 4</title>
- <note>
- <title>Your Participation Is Requested</title>
- <para>
-We request active participation from the community to test the following major changes with special care and provide feedback to the developers for a robust and cutting edge release of Fedora Core 5. You can provide feedback and discuss changes in the fedora-test (<ulink url='http://redhat.com/mailman/listinfo/fedora-test-list/'>http://redhat.com/mailman/listinfo/fedora-test-list/</ulink>) mailing list. Thank you for your interest and participation in the development of Fedora. </para>
- </note>
+ <para>This release is the culmination of nine months of development, and includes significant new versions of many key products and technologies. The following sections provide a brief overview of major changes from the last release of Fedora Core. </para>
<section>
<title>Desktop</title>
+ <para>Some of the highlights of this release include: </para>
<itemizedlist>
<listitem>
- <para> A completely revamped look and feel including a bubbly new theme, wallpaper, screensaver and logo has been provided that is visually appealing and demonstrates the exciting and user friendly nature of Fedora. </para>
+ <para> There is a completely revamped appearance with a bubbly new theme and the first use of the new Fedora logo. </para>
</listitem>
<listitem>
- <para> GNOME 2.13.4 (<ulink url='http://live.gnome.org/TwoPointThirteen'>http://live.gnome.org/TwoPointThirteen</ulink>) development release and KDE 3.5 (<ulink url='http://kde.org/announcements/announce-3.5.php'>http://kde.org/announcements/announce-3.5.php</ulink>) general release of popular desktop environments is available. </para>
+ <para> Early work from the Fedora Rendering Project is integrated into the desktop. This new project (<ulink url='http://fedoraproject.org/wiki/RenderingProject'>http://fedoraproject.org/wiki/RenderingProject</ulink>) is going to provide the technical foundations for advanced desktop interfaces based on OpenGL. </para>
</listitem>
<listitem>
- <para> GNOME Power Manager and GNOME Screensaver are available as a technology preview within this release. </para>
+ <para> Popular desktop environments GNOME and KDE have innovative new versions included in this release. The GNOME desktop is based on the 2.14 release (<ulink url='http://www.gnome.org/~davyd/gnome-2-14/'>http://www.gnome.org/~davyd/gnome-2-14/</ulink>), and the KDE 3.5 desktop is the general 3.5 release (<ulink url='http://kde.org/announcements/announce-3.5.php'>http://kde.org/announcements/announce-3.5.php</ulink>). </para>
</listitem>
<listitem>
- <para> Open<emphasis role='strong'/>Office.org 2.0 (<ulink url='http://www.openoffice.org/product/index.html/'>http://www.openoffice.org/product/index.html/</ulink>) release is included. Open<emphasis role='strong'/>Office.org now uses system versions for many of the libraries leading to increased performance and efficiency. </para>
+ <para> The latest versions of <emphasis role='strong'>GNOME Power Manager</emphasis> (<ulink url='http://www.gnome.org/projects/gnome-power-manager/'>http://www.gnome.org/projects/gnome-power-manager/</ulink>) and <emphasis role='strong'>GNOME Screensaver</emphasis>(<ulink url='http://live.gnome.org/GnomeScreensaver/'>http://live.gnome.org/GnomeScreensaver/</ulink>) provide new and integrated power management capabilities. </para>
</listitem>
<listitem>
- <para> Firefox 1.5(<ulink url='http://www.mozilla.com/firefox/releases/1.5.html'>http://www.mozilla.com/firefox/releases/1.5.html</ulink>) web browser with many new features is included in this release </para>
+ <para> The new <emphasis role='strong'>GNOME User Share</emphasis> facility provides simple and efficient file sharing. </para>
</listitem>
<listitem>
- <para> Pup, the package updater has been joined by Pirut, which is the replacement for system-config-packages providing comprehensive software package management using yum as a backend. </para>
+ <para> Software suspend (hibernate) capability is now provided for a wide variety of hardware. </para>
</listitem>
<listitem>
- <para> Beagle which provides a index based search interface, f-spot for photo management and tomboy, a note taking application has been added to this release. </para>
+ <para> The previous graphical software management utilities have been replaced with the first versions of a new generation of tools. This release includes <emphasis role='strong'>Pup</emphasis>, a simple interface for system updates, and <emphasis role='strong'>Pirut</emphasis>, a new package manager that replaces <code>system-config-packages</code>. These build on the <code>yum</code> utility, to provide consistent software installation and update facilities throughout the system. </para>
</listitem>
<listitem>
- <para> Support for Broadcom 43xx wireless chipsets (<ulink url='http://bcm43xx.berlios.de/'>http://bcm43xx.berlios.de/</ulink>) has been included in the kernel. </para>
+ <para> This release of Fedora includes Mono support for the first time, and Mono applications such as <emphasis role='strong'>Beagle</emphasis>, a desktop search interface; <emphasis role='strong'>F-Spot</emphasis>, a photo management utility; and <emphasis role='strong'>Tomboy</emphasis>, a note-taking application. </para>
</listitem>
<listitem>
- <para> I18N support has drastically improved through the use of SCIM language input framework which has replaced IIMF in this release </para>
+ <para> You can now enjoy enhanced multimedia support with version 0.10 of the <emphasis role='strong'>Gstreamer</emphasis> media framework. This milestone release brings major improvements in robustness, compatibility, and features, over previous versions of <emphasis role='strong'>Gstreamer</emphasis>. The <emphasis role='strong'>Totem</emphasis> movie player and other media software in this release have been updated to use the new framework. </para>
</listitem>
<listitem>
- <para> Gstreamer media framework 0.10 which brings major improvements in robustness and features has been included in this release. Totem uses this new version of Gstreamer now. Other media applications that use gstreamer is expected to be updated within the subsequent releases. </para>
+ <para> There is dramatically improved internationalization support with <emphasis role='strong'>SCIM</emphasis> in Fedora Core . The <emphasis role='strong'>SCIM</emphasis> language input framework provides an easy to use interface for inputting many different non-English languages. <emphasis role='strong'>SCIM</emphasis> replaces the <emphasis role='strong'>IIIMF</emphasis> system used in previous Fedora releases. </para>
+ </listitem>
+ <listitem>
+ <para> The default Web browser is <emphasis role='strong'>Firefox</emphasis> 1.5 (<ulink url='http://www.mozilla.com/firefox/releases/1.5.html'>http://www.mozilla.com/firefox/releases/1.5.html</ulink>), which has many new features for faster, safer, and more efficient browsing. </para>
+ </listitem>
+ <listitem>
+ <para> The office applications suite <emphasis role='strong'>OpenOffice.org</emphasis> 2.0 (<ulink url='http://www.openoffice.org/product/index.html'>http://www.openoffice.org/product/index.html</ulink>) now makes better use of general system libraries for increased performance and efficiency. </para>
+ </listitem>
+ <listitem>
+ <para> A large number of <emphasis role='strong'>GTK</emphasis> and <emphasis role='strong'>GNOME</emphasis> programs take advantage of the <emphasis role='strong'>Cairo</emphasis> 2D graphics library (<ulink url='http://cairographics.org/'>http://cairographics.org/</ulink>), included in this release, to provide streamlined attractive graphical interfaces. </para>
+ </listitem>
+ <listitem>
+ <para> There are new drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (<ulink url='http://bcm43xx.berlios.de/'>http://bcm43xx.berlios.de/</ulink>). </para>
+ </listitem>
+ <listitem>
+ <para> This release includes <code>libnotify</code>, a library that features simple and attractive notifications for the desktop. </para>
+ </listitem>
+ <listitem>
+ <para> Fedora Core now uses <code>gnome-mount</code>, a more efficient mechanism that replaces <code>fstab-sync</code>, and uses HAL to handle mounting. </para>
+ </listitem>
+ <listitem>
+ <para> Printing support is improved in this release with the inclusion of the <code>hplip</code> utility, which replaces <code>hpijs</code>. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Administration</title>
+ <para>Improvements for administrators and developers include: </para>
<itemizedlist>
<listitem>
- <para> Xen Virtualisation software and yum package manager are now well integrated within the Fedora installer. The installer interface is more streamlined. Remote logging and improved support for tracebacks is included. </para>
+ <para> The <emphasis role='strong'>Xen</emphasis> virtualization system has enhanced support. The tools to configure <emphasis role='strong'>Xen</emphasis> virtual machines on your Fedora Core system now use the standard graphical installation process, run as a window on your desktop. Fedora developers have also created <code>gnome-applet-vm</code>, which provides a simple virtual domains monitor applet, and <code>libvirt</code> (<ulink url='http://libvirt.org/'>http://libvirt.org/</ulink>), a library providing an API to use Xen virtualization capabilities. </para>
+ </listitem>
+ <listitem>
+ <para> The industry-leading <code>anaconda</code> installation system continues to evolve. New features for this release include remote logging and improved support for tracebacks. Package management in the installation system is now provided by <code>yum</code>. This enhancement is the first step in enabling access to Fedora Extras from within the installation process. </para>
+ </listitem>
+ <listitem>
+ <para> Version 2.2 of the <emphasis role='strong'>Apache</emphasis> HTTP server is now included. This release provides enhancements to authentication, database support, proxy facilities, and content filtering. </para>
+ </listitem>
+ <listitem>
+ <para> The latest generation of database servers are packaged in this release, including both <emphasis role='strong'>MySQL</emphasis> 5.0 and <emphasis role='strong'>PostgreSQL</emphasis> 8.1. </para>
+ </listitem>
+ <listitem>
+ <para> Several native Java programs are now available compiled with <code>GCJ</code>, such as the <emphasis role='strong'>Geronimo</emphasis> J2EE server and the <emphasis role='strong'>Apache Jakarta</emphasis> Project, in addition to the Java programs and development capabilities in the previous releases. </para>
</listitem>
<listitem>
- <para> System Tap (<ulink url='http://sourceware.org/systemtap/'>http://sourceware.org/systemtap/</ulink>) a instrumentation system for debugging and analysing performance bottle necks and Frysk (<ulink url='http://sourceware.org/frysk/'>http://sourceware.org/frysk/</ulink>), an execution analysis technology for monitoring running processes or threads is included within this release. </para>
+ <para> There are new tools for system monitoring and performance analysis. This release includes <emphasis role='strong'><ulink url='/SystemTap'>SystemTap</ulink>
+ </emphasis> (<ulink url='http://fedoraproject.org/wiki/SystemTap'>http://fedoraproject.org/wiki/SystemTap</ulink>), an instrumentation system for debugging and analyzing performance bottle necks, and <emphasis role='strong'>Frysk</emphasis> (<ulink url='http://fedoraproject.org/wiki/Frysk'>http://fedoraproject.org/wiki/Frysk</ulink>), an execution analysis technology for monitoring running processes or threads. </para>
+ </listitem>
+ <listitem>
+ <para> This release includes <code>system-config-cluster</code>, a utility that allows you to manage cluster configuration in a graphical setting. </para>
+ </listitem>
+ <listitem>
+ <para> The combination of <emphasis role='strong'>Kexec</emphasis> and <emphasis role='strong'>Kdump</emphasis> utilities provides modern crash dumping facilities and potential for faster bootup, bypassing the firmware on reboots. <emphasis role='strong'>Kexec</emphasis> loads a new kernel from a running kernel, and <emphasis role='strong'>Kdump</emphasis> can provide a memory dump of the previous kernel for debugging. </para>
+ </listitem>
+ <listitem>
+ <para> This release includes <code>iscsi-initiator-utils</code>, iSCSI daemon and utility programs that provide support for hardware using the iSCSI interface. </para>
</listitem>
</itemizedlist>
</section>
@@ -64,23 +105,26 @@
<title>System Level Changes</title>
<itemizedlist>
<listitem>
- <para> Xorg X11<emphasis role='strong'/>R7.0 has been included in this release. This is the first modular version, which helps in providing additional features and bug fixes at a faster pace. </para>
+ <para> X.org X11R7.0 is included in this release. The new modular architecture of R7.0 enables easier driver upgrades and simplifies development, opening the way for rapid improvement in Linux graphics. </para>
+ </listitem>
+ <listitem>
+ <para> The GCC 4.1 compiler is included, and the entire set of Fedora packages is built with this technology. This provides security and performance enhancements throughout the system. </para>
</listitem>
<listitem>
- <para> gcc 4.1 compiler is included and the entire set of Fedora packages is now build using this new compiler version which brings in new security and performance enhancements. </para>
+ <para> The kernels for this release are based on Linux 2.6.16. Refer to the section on the kernel in these release notes for other details. </para>
</listitem>
<listitem>
- <para> PCMCIA framework used by laptop and mobile devices had changed as with kernel version 2.6.13-rc1 onwards. The older pcmcia-cs package using the cardmgr/pcmcia service has been replaced with a new pcmciautils package where the PCMCIA devices are handled directly with the hotplug system using udev dynamically in this Fedora release. This increases both efficiency and performance of the system. More information about this changes are available from <ulink url='http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html'>http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html</ulink>. </para>
+ <para> The PCMCIA framework used by laptop and mobile devices has changed. The older <code>pcmcia-cs</code> package using the <code>cardmgr/pcmcia</code> service has been replaced with a new <code>pcmciautils</code> package. With <code>pcmciautils</code>, PCMCIA devices are handled directly and dynamically by the <code>hotplug</code> and <code>udev</code> subsystems. This update increases both efficiency and performance of the system. For more information about these changes, refer to <ulink url='http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html'>http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html</ulink>. </para>
</listitem>
<listitem>
- <para> SELinux implementation has undergone a major change with a switchover to <ulink url='http://serefpolicy.sourceforge.net/'>reference policy</ulink>. SELinux reference policy can support binary policy modules. It is possible now to move SELinux policies into individual packages and make it easier for users to ship site-specific policy customizations when required. This version also adds support for MCS (Multi Category System) enabled by default and MLS (Multi Level System) in addition to the the previous versions which have TE (Type Enforcement) which is enabled by default and RBAC (Role Based Access Contro) security sub systems within the SELinux framework. </para>
+ <para> SELinux implementation has undergone a major change, with a switch to the SELinux reference policy (<ulink url='http://serefpolicy.sourceforge.net/'>http://serefpolicy.sourceforge.net/</ulink>). The SELinux reference policy can support binary policy modules. It is now possible to move SELinux policies into individual packages, making it easier for users to ship site-specific policy customizations when required. This version also adds support for Multi-Category Security (MCS), enabled by default, and Multi-Level Security (MCS). SELinux continues to offer support for TE (Type Enforcement), enabled by default, and RBAC (Role-Based Access Control). Refer to the section on SELinux in these release notes for other details and links to SELinux resources on the Fedora Project pages. </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Road Map</title>
- <para>The proposed plans for Fedora in this version are available from <ulink url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>. </para>
+ <para>The proposed plans for the next release of Fedora are available at <ulink url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>. </para>
</section>
</section>
</article>
Index: PackageChanges.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/PackageChanges.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PackageChanges.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ PackageChanges.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,15 +1,45 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-PackageChanges">
+ <section>
<title>Package Changes</title>
- <important>
- <title><command>LinuxThreads</command> library is no longer available</title>
- <para>
- <command>LinuxThreads</command> was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely. </para>
- </important>
+ <para>
+ </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'>This list is automatically generated</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> This list is automatically generated. It is not a good choice for translation. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>This list was made using the <code>treediff</code> utility, ran as <code>treediff newtree oldtree</code> against the rawhide tree of 28 Feb. 2006. </para>
+ <para>For a list of which packages were updated since FC 4, refer to this page: </para>
+ <para>
+ <ulink url='http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages'>http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages</ulink>
+ </para>
+ <screen>New package adaptxAdaptXNew package aggAnti-Grain GeometryNew package amtuAbstract Machine Test Utility (AMTU)New package anthyJapanese character set input libraryNew package aspell-ruRussian dictionaries for Aspell.New package aspell-slSlovenian dictionaries for Aspell.New package aspell-srSerbian dictionaries for Aspell.New package avahiLocal network service discoveryNew package axisA SOAP implementation in JavaNew package beagleThe Beagle Search InfrastructureNew package bsfBean Scripting FrameworkNew package bshLightweight Scripting for JavaNew package cairoA vector graphics libraryNew package cairo-javaJava bindings for the Cairo libraryNew package castorAn open source data binding framework for JavaNew package concurrentUtility classes for concurrent Java programmingNew package dev86A real mode 80x86 assembler and linker.New package dhcdbdDHCP D-BUS daemon (dhcdbd) controls dhclient sessions with D-BUS, stores and presents DHCP options.New package ekigaA G!
nome based SIP/H323 teleconferencing applicationNew package eliloELILO linux boot loader for EFI-based systemsNew package evolution-sharpEvolution Data Server Mono BindingsNew package f-spotPhoto management applicationNew package fryskFrysk execution analysis toolNew package gecko-sharp2Gecko bindings for MonoNew package geronimo-specsGeronimo J2EE server J2EE specificationsNew package giflibLibrary for manipulating GIF format image filesNew package glib-javaBase Library for the Java-GNOME librariesNew package gmimeLibrary for creating and parsing MIME messagesNew package gnome-applet-vmSimple virtual domains monitor which embed themselves in the GNOME panelNew package gnome-mountMount replacement which uses HAL to do the mountingNew package gnome-power-managerGNOME Power ManagerNew package gnome-python2-desktopThe sources for additional PyGNOME Python extension modules for the GNOME desktop.New package gnome-screensaverGNOME SreensaverNew package gnome-user-shareGnome user!
file sharingNew package gnu-efiDevelopment Libraries and head!
ers fo
FINew package gpartA program for recovering corrupt partition tables.New package gsf-sharpMono bindings for libgsfNew package gstreamer-plugins-baseGStreamer streaming media framework base plug-insNew package gstreamer-plugins-goodGStreamer plug-ins with good code and licensingNew package gtk-sharpGTK+ and GNOME bindings for MonoNew package gtk-sharp2GTK+ and GNOME bindings for MonoNew package hplipHP Linux Imaging and Printing ProjectNew package hsqldbHsqldb Database EngineNew package icon-naming-utilsA script to handle icon names in desktop icon themesNew package icuInternational Components for UnicodeNew package imakeimake source code configuration and build systemNew package iscsi-initiator-utilsiSCSI daemon and utility programsNew package iso-codesISO code lists and translationsNew package jakarta-commons-codecJakarta Commons Codec PackageNew package jakarta-commons-daemonJakarta Commons Daemon PackageNew package jakarta-commons-discoveryJakarta Commons DiscoveryNew pac!
kage jakarta-commons-httpclientJakarta Commons HTTPClient PackageNew package javaccA parser/scanner generator for javaNew package jdomJava alternative to DOM and SAXNew package jgroupsToolkit for reliable multicast communication.New package jrefactoryJRefactory and Pretty PrintNew package kasumiAn anthy dictionary management tool.New package kexec-toolsThe kexec/kdump userspace component.New package lcmsColor Management SystemNew package libFSX.Org X11 libFS runtime libraryNew package libICEX.Org X11 libICE runtime libraryNew package libSMX.Org X11 libSM runtime libraryNew package libX11X.Org X11 libX11 runtime libraryNew package libXScrnSaverX.Org X11 libXss runtime libraryNew package libXTrapX.Org X11 libXTrap runtime libraryNew package libXauX.Org X11 libXau runtime libraryNew package libXawX.Org X11 libXaw runtime libraryNew package libXcompositeX.Org X11 libXcomposite runtime libraryNew package libXcursorX.Org X11 libXcursor runtime libraryNew package libXdamageX.Org X!
11 libXdamage runtime libraryNew package libXdmcpX.Org X11 lib!
Xdmcp
time libraryNew package libXevieX.Org X11 libXevie runtime libraryNew package libXextX.Org X11 libXext runtime libraryNew package libXfixesX.Org X11 libXfixes runtime libraryNew package libXfontX.Org X11 libXfont runtime libraryNew package libXfontcacheX.Org X11 libXfontcache runtime libraryNew package libXftX.Org X11 libXft runtime libraryNew package libXiX.Org X11 libXi runtime libraryNew package libXineramaX.Org X11 libXinerama runtime libraryNew package libXmuX.Org X11 libXmu/libXmuu runtime librariesNew package libXpX.Org X11 libXp runtime libraryNew package libXpmX.Org X11 libXpm runtime libraryNew package libXrandrX.Org X11 libXrandr runtime libraryNew package libXrenderX.Org X11 libXrender runtime libraryNew package libXresX.Org X11 libXres runtime libraryNew package libXtX.Org X11 libXt runtime libraryNew package libXtstX.Org X11 libXtst runtime libraryNew package libXvX.Org X11 libXv runtime libraryNew package libXvMCX.Org X11 libXvMC runtime libraryNew package lib!
Xxf86dgaX.Org X11 libXxf86dga runtime libraryNew package libXxf86miscX.Org X11 libXxf86misc runtime libraryNew package libXxf86vmX.Org X11 libXxf86vm runtime libraryNew package libchewingIntelligent phonetic input method library for Traditional ChineseNew package libdaemonlibrary for writing UNIX daemonsNew package libdmxX.Org X11 libdmx runtime libraryNew package libdrmlibdrm Direct Rendering Manager runtime libraryNew package libeventAbstract asynchronous event notification libraryNew package libfontencX.Org X11 libfontenc runtime libraryNew package libgdipluslibgdiplus: An Open Source implementation of the GDI+ APINew package libgpodLibrary to access the contents of an iPodNew package libgssapiGeneric Security Services Application Programming Interface LibraryNew package libiec61883Streaming library for IEEE1394New package liblbxutilX.Org X11 liblbxutil runtime libraryNew package libnlConvenience library for kernel netlink socketsNew package libnotifylibnotify notificati!
on libraryNew package liboilLibrary of Optimized Inner Loops, !
CPU op
ized functionsNew package liboldXX.Org X11 liboldX runtime libraryNew package libpfma performance monitoring library for Linux/ia64New package librtasLibraries to provide access to RTAS calls and RTAS events.New package libsemanageSELinux binary policy manipulation libraryNew package libsetransSELinux Translation libraryNew package libstdc++so7libstdc++.so.7 previewNew package libunwindAn unwinding library for ia64.New package libvirtLibrary providing an API to use the Xen virtualizationNew package libvte-javaWrapper library for GNOME VTENew package libxkbfileX.Org X11 libxkbfile runtime libraryNew package libxkbuiX.Org X11 libxkbui runtime libraryNew package luceneHigh-performance, full-featured text search engineNew package m17n-dbMultilingualization datafiles for m17n-libNew package m17n-libMultilingual text libraryNew package mesaMesa graphics librariesNew package mlocateAn utility for finding files by nameNew package mockobjectsJava MockObjects packageNew package monoa !
.NET runtime environmentNew package mysql-connector-odbcODBC driver for MySQLNew package mysqlclient14Backlevel MySQL shared libraries.New package nautilus-sendtoNautilus context menu for sending filesNew package nfs-utils-libNetwork File System Support LibraryNew package notify-daemonNotification DaemonNew package nsprNetscape Portable RuntimeNew package opalOpen Phone Abstraction LibraryNew package openCryptokiImplementation of Cryptoki v2.11 for IBM Crypto HardwareNew package openspSGML and XML parserNew package pcmciautilsPCMCIA utilities and initialization programsNew package perl-Net-IPPerl module for manipulation of IPv4 and IPv6 addressesNew package perl-String-CRC32Perl interface for cyclic redundency check generationNew package perl-XML-SimpleEasy API to maintain XML in PerlNew package pfmona performance monitoring tool for Linux/ia64New package php-pearPHP Extension and Application Repository frameworkNew package pirutPackage Installation, Removal and Update Tool!
sNew package prctlUtility to perform process operationsNew pac!
kage p
iroPython bindings for the cairo libraryNew package pykickstartA python library for manipulating kickstart filesNew package python-pyblockPython modules for dealing with block devicesNew package rhpxlPython library for configuring and running X.New package s390utilsLinux/390 specific utilities.New package salinfoSAL info tool.New package scimSmart Common Input Method platformNew package scim-anthySCIM IMEngine for anthy for Japanese inputNew package scim-chewingChewing Chinese input method for SCIMNew package scim-hangulHangul Input Method Engine for SCIMNew package scim-m17nSCIM IMEngine for m17n-libNew package scim-pinyinSmart Pinyin IMEngine for Smart Common Input Method platformNew package scim-qtimmSCIM input method module for QtNew package scim-tablesSCIM Generic Table IMEngineNew package squashfs-toolssquashfs utilitiesNew package system-config-clustersystem-config-cluster is a utility which allows you to manage cluster configuration in a graphical setting.New package!
systemtapInstrumentation SystemNew package tanukiwrapperJava Service WrapperNew package tog-pegasusOpenPegasus WBEM Services for LinuxNew package tomboyTomboy is a desktop note-taking application for Linux and Unix.New package velocityJava-based template engineNew package werken.xpathXPath implementation using JDOMNew package wpa_supplicantWPA/WPA2/IEEE 802.1X SupplicantNew package wsdl4jWeb Services Description Language Toolkit for JavaNew package xdocletXDoclet Attribute Orientated Programming FrameworkNew package xjavadocThe XJavaDoc engineNew package xmlrpcJava XML-RPC implementationNew package xorg-x11-appsX.Org X11 applicationsNew package xorg-x11-driversX.Org X11 driver installation packageNew package xorg-x11-drv-acecadXorg X11 acecad input driverNew package xorg-x11-drv-aiptekXorg X11 aiptek input driverNew package xorg-x11-drv-apmXorg X11 apm video driverNew package xorg-x11-drv-arkXorg X11 ark video driverNew package xorg-x11-drv-atiXorg X11 ati video driverNew !
package xorg-x11-drv-calcompXorg X11 calcomp input driverNew p!
ackage
rg-x11-drv-chipsXorg X11 chips video driverNew package xorg-x11-drv-cirrusXorg X11 cirrus video driverNew package xorg-x11-drv-citronXorg X11 citron input driverNew package xorg-x11-drv-cyrixXorg X11 cyrix video driverNew package xorg-x11-drv-digitaledgeXorg X11 digitaledge input driverNew package xorg-x11-drv-dmcXorg X11 dmc input driverNew package xorg-x11-drv-dummyXorg X11 dummy video driverNew package xorg-x11-drv-dynaproXorg X11 dynapro input driverNew package xorg-x11-drv-elo2300Xorg X11 elo2300 input driverNew package xorg-x11-drv-elographicsXorg X11 elographics input driverNew package xorg-x11-drv-evdevXorg X11 evdev input driverNew package xorg-x11-drv-fbdevXorg X11 fbdev video driverNew package xorg-x11-drv-fpitXorg X11 fpit input driverNew package xorg-x11-drv-glintXorg X11 glint video driverNew package xorg-x11-drv-hyperpenXorg X11 hyperpen input driverNew package xorg-x11-drv-i128Xorg X11 i128 video driverNew package xorg-x11-drv-i740Xorg X11 i740 video driverNe!
w package xorg-x11-drv-i810Xorg X11 i810 video driverNew package xorg-x11-drv-jamstudioXorg X11 jamstudio input driverNew package xorg-x11-drv-joystickXorg X11 joystick input driverNew package xorg-x11-drv-keyboardXorg X11 keyboard input driverNew package xorg-x11-drv-magellanXorg X11 magellan input driverNew package xorg-x11-drv-magictouchXorg X11 magictouch input driverNew package xorg-x11-drv-mgaXorg X11 mga video driverNew package xorg-x11-drv-microtouchXorg X11 microtouch input driverNew package xorg-x11-drv-mouseXorg X11 mouse input driverNew package xorg-x11-drv-mutouchXorg X11 mutouch input driverNew package xorg-x11-drv-neomagicXorg X11 neomagic video driverNew package xorg-x11-drv-nscXorg X11 nsc video driverNew package xorg-x11-drv-nvXorg X11 nv video driverNew package xorg-x11-drv-palmaxXorg X11 palmax input driverNew package xorg-x11-drv-penmountXorg X11 penmount input driverNew package xorg-x11-drv-renditionXorg X11 rendition video driverNew package xorg-x11-d!
rv-s3Xorg X11 s3 video driverNew package xorg-x11-drv-s3virgeX!
org X1
3virge video driverNew package xorg-x11-drv-savageXorg X11 savage video driverNew package xorg-x11-drv-siliconmotionXorg X11 siliconmotion video driverNew package xorg-x11-drv-sisXorg X11 sis video driverNew package xorg-x11-drv-sisusbXorg X11 sisusb video driverNew package xorg-x11-drv-spaceorbXorg X11 spaceorb input driverNew package xorg-x11-drv-summaXorg X11 summa input driverNew package xorg-x11-drv-tdfxXorg X11 tdfx video driverNew package xorg-x11-drv-tek4957Xorg X11 tek4957 input driverNew package xorg-x11-drv-tridentXorg X11 trident video driverNew package xorg-x11-drv-tsengXorg X11 tseng video driverNew package xorg-x11-drv-ur98Xorg X11 ur98 input driverNew package xorg-x11-drv-v4lXorg X11 v4l video driverNew package xorg-x11-drv-vesaXorg X11 vesa video driverNew package xorg-x11-drv-vgaXorg X11 vga video driverNew package xorg-x11-drv-viaXorg X11 via video driverNew package xorg-x11-drv-vmwareXorg X11 vmware video driverNew package xorg-x11-drv-voidXorg X11 void i!
nput driverNew package xorg-x11-drv-voodooXorg X11 voodoo video driverNew package xorg-x11-filesystemX.Org X11 filesystem layoutNew package xorg-x11-font-utilsX.Org X11 font utilitiesNew package xorg-x11-fontsX.Org X11 fontsNew package xorg-x11-proto-develX.Org X11 Protocol headersNew package xorg-x11-resutilsX.Org X11 X resource utilitiesNew package xorg-x11-serverX.Org X11 X serverNew package xorg-x11-server-utilsX.Org X11 X server utilitiesNew package xorg-x11-twmX.Org X11 twm window managerNew package xorg-x11-util-macrosX.Org X11 Autotools macrosNew package xorg-x11-utilsX.Org X11 X client utilitiesNew package xorg-x11-xauthX.Org X11 X authority utilitiesNew package xorg-x11-xbitmapsX.Org X11 application bitmapsNew package xorg-x11-xdmX.Org X11 xdm - X Display ManagerNew package xorg-x11-xfsX.Org X11 xfs font serverNew package xorg-x11-xfwpX.Org X11 X firewall proxyNew package xorg-x11-xinitX.Org X11 X Window System xinit startup scriptsNew package xorg-x11-xkb-utilsX.!
Org X11 xkb utilitiesNew package xorg-x11-xkbdataxkb data file!
s for
X.Org X11 X serverNew package xorg-x11-xsmX.Org X11 X Session ManagerNew package xorg-x11-xtrans-develX.Org X11 developmental X transport libraryRemoved package CannaRemoved package 4SuiteRemoved package MyODBCRemoved package apelRemoved package VFlib2Removed package anaconda-helpRemoved package aqhbciRemoved package cdicconfRemoved package fonts-xorgRemoved package gimp-gapRemoved package gnome-kerberosRemoved package gnomemeetingRemoved package hotplugRemoved package howlRemoved package hpijsRemoved package hpojRemoved package iiimfRemoved package iiimf-le-chinputRemoved package iiimf-le-xcinRemoved package libgal2Removed package libungifRemoved package lvm2-clusterRemoved package mod_jkRemoved package nvi-m17nRemoved package openh323Removed package openmotif21Removed package pcmcia-csRemoved package perl-FilterRemoved package perl-Filter-SimpleRemoved package perl-Parse-YappRemoved package perl-RPM2Removed package perl-Time-HiResRemoved package perl-XML-EncodingRemoved p!
ackage perl-libxml-ennoRemoved package python-twistedRemoved package sashRemoved package schedutilsRemoved package selinux-policy-targetedRemoved package selinux-policy-strictRemoved package slocateRemoved package struts11Removed package system-config-mouseRemoved package system-config-packagesRemoved package taipeifontsRemoved package w3c-libwwwRemoved package xinitrcRemoved package usbview</screen>
</section>
</article>
Index: PackageNotes.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/PackageNotes.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PackageNotes.xml 17 Feb 2006 00:49:51 -0000 1.2
+++ PackageNotes.xml 28 Feb 2006 17:25:26 -0000 1.3
@@ -1,39 +1,103 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
- <title>Package Notes</title>
+ <title>Temp</title>
</articleinfo>
- <section id="sn-PackageNotes">
+ <section>
<title>Package Notes</title>
- <para>The following sections contain information regarding packages that have undergone significant changes for Fedora Core . For easier access, they are generally organized using the same groups used in Anaconda. </para>
+ <para>The following sections contain information regarding software packages that have undergone significant changes for Fedora Core . For easier access, they are generally organized using the same groups that are shown in the installation system. </para>
+ <section>
+ <title>Kernel device, module loading, and hotplug changes</title>
+ <para>The hotplug and device handling subsystem has undergone significant changes in Fedora Core . The <code>udev</code> method now handles all module loading, both on system boot and for hotplugged devices. The <code>hotplug</code> package has been removed, as it is no longer needed. </para>
+ <para>Support for hotplug helpers via the <code>/etc/hotplug</code>, <code>/etc/hotplug.d</code>, and <code>/etc/dev.d</code> directories is deprecated, and may be removed in a future Fedora Core release. These helpers should be converted to <code>udev</code> rules. Please see <ulink url='http://www.reactivated.net/writing_udev_rules.html'>http://www.reactivated.net/writing_udev_rules.html</ulink> for examples. </para>
+ </section>
+ <section>
+ <title>Systemwide Search Changes</title>
+ <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'>
+ <code>mlocate</code> Has Replaced <code>slocate</code>
+ </emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> The new <code>mlocate</code> package provides the implementations of <code>/usr/bin/locate</code> and <code>/usr/bin/updatedb</code>. Previous Fedora releases included the <code>slocate</code> versions of these programs. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ <listitem>
+ <para> The <code>locate</code> command should be completely compatible. </para>
+ </listitem>
+ <listitem>
+ <para> The configuration file <code>/etc/updatedb.conf</code> is compatible. </para>
+ </listitem>
+ <listitem>
+ <para> Syntax errors that <code>slocate</code> would not detect are now reported. </para>
+ </listitem>
+ <listitem>
+ <para> The <code>DAILY_UPDATE</code> variable is not supported. </para>
+ </listitem>
+ <listitem>
+ <para> The <code>updatedb</code> command is <emphasis>not</emphasis> compatible, and custom scripts that use <code>updatedb</code> may have to be updated. </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>Mouse Configuration Utility Removed</title>
+ <para>The <code>system-config-mouse</code> configuration utility has been dropped in this release because <code>synaptic</code> and three-button mouse configuration is handled automatically. Serial mice are no longer supported. </para>
+ </section>
+ <section>
+ <title>NetworkManager</title>
+ <para>Fedora systems use <code>Network</code>
+ <code>Manager</code> to automatically detect, select, and configure wired and wireless network connections. Wireless network devices may require third-party software or manual configuration to activate after the installation process completes. For this reason, Fedora Core provides <code>Network</code>
+ <code>Manager</code> as an optional component. </para>
+ <para>Refer to <ulink url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink> for more information on how to install and enable <code>Network</code>
+ <code>Manager</code>. </para>
+ </section>
+ <section>
+ <title>Dovecot</title>
+ <para>Fedora Core includes a new version of the <code>dovecot</code> IMAP server software, which has has many changes in its configuration file. These changes are of particular importance to users upgrading from a previous release. Refer to <ulink url='http://wiki.dovecot.org/UpgradingDovecot'>http://wiki.dovecot.org/UpgradingDovecot</ulink> for more information on the changes. </para>
+ </section>
+ <section>
+ <title>Kudzu</title>
+ <para>The <code>kudzu</code> utility, <code>libkudzu</code> library, and <code>/etc/sysconfig/hwconf</code> hardware listing are all deprecated, and will be removed in a future release of Fedora Core. Applications which need to probe for available hardware should be ported to use the HAL library. More information on HAL is available at <ulink url='http://freedesktop.org/wiki/Software/hal'>http://freedesktop.org/wiki/Software/hal</ulink>. </para>
+ </section>
+ <section>
+ <title>No automatic fstab editing for removable media</title>
+ <para>The <code>fstab-sync</code> facility has been removed. In Fedora Core , the <code>fstab-sync</code> program is removed in favor of desktop specific solutions for mounting removable media. Entries for hotplug devices or inserted media are no longer automatically added to the <code>/etc/fstab</code> file. Command-line users may migrate to <code>gnome-mount</code>, which provides similar functionality. </para>
+ </section>
+ <section>
+ <title>GnuCash</title>
+ <para>The PostgreSQL backend for <emphasis role='strong'>GnuCash</emphasis> has been removed, as it is unmaintained upstream, does not support the full set of <emphasis role='strong'>GnuCash</emphasis> features, and can lead to crashes. Users who use the PostgreSQL backend should load their data and save it as an XML file <emphasis role='strong'>before</emphasis> upgrading <emphasis role='strong'>GnuCash</emphasis>. </para>
+ </section>
+ <section>
+ <title>Mozilla</title>
+ <para>The <emphasis role='strong'>Mozilla</emphasis> application suite is deprecated. It is shipped in Fedora Core and applications can expect to build against <code>mozilla-devel</code>, however it will be removed in a future release of Fedora Core. </para>
+ </section>
+ <section>
+ <title>libstc++ preview</title>
+ <para>The <code>libstdc++so7</code> package has been added. This package contains a preview of the GNU Standard C++ Library from <code>libstdcxx_so_7-branch</code>. It is considered experimental and unsupported. Do not build any production software against it, as its ABI and so-version will change in future upgrades. To build software using this library, invoke <code>g++-libstdc++so_7</code> instead of <code>g++</code>. </para>
+ </section>
<section>
- <title>Basic Components</title>
- <para>This section contains information related to basic system components. </para>
- <section>
- <title>Mouse Configuration Utility Removed</title>
- <para>The <emphasis role='strong'>system-config-mouse</emphasis> configuration utility has been dropped in this release because synaptic and 3 button mouse configuration is being done automatically. Serial mice are no longer supported. </para>
- </section>
- <section>
- <title>Screensavers Not Installed by Default</title>
- <para>Screensavers not installed by default anymore? Explain why and provide commands to install them. </para>
- </section>
- <section>
- <title>NetworkManager</title>
- <para>Because it is not possible to test <ulink url='/NetworkManager'>NetworkManager</ulink> in all configurations, it is not enabled by default in Fedora Core . </para>
- <para>Refer to this page for information about enabling this application: </para>
- <para>
- <ulink url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink>
- </para>
- </section>
- <section>
- <title>Dovecot</title>
- <para>This release of Fedora Core has a new version of the Dovecot IMAP server software which has has many changes in its configuration file. These changes are of importance especially to users upgrading from a previous release. Refer to <ulink url='http://wiki.dovecot.org/UpgradingDovecot'>http://wiki.dovecot.org/UpgradingDovecot</ulink> for more information on the changes. </para>
- <para>
- </para>
- </section>
+ <title>LinuxThreads support removed</title>
+ <para>The LinuxThreads library is no longer available. LinuxThreads was deprecated in Fedora Core 4 and is no longer available in this release. The Native POSIX Threading Library (NPTL), which has been the default threading library since Red Hat Linux 9, has replaced LinuxThreads completely. </para>
</section>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="PackageNotesJava.xml" xpointer="element(sn-PackageNotesJava)" />
</section>
</article>
Index: Printing.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Printing.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Printing.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Printing.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,16 +1,36 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Printing">
- <title>Printing</title>
-<!-- <para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
- <para>Beat writers: this is where you want to fill in with instructions -->
-<!-- about how to post relevant information. Any questions that come up can -->
-<!-- be taken to a bugzilla report for discussion to resolution, or to -->
-<!-- fedora-docs-list for wider discussions. </para> -->
- <para><emphasis>No changes to report.</emphasis></para>
+ <section>
+ <title>Docs/Beats/Printing</title>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>/!\</phrase>
+ </textobject>
+ </inlinemediaobject> REMOVE ME Before Publishing - Beat Comment </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page.</para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions.</para>
+ </td>
+ </tr>
+ </table>
</section>
</article>
Index: ProjectOverview.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ProjectOverview.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ProjectOverview.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ProjectOverview.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,48 +1,74 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ProjectOverview">
+ <section>
<title>An Overview of the Fedora Project</title>
- <para>The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community. </para>
+ <para>The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule available at <ulink url='http://fedora.redhat.com/About/schedule/'>http://fedora.redhat.com/About/schedule/</ulink>. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community. </para>
<para>For more information, refer to the Fedora Project website: </para>
<para>
<ulink url='http://fedora.redhat.com/'>http://fedora.redhat.com/</ulink>
</para>
- <para>Your participation is welcome. See <ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink> for details. </para>
- <para>For communication in the Fedora Project look at <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
+ <para>The Fedora Project is driven by the individuals that contribute to it. As a tester, developer, documenter or translator, you can make a difference. See <ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink> for details. </para>
+ <para>This page explains the channels of communication for Fedora users and contributors: </para>
+ <para>
+ <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
<para>In addition to the website, the following mailing lists are available: </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='mailto:fedora-list at redhat.com'>fedora-list at redhat.com</ulink> - For users of Fedora Core releases </para>
- </listitem>
- <listitem>
- <para>
- <ulink url='mailto:fedora-test-list at redhat.com'>fedora-test-list at redhat.com</ulink> - For testers of Fedora Core test releases </para>
- </listitem>
- <listitem>
- <para>
- <ulink url='mailto:fedora-devel-list at redhat.com'>fedora-devel-list at redhat.com</ulink> - For developers, developers, developers </para>
- </listitem>
- <listitem>
- <para>
- <ulink url='mailto:fedora-docs-list at redhat.com'>fedora-docs-list at redhat.com</ulink> - For participants of the Documentation Project </para>
- </listitem>
- </itemizedlist>
- <para>To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <listname>-request (where <listname> is one of the above list names.) </para>
- <para>Alternately, you can subscribe through the Web interface: </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url='mailto:fedora-list at redhat.com'>fedora-list at redhat.com</ulink> — For users of Fedora Core releases </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url='mailto:fedora-test-list at redhat.com'>fedora-test-list at redhat.com</ulink> — For testers of Fedora Core test releases </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url='mailto:fedora-devel-list at redhat.com'>fedora-devel-list at redhat.com</ulink> — For developers, developers, developers </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url='mailto:fedora-docs-list at redhat.com'>fedora-docs-list at redhat.com</ulink> — For participants of the Documentation Project </para>
+ </listitem>
+ </itemizedlist>
+ <para>To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <emphasis><listname>-request</emphasis>, where <emphasis><listname></emphasis> is one of the above list names. </para>
+ <para>Alternately, you can subscribe to Fedora mailing lists through the Web interface: </para>
<para>
<ulink url='http://www.redhat.com/mailman/listinfo/'>http://www.redhat.com/mailman/listinfo/</ulink>
</para>
- <para>The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one. </para>
- <para>To talk with other Fedora Project participants via IRC, access freenode IRC network. Refer to the freenode website (<ulink url='http://www.freenode.net/'>http://www.freenode.net/</ulink>) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages and at <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
- <para>In order to talk on the #fedora channel, you will need to register your nickname (nick). Instructions are given when you /join the channel. </para>
- <important>
- <title>IRC Content is Uncontrolled</title>
- <para> Red Hat has no control over the Fedora Project IRC channels or their content. </para>
- </important>
+ <para>The Fedora Project also uses several IRC (Internet Relay Chat) channels. IRC is a real-time, text-based form of communication, similar to Instant Messaging. With it, you may have conversations with multiple people in an open channel, or chat with someone privately one-on-one. </para>
+ <para>To talk with other Fedora Project participants via IRC, access the Freenode IRC network. Refer to the Freenode website (<ulink url='http://www.freenode.net/'>http://www.freenode.net/</ulink>) for more information. </para>
+ <para>Fedora Project participants frequent the <code>#fedora</code> channel on the Freenode network, whilst Fedora Project developers may often be found on the <code>#fedora-devel</code> channel. Some of the larger projects may have their own channels as well; this information may be found on the webpage for the project, and at <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
+ <para>In order to talk on the <code>#fedora</code> channel, you will need to register your nickname, or <emphasis>nick</emphasis>. Instructions are given when you <code>/join</code> the channel. </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'>IRC Channels</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Fedora Foundation or Red Hat has no control over the Fedora Project IRC channels or their content. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
</section>
</article>
Index: Samba.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Samba.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Samba.xml 20 Feb 2006 19:01:04 -0000 1.2
+++ Samba.xml 28 Feb 2006 17:25:26 -0000 1.3
@@ -1,37 +1,15 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Samba">
- <title>Samba</title>
- <note>
- <title>Content temporarily removed</title>
- <para>
- This section has been removed for the Fedora Core 5 test3 publication of
- these release notes that is happening under the Opencontent Public
- License (OPL), as specified in the <xref linkend="legalnotice"/>. We
- were not able to obtain permission from the contributor of this content
- in time for publication. This or similar content is going to return for
- the Fedora Core 5 final release.
- </para>
- </note>
-<!--
- <section>
+ <section>
<title>Samba (Windows Compatibility)</title>
- <para>This section contains information related to Samba, the suite of software that enables Linux to interact with Microsoft Windows systems. </para>
+ <para>This section contains information related to Samba, the suite of software Fedora uses to interact with Microsoft Windows systems. </para>
<section>
- <title>SMB Browsing</title>
- <para>Browsing of Windows shares (also known as SMB browsing) is now possible. In releases prior to Fedora Core 5, the firewall prevented the proper function of SMB browsing. With the addition of <command>ip_conntrack_netbios_ns</command> kernel module to the 2.6.14 kernel and corresponding enhancements to <command>system-config-securitylevel</command>, the firewall now properly tracks SMB browse broadcasts. </para>
- <section>
- <title>Samba Configuration using SWAT</title>
- <para>Samba-SWAT, is still required for ease of use of Samba. Once installed you can access it by opening a web-browser and navigating to <emphasis><ulink url='http://localhost:901'>http://localhost:901</ulink>
- </emphasis> replacing <emphasis>localhost</emphasis> with the name of the computer on which <emphasis>Samba</emphasis> is installed. </para>
- <para>For more information about SWAT navigate here, <ulink url='http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html'>http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html</ulink>
- </para>
- </section>
- </section>
- </section>-->
+ <title>Windows Network Browsing</title>
+ <para>Fedora can now browse Windows shares, a feature known as SMB browsing. In releases prior to Fedora Core , the firewall prevented the proper function of SMB browsing. With the addition of the <code>ip_conntrack_netbios_ns</code> kernel module to the 2.6.14 kernel, and corresponding enhancements to <emphasis role='strong'>system-config-securitylevel</emphasis>, the firewall now properly handles SMB broadcasts and permits network browsing. </para>
+ </section>
</section>
</article>
Index: Security.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Security.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Security.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Security.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,75 +1,68 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Security">
+ <section>
<title>Security</title>
<para>This section highlights various security items from Fedora Core. </para>
<section>
<title>General Information</title>
- <para>General introduction to the many proactive security features in Fedora, current status and policies is available from this page: </para>
- <para>
- <ulink url='http://fedoraproject.org/wiki/Security'>http://fedoraproject.org/wiki/Security</ulink>
- </para>
+ <para>A general introduction to the many proactive security features in Fedora, current status and policies is available at <ulink url='http://fedoraproject.org/wiki/Security'>http://fedoraproject.org/wiki/Security</ulink>. </para>
</section>
<section>
<title>What's New</title>
<section>
- <title>PAM Module Deprecation</title>
+ <title>PAM module Deprecation</title>
<para>
- <command>Pam_stack</command> is deprecated in this release. </para>
- <para>Linux-PAM 0.78 and later contains the include directive which obsoletes the <command>pam_stack</command> module. <command>pam_stack</command> module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it. </para>
- <important>
- <title>Upgraded installations using older PAM stacks need manual intervention</title>
- <para> When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration fiels are created as <command>.rpmnew</command> files. Such service configurations must be fixed so the <command>pam_stack</command> module is not used. Refer to the <command>.rpmnew</command> files for the actual changes needed. </para>
+ <code>Pam_stack</code> is deprecated in this release. Linux-PAM 0.78 and later contains the <code>include</code> directive which obsoletes the <code>pam_stack</code> module. <code>pam_stack</code> module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it. </para>
+ <itemizedlist>
+ <listitem>
+ <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'>Upgrading and PAM Stacks</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are <emphasis>not</emphasis> replaced when new packages are installed. Instead, the new configuration files are created as <code>.rpmnew</code> files. Such service configurations must be fixed so the <code>pam_stack</code> module is not used. Refer to the <code>.rpmnew</code> files for the actual changes needed. </para>
+ </td>
+ </tr>
+ </table>
<screen>diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew</screen>
- </important>
- <para>Example /etc/pam.d/login: </para>
- <screen>
-<computeroutput># OLD VERSION
-#%PAM-1.0
-auth required pam_securetty.so
-auth required pam_stack.so service=system-auth
-auth required pam_nologin.so
-account required pam_stack.so service=system-auth
-password required pam_stack.so service=system-auth
-# pam_selinux.so close should be the first session rule
-session required pam_selinux.so close
-session required pam_stack.so service=system-auth
-session required pam_loginuid.so
-session optional pam_console.so
-# pam_selinux.so open should be the last session rule
-session required pam_selinux.so open</computeroutput>
- </screen>
- <screen>
-<computeroutput># NEW VERSION
-#%PAM-1.0
-auth required pam_securetty.so
-auth include system-auth
-# no module should remain after 'include' if 'sufficient' might
-# be used in the included configuration file
-# pam_nologin moved to account phase - it's more appropriate there
-# other modules might be moved before the system-auth 'include'
-account required pam_nologin.so
-account include system-auth
-password include system-auth
-# pam_selinux.so close should be the first session rule
-session required pam_selinux.so close
-session include system-auth
-# the system-auth config doesn't contain sufficient modules
-# in the session phase
-session required pam_loginuid.so
-session optional pam_console.so
-# pam_selinux.so open should be the last session rule
-session required pam_selinux.so open</computeroutput>
- </screen>
+ </listitem>
+ </itemizedlist>
+ <para>The following example shows the <code>/etc/pam.d/login</code> configuration file in its original form using <code>pam_stack</code>, and then revised with the <code>include</code> directive. </para>
+ <itemizedlist>
+ <listitem>
+ <screen>#%PAM-1.0auth required pam_securetty.soauth required pam_stack.so service=system-authauth required pam_nologin.soaccount required pam_stack.so service=system-authpassword required pam_stack.so service=system-auth# pam_selinux.so close should be the first session rulesession required pam_selinux.so closesession required pam_stack.so service=system-authsession required pam_loginuid.sosession optional pam_console.so# pam_selinux.so open should be the last session rulesession required pam_selinux.so open</screen>
+ <screen>#%PAM-1.0auth required pam_securetty.soauth include system-auth# no module should remain after 'include' if 'sufficient' might# be used in the included configuration file# pam_nologin moved to account phase - it's more appropriate there# other modules might be moved before the system-auth 'include'account required pam_nologin.soaccount include system-authpassword include system-auth# pam_selinux.so close should be the first session rulesession required pam_selinux.so closesession include system-auth# the system-auth config doesn't contain sufficient modules# in the session phasesession required pam_loginuid.sosession optional pam_console.so# pam_selinux.so open should be the last session rulesession required pam_selinux.so open</screen>
+ </listitem>
+ </itemizedlist>
</section>
<section>
<title>Buffer Overflow detection and variable reordering</title>
- <para>All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called <command>fstack-protecter</command>. <command>fstack-protector</command> puts a canary value on the stack of <emphasis>key</emphasis> functions, just before the return address and just before returning from that value. Then the canary value is verified, and if there was a buffer overflow, the canary will no longer match and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature written by Red Hat developers as a rewritten implementation of the IBM <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>ProPolice/SSP</ulink> feature and available as part of GCC 4.1 compiler used in Fedora Core . </para>
- <para>This is in addition to using <command>FORTIFY_SOURCE</command> from Fedora Core 4 onwards. </para>
+ <para>All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called <code>fstack-protector</code>. <code>fstack-protector</code> places a canary value on the stack of functions containing a local character array. Before returning from a protected function, the canary value is verified. If there was a buffer overflow, the canary will no longer match the expected value, aborting the program. The canary value is random each time the application is started, making remote exploitation very difficult. The <code>fstack-protector</code> feature does not protect against heap-based buffer overflows. </para>
+ <para>This is a security feature written by Red Hat developers, implementing the IBM <ulink url='/ProPolice'>ProPolice</ulink>/SSP feature. For more information about <ulink url='/ProPolice'>ProPolice</ulink>/SSP, refer to <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>http://www.research.ibm.com/trl/projects/security/ssp/</ulink>. This feature is available as part of the GCC 4.1 compiler used in Fedora Core . </para>
+ <para>The <code>FORTIFY_SOURCE</code> security feature for <code>gcc</code> and <code>glibc</code> introduced in Fedora Core 4 remains available. For more information about security features in Fedora, refer to <ulink url='http://fedoraproject.org/wiki/Security/Features'>http://fedoraproject.org/wiki/Security/Features</ulink>. </para>
+ <para>
+ </para>
+ <para>
+ <ulink url='/CategorySecurity'>CategorySecurity</ulink>
+ </para>
</section>
</section>
</section>
Index: SecuritySELinux.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/SecuritySELinux.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SecuritySELinux.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ SecuritySELinux.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,77 +1,42 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>SELinux</title>
- <para>The new SELinux project pages have troubleshooting tips, explanations, and pointers to documentation and references: </para>
+ <para>The new SELinux project pages have troubleshooting tips, explanations, and pointers to documentation and references. Some useful links include the following: </para>
<itemizedlist>
<listitem>
- <para> New SELinux project pages: </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='http://fedoraproject.org/wiki/SELinux'>http://fedoraproject.org/wiki/SELinux</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ <para> New SELinux project pages: <ulink url='http://fedoraproject.org/wiki/SELinux'>http://fedoraproject.org/wiki/SELinux</ulink>
+ </para>
</listitem>
<listitem>
- <para> If you are having trouble: </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='http://fedoraproject.org/wiki/SELinux/Troubleshooting'>http://fedoraproject.org/wiki/SELinux/Troubleshooting</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ <para> Troubleshooting tips: <ulink url='http://fedoraproject.org/wiki/SELinux/Troubleshooting'>http://fedoraproject.org/wiki/SELinux/Troubleshooting</ulink>
+ </para>
</listitem>
<listitem>
- <para> Questions? </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='http://fedora.redhat.com/docs/selinux-faq/'>http://fedora.redhat.com/docs/selinux-faq/</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ <para> Frequently Asked Questions: <ulink url='http://fedora.redhat.com/docs/selinux-faq/'>http://fedora.redhat.com/docs/selinux-faq/</ulink>
+ </para>
</listitem>
<listitem>
- <para> Looking for a list of SELinux commands? </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='http://fedoraproject.org/wiki/SELinux/Commands'>http://fedoraproject.org/wiki/SELinux/Commands</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ <para> Listing of SELinux commands: <ulink url='http://fedoraproject.org/wiki/SELinux/Commands'>http://fedoraproject.org/wiki/SELinux/Commands</ulink>
+ </para>
</listitem>
<listitem>
- <para> Want to know which domains are confined? </para>
- <itemizedlist>
- <listitem>
- <para>
- <ulink url='http://fedoraproject.org/wiki/SELinux/Domains'>http://fedoraproject.org/wiki/SELinux/Domains</ulink>
- </para>
- </listitem>
- </itemizedlist>
+ <para> Details of confined domains: <ulink url='http://fedoraproject.org/wiki/SELinux/Domains'>http://fedoraproject.org/wiki/SELinux/Domains</ulink>
+ </para>
</listitem>
</itemizedlist>
<section>
<title>Multi Category Security (MCS)</title>
- <para>General use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with <emphasis>categories</emphasis>. For example, <command>Company_Confidential</command>, <command>CEO_EYES_ONLY</command>, or <command>Sysadmin_Passwords</command>. </para>
- <para>For more information, you can read this article from the creator of MCS: </para>
- <para>
- <ulink url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>
- </para>
+ <para>MCS is a general-use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with <emphasis>categories</emphasis>. Categories might include <code>Company_Confidential</code>, <code>CEO_EYES_ONLY</code>, or <code>Sysadmin_Passwords</code>. For more information about MCS, refer to <ulink url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>, an article by the author. </para>
<section>
<title>Multilevel Security (MLS)</title>
- <para>A specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object (a document file) can have the security level of <command>{ Secret, ProjectMeta }</command>, where <command>Secret</command> is the sensitivity level, and the <command>ProjectMeta</command> is the category. </para>
- <para>Refer to this technical article for more information: </para>
+ <para>MLS is a specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object such as a document file can have the security level of <code>{ Secret, ProjectMeta }</code>, where <code>Secret</code> is the sensitivity level, and <code>ProjectMeta</code> is the category. For more information about MLS, refer to <ulink url='http://james-morris.livejournal.com/5020.html'>http://james-morris.livejournal.com/5020.html</ulink>. </para>
<para>
- <ulink url='http://james-morris.livejournal.com/5020.html'>http://james-morris.livejournal.com/5020.html</ulink>
+ <ulink url='/CategorySecurity'>CategorySecurity</ulink>
</para>
</section>
</section>
Index: ServerTools.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/ServerTools.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ServerTools.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ ServerTools.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,33 +1,43 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-ServerTools">
- <title>Server Tools</title>
+ <section>
+ <title>Docs/Beats/ServerTools</title>
<para>This section highlights changes and additions to the various GUI server and system configuration tools in Fedora Core. </para>
<section>
<title>system-config-printer</title>
<section>
<title>SMB Browsing Outside Local Network</title>
- <para>Browsing for Samba print shares across subnets is now possible. In addition, if at least one WINS server has been specified in <emphasis>/etc/samba/smb.conf</emphasis>, the first address specified is used when browsing. </para>
+ <para>You can now browse for Samba print shares across subnets. If you specify at least one WINS server in <code>/etc/samba/smb.conf</code>, the first address is used when browsing. </para>
</section>
<section>
<title>Kerberos Support for SMB Printers</title>
- <para>The system-config-printer application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and <emphasis>/usr/sbin/printconf-gui</emphasis> must be launched via sudo. No username and password is stored in <emphasis>/etc/cups/printers.conf</emphasis>. Printing is still possible if the SMB print queue permits anonymous printing. </para>
+ <para>The <emphasis role='strong'>system-config-printer</emphasis> application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and launch the printer configuration tool. Select <emphasis>System</emphasis>><emphasis>Administration</emphasis>><emphasis>Printing</emphasis> from the main menu, or use the following command: </para>
+ <itemizedlist>
+ <listitem>
+ <screen>su -c 'system-config-printer' </screen>
+ </listitem>
+ </itemizedlist>
+ <para>No username and password is stored in <code>/etc/cups/printers.conf</code>. Printing is still possible if the SMB print queue permits anonymous printing. </para>
</section>
</section>
<section>
<title>system-config-securitylevel</title>
<section>
<title>Trusted Service Additions</title>
- <para>Samba is now listed in the "Trusted services" list and can thus be enabled to permit the firewall to pass SMB traffic. </para>
+ <para>Samba is now listed in the <emphasis>Trusted services</emphasis> list. To permit the firewall to pass SMB traffic, enable this option. </para>
</section>
<section>
<title>Port Ranges</title>
- <para>When defining "Other Ports" in the <command>system-config-securitylevel</command> tool, port ranges can now be specified. For example, specifying "6881-6999:tcp" results in the addition of the following line to <command>/etc/sysconfig/iptables</command>: </para>
+ <para>When you define <emphasis>Other Ports</emphasis> in the <emphasis role='strong'>system-config-securitylevel</emphasis> tool, you may now specify port ranges. For example, if you specify <code>6881-6999:tcp</code>, the following line is added to <code>/etc/sysconfig/iptables</code>: </para>
+ <itemizedlist>
+ <listitem>
<screen>A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 -j ACCEPT </screen>
+ </listitem>
+ </itemizedlist>
</section>
</section>
</section>
Index: SystemDaemons.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/SystemDaemons.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SystemDaemons.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ SystemDaemons.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,21 +1,41 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-SystemDaemons">
- <title>System Daemons</title>
-<!-- <para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
- <para>Beat writers: this is where you want to fill in with instructions -->
-<!-- about how to post relevant information. Any questions that come up can -->
-<!-- be taken to a bugzilla report for discussion to resolution, or to -->
-<!-- fedora-docs-list for wider discussions. </para> -->
- <para><emphasis>No changes to report.</emphasis>
+ <section>
+ <title>Docs/Beats/SystemDaemons</title>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>/!\</phrase>
+ </textobject>
+ </inlinemediaobject> REMOVE ME Before Publishing - Beat Comment </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page.</para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions.</para>
+ </td>
+ </tr>
+ </table>
+ <para>
</para>
</section>
<section>
<title>System Services</title>
- <para><emphasis>No changes to report.</emphasis></para>
</section>
</article>
Index: WebServers.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/WebServers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- WebServers.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ WebServers.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,46 +1,88 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-WebServers">
+ <section>
<title>Web Servers</title>
<para>This section contains information on Web-related applications. </para>
<section>
<title>httpd</title>
- <para>Version 2.2 of the Apache HTTP Server is now included in Fedora Core. This release brings a number of improvements since the 2.0 series, including: </para>
+ <para>Fedora Core now includes version 2.2 of the Apache HTTP Server. This release brings a number of improvements over the 2.0 series, including: </para>
<itemizedlist>
<listitem>
- <para> greatly improved caching modules (<command>mod_cache</command>, <command>mod_disk_cache</command>, <command>mod_mem_cache</command>) </para>
+ <para> greatly improved caching modules (<code>mod_cache</code>, <code>mod_disk_cache</code>, <code>mod_mem_cache</code>) </para>
</listitem>
<listitem>
- <para> refactored authentication and authorization support </para>
+ <para> a new structure for authentication and authorization support, replacing the security modules provided in previous versions </para>
</listitem>
<listitem>
- <para> support for proxy load balancing (<command>mod_proxy_balance</command>) </para>
+ <para> support for proxy load balancing (<code>mod_proxy_balance</code>) </para>
</listitem>
<listitem>
- <para> large file support for 32-bit platforms (including support for >2Gb request bodies) </para>
- </listitem>
- <listitem>
- <para> new modules <command>mod_dbd</command> and <command>mod_filter</command> bring SQL database support and enhanced filtering </para>
+ <para> large file support for 32-bit platforms (including support for serving files larger than 2Gb) </para>
+ </listitem>
+ <listitem>
+ <para> new modules <code>mod_dbd</code> and <code>mod_filter</code>, which bring SQL database support and enhanced filtering </para>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/star_on.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>{*}</phrase>
+ </textobject>
+ </inlinemediaobject>
+ <emphasis role='strong'>Upgrading and Security Modules</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> If you upgrade from a previous version of <code>httpd</code>, update your server configuration to use the new authentication and authorization modules. Refer to the page listed below for more details. </para>
+ </td>
+ </tr>
+ </table>
</listitem>
</itemizedlist>
- <para>The following changes have been made to the default <command>httpd</command> configuration: </para>
+ <para>The following changes have been made to the default <code>httpd</code> configuration: </para>
<itemizedlist>
<listitem>
- <para> the <command>mod_cern_meta</command> and <command>mod_asis</command> modules are no longer loaded by default </para>
+ <para> The <code>mod_cern_meta</code> and <code>mod_asis</code> modules are no longer loaded by default. </para>
</listitem>
<listitem>
- <para> the <command>mod_ext_filter</command> module is now loaded by default </para>
+ <para> The <code>mod_ext_filter</code> module is now loaded by default. </para>
+ <table>
+ <caption/>
+ <tr>
+ <td>
+ <para>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata width='15' fileref='/wiki/ntheme/img/star_on.png' depth='15'/>
+ </imageobject>
+ <textobject>
+ <phrase>{*}</phrase>
+ </textobject>
+ </inlinemediaobject>
+ <emphasis role='strong'>Third-party Modules</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Any third-party modules compiled for <code>httpd</code> 2.0 must be rebuilt for <code>httpd</code> 2.2. </para>
+ </td>
+ </tr>
+ </table>
</listitem>
</itemizedlist>
- <para>Any third-party modules compiled for <command>httpd</command> 2.0 must be rebuilt for <command>httpd</command> 2.2. </para>
- <para>Any existing configuration files might need adapting for 2.2. For
- more information, refer to
- <ulink url='http://httpd.apache.org/docs/2.2/upgrading.html'>http://httpd.apache.org/docs/2.2/upgrading.html</ulink>.
- </para>
+ <para>For more information on upgrading existing installations, refer to <ulink url='http://httpd.apache.org/docs/2.2/upgrading.html'>http://httpd.apache.org/docs/2.2/upgrading.html</ulink>. </para>
</section>
<section>
<title>php</title>
@@ -57,68 +99,68 @@
<itemizedlist>
<listitem>
<para>
- <command>date</command>, <command>hash</command>, and <command>Reflection</command> (built-in with the php package) </para>
+ <code>date</code>, <code>hash</code>, and <code>Reflection</code> (built-in with the <code>php</code> package) </para>
</listitem>
<listitem>
<para>
- <command>pdo</command> and <command>pdo_psqlite</command> (in the <command>php-pdo</command> package) </para>
+ <code>pdo</code> and <code>pdo_psqlite</code> (in the <code>php-pdo</code> package) </para>
</listitem>
<listitem>
<para>
- <command>pdo_mysql</command> (in the <command>php-mysql</command> package) </para>
+ <code>pdo_mysql</code> (in the <code>php-mysql</code> package) </para>
</listitem>
<listitem>
<para>
- <command>pdo_pgsql</command> (in the <command>php-pgsql</command> package) </para>
+ <code>pdo_pgsql</code> (in the <code>php-pgsql</code> package) </para>
</listitem>
<listitem>
<para>
- <command>pdo_odbc</command> (in the <command>php-odbc</command> package) </para>
+ <code>pdo_odbc</code> (in the <code>php-odbc</code> package) </para>
</listitem>
<listitem>
<para>
- <command>xmlreader</command> and <command>xmlwriter</command> (in the <command>php-xml</command> package) </para>
+ <code>xmlreader</code> and <code>xmlwriter</code> (in the <code>php-xml</code> package) </para>
</listitem>
</itemizedlist>
<para>The following extension modules are no longer built: </para>
<itemizedlist>
<listitem>
<para>
- <command>dbx</command>
+ <code>dbx</code>
</para>
</listitem>
<listitem>
<para>
- <command>dio</command>
+ <code>dio</code>
</para>
</listitem>
<listitem>
<para>
- <command>yp</command>
+ <code>yp</code>
</para>
</listitem>
</itemizedlist>
<section>
<title>The PEAR framework</title>
- <para>The PEAR framework is now packaged in the <command>php-pear</command> package; only the following PEAR components are included in Fedora Core: </para>
+ <para>The PEAR framework is now packaged in the <code>php-pear</code> package. Only the following PEAR components are included in Fedora Core: </para>
<itemizedlist>
<listitem>
<para>
- <command>Archive_Tar</command>
+ <code>Archive_Tar</code>
</para>
</listitem>
<listitem>
<para>
- <command>Console_Getopt</command>
+ <code>Console_Getopt</code>
</para>
</listitem>
<listitem>
<para>
- <command>XML_RPC</command>
+ <code>XML_RPC</code>
</para>
</listitem>
</itemizedlist>
- <para>additional components may be packaged in Fedora Extras. </para>
+ <para>Additional components may be packaged in Fedora Extras. </para>
</section>
</section>
</section>
Index: Welcome.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Welcome.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Welcome.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Welcome.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,36 +1,47 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Welcome">
+ <section>
+ <title>Docs/Beats/Welcome</title>
+ <section>
<title>Welcome to Fedora Core</title>
- <warning>
- <title>Fedora Core Test Release</title>
- <para> This is a test release and is provided for developers and testers to participate and provide feedback. It is not meant for end users. </para>
- </warning>
- <tip>
- <title>Join the Community for More Information</title>
- <para> Subscribe to the fedora-test and fedora-devel mailings lists to keep track of important changes in the current development versions and provide feedback to the developers. Fedora Project requests you to file bug reports and enhancements to provide a improved final release to end users. See the following document for more information. </para>
- <para>
- <ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>. Thank you for your participation. </para>
- </tip>
- <important>
- <title>Latest Release Notes on the Web</title>
- <para>These release notes may be updated. Visit <ulink url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink> to view the latest release notes for Fedora Core . </para>
- </important>
- <para>Refer to these webpages to find out more information about Fedora: </para>
<itemizedlist>
<listitem>
<para>
- <ulink url='/Docs/Beats/OverView'>Docs/Beats/OverView</ulink>
</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'>Latest Release Notes on the Web</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> These release notes may be updated. Visit <ulink url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink> to view the latest release notes for Fedora Core . </para>
+ </td>
+ </tr>
+ </table>
</listitem>
+ </itemizedlist>
+ <para>You can help the Fedora Project community continue to improve Fedora if you file bug reports and enhancement requests. Refer to <ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink> for more information about bugs. Thank you for your participation. </para>
+ <para>To find out more general information about Fedora, refer to the following Web pages: </para>
+ <itemizedlist>
<listitem>
- <para>
- <ulink url='/Docs/Beats/Introduction'>Docs/Beats/Introduction</ulink>
- </para>
+ <para> Fedora Overview (<ulink url='http://fedoraproject.org/wiki/Overview'>http://fedoraproject.org/wiki/Overview</ulink>) </para>
</listitem>
<listitem>
<para> Fedora FAQ (<ulink url='http://fedoraproject.org/wiki/FAQ'>http://fedoraproject.org/wiki/FAQ</ulink>) </para>
@@ -45,5 +56,6 @@
<para> About the Fedora Project (<ulink url='http://fedora.redhat.com/About/'>http://fedora.redhat.com/About/</ulink>) </para>
</listitem>
</itemizedlist>
+ </section>
</section>
</article>
Index: Xorg.xml
===================================================================
RCS file: /cvs/docs/release-notes/en/Xorg.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Xorg.xml 17 Feb 2006 00:47:01 -0000 1.1
+++ Xorg.xml 28 Feb 2006 17:25:26 -0000 1.2
@@ -1,59 +1,100 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
- <section id="sn-Xorg">
+ <section>
<title>X Window System (Graphics)</title>
<para>This section contains information related to the X Window System implementation provided with Fedora. </para>
<section>
<title>xorg-x11</title>
- <para>X.org X11 is an open source implementation of the X Window System. It provides the basic low level functionality which full fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed upon. </para>
- <para>For more information about Xorg refer to <ulink url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
- </para>
- <para>You can use Applications => System Settings => Display or system-config-display to configure the settings. The configuration file for Xorg is located in /etc/X11/xorg.conf </para>
- <para>Modular X.Org X11R7 RC2 was released into Fedora development (rawhide) on November 16, 2005. This is the first modular release of Xorg which among several other benefits, enable users to receive updates in a faster pace and helps developers to develop and release specific components in a rapid fashion. </para>
- <para>More information on the current status of the Xorg modularization effort in Fedora is available from <ulink url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
- </para>
+ <para>X.org X11 is an open source implementation of the X Window System. It provides the basic low-level functionality upon which full-fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed. For more information about X.org, refer to <ulink url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>. </para>
+ <para>You may use <emphasis>Applications > System Settings > Display</emphasis> or <emphasis role='strong'>system-config-display</emphasis> to configure the settings. The configuration file for X.org is located in <code>/etc/X11/xorg.conf</code>. </para>
+ <para>X.org X11R7 is the first modular release of X.org, which, among several other benefits, promotes faster updates and helps programmers rapidly develop and release specific components. More information on the current status of the X.org modularization effort in Fedora is available at <ulink url='http://fedoraproject.org/wiki/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>. </para>
</section>
<section>
- <title>Xorg X11R7.0 Developer Notes</title>
- <para>X11R7.0 is included in this release and there are a number of things that software developers, and packagers in Fedora repositories need to be aware of in order to ensure that their software or software packages properly compile and work with X11<emphasis role='strong'/>R7. Some are simple changes, while others may be more involved. Here is a summary of issues that may arise and where possible, suggestions on how to fix them. </para>
- <section>
- <title>The /usr/X11R6 Directory Hierarchy</title>
- <para>X11<emphasis role='strong'/>R7 install into /usr directly now, and no longer uses the /usr/X11<emphasis role='strong'/>R6 hierarchy. Applications which rely on files being present at fixed paths under /usr/X11<emphasis role='strong'/>R6 at compile time or at run time, must be updated to use the system PATH, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks. </para>
- </section>
- <section>
- <title>Imake</title>
- <para>Imake is no longer used to build the X Window System, and as such is now officially deprecated. Imake, xmkmf and other utilities previously supplied by the X Window System, are still supplied in X11<emphasis role='strong'/>R7, however X.Org highly recommends that people migrate from Imake to using GNU autotools and pkg-config. imake support may vanish in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects. </para>
- </section>
- <section>
- <title>The Systemwide <filename>app-defaults</filename> Directory</title>
- <para>The system app-defaults directory for X resources, is now "%{_datadir}/X11/app-defaults", which expands to /usr/share/X11/app-defaults on Fedora Core 5 and for future Red Hat Enterprise Linux systems. </para>
- </section>
- <section>
- <title>xft-config Can't Be Found</title>
- <para>Modular X now uses GNU autotools, and pkg-config for its buildsystem configuration, etc. xft-config has been deprecated for 2-3 years now, and pkgconfig *.pc files have been provided for most of this time. Applications which previously used xft-config to obtain the Cflags or libs options for building with, must now be updated to use pkg-config. </para>
- </section>
+ <title>X.org X11R7 End-User Notes</title>
+ <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'>Installing Third Party Drivers</emphasis>
+ </para>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <para> Before you install any third party drivers from any vendor, including ATI or nVidia, please read <ulink url='http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers'>http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>. </para>
+ </td>
+ </tr>
+ </table>
+ </listitem>
+ </itemizedlist>
+ <para>The <code>xorg-x11-server-Xorg</code> package install scripts automatically remove the <code>RgbPath</code> line from the <code>xorg.conf</code> file if it is present. You may need to reconfigure your keyboard differently from what you are used to. You are encouraged to subscribe to the upstream <ulink url='mailto:xorg at freedesktop.org'>xorg at freedesktop.org</ulink> mailing list if you do need assistance reconfiguring your keyboard. </para>
</section>
<section>
- <title>Xorg X11R7 Developer Overview</title>
- <para>Here is a short list of some of the more developer/package visible changes that are present in X11<emphasis role='strong'/>R7: </para>
+ <title>X.org X11R7 Developer Overview</title>
+ <para>The following list includes some of the more visible changes for developers in X11R7: </para>
<itemizedlist>
<listitem>
- <para> The entire buildsystem has changed from "Imake" to the GNU autotools collection. </para>
+ <para> The entire buildsystem has changed from <code>imake</code> to the GNU <code>autotools</code> collection. </para>
</listitem>
<listitem>
- <para> All of the libraries now install pkgconfig *.pc files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in /usr/X11<emphasis role='strong'/>R6/lib or elsewhere. </para>
+ <para> Libraries now install <code>pkgconfig</code>
+ <code>*.pc</code> files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in <code>/usr/X11</code>
+ <code>R6/lib </code> or elsewhere. </para>
</listitem>
<listitem>
- <para> Everything is now installed directly into /usr instead of /usr/X11<emphasis role='strong'/>R6. All software which hard codes paths to anything in /usr/X11<emphasis role='strong'/>R6, must now be changed preferably to dynamically detect the proper location of the object, or to hard code the new paths that X11<emphasis role='strong'/>R7 uses by default. It is strongly advised to use autodetection methods than to hard code paths. </para>
+ <para> Everything is now installed directly into <code>/usr</code> instead of <code>/usr/X11</code>
+ <code>R6</code>. All software that hard codes paths to anything in <code>/usr/X11</code>
+ <code>R6</code> must now be changed, preferably to dynamically detect the proper location of the object. Developers are <emphasis role='strong'>strongly</emphasis> advised against hard-coding the new X11R7 default paths. </para>
</listitem>
<listitem>
- <para> Every library is in its own private source RPM now, which creates a runtime binary subpackage, and a -devel subpackage. Any software package that previously picked up the development headers, etc. for X libraries by using "Build<emphasis role='strong'/>Requires: (XFree86-devel|xorg-x11-devel)", must now individually list each library dependency individually. When doing this, it is greatly preferred and strongly recommended to use "virtual" build dependencies instead of hard coding the library rpm package names of the xorg implementation. This means you should use: "Build<emphasis role='strong'/>Requires: libXft-devel" instead of using: "Build<emphasis role='strong'/>Requires: xorg-x11-Xft-devel". If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean/safe way to state the dependency, then go ahead and use the "xorg-x11--devel" form. By sticking to the virtual provides/requires mechanism, this ma!
kes it painless if and when the libraries move to another location in the future. </para>
+ <para> Every library has its own private source RPM package, which creates a runtime binary subpackage and a <code>-devel</code> subpackage. </para>
</listitem>
</itemizedlist>
</section>
+ <section>
+ <title>X.org X11R7 Developer Notes</title>
+ <para>This section includes a summary of issues of note for developers and packagers, and suggestions on how to fix them where possible. </para>
+ <section>
+ <title>The /usr/X11R6/ Directory Hierarchy</title>
+ <para>X11R7 files install into <code>/usr</code> directly now, and no longer use the <code>/usr/X11</code>
+ <code>R6/</code> hierarchy. Applications that rely on files being present at fixed paths under <code>/usr/X11</code>
+ <code>R6/</code>, either at compile time or run time, must be updated. They should now use the system <code>PATH</code>, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks. </para>
+ </section>
+ <section>
+ <title>Imake</title>
+ <para>The <code>imake</code> utility is no longer used to build the X Window System, and is now officially deprecated. X11R7 includes <code>imake</code>, <code>xmkmf</code>, and other build utilities previously supplied by the X Window System. X.Org highly recommends, however, that people migrate from <code>imake</code> to use GNU <code>autotools</code> and <code>pkg-config</code>. Support for <code>imake</code> may be removed in a future X Window System release, so developers are <emphasis role='strong'>strongly</emphasis> encouraged to transition away from it, and not use it for any new software projects. </para>
+ </section>
+ <section>
+ <title>The Systemwide app-defaults/ Directory</title>
+ <para>The system <code>app-defaults/</code> directory for X resources is now <code>%{_datadir}/X11/app-defaults</code>, which expands to <code>/usr/share/X11/app-defaults/</code> on Fedora Core and for future Red Hat Enterprise Linux systems. </para>
+ </section>
+ <section>
+ <title>Correct Package Dependencies</title>
+ <para>Any software package that previously used <code>Build</code>
+ <code>Requires: (XFree86-devel|xorg-x11-devel)</code> to satisfy build dependencies must now individually list each library dependency. The preferred and recommended method is to use <emphasis>virtual</emphasis> build dependencies instead of hard coding the library package names of the <code>xorg</code> implementation. This means you should use <code>Build</code>
+ <code>Requires: libXft-devel</code> instead of <code>Build</code>
+ <code>Requires: xorg-x11-Xft-devel</code>. If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean or safe way to state the dependency, then use the <code>xorg-x11-devel</code> form. If you use the virtual provides/requires mechanism, you will avoid inconvenience if the libraries move to another location in the future. </para>
+ </section>
+ <section>
+ <title>xft-config</title>
+ <para>Modular X now uses GNU <code>autotools</code> and <code>pkg-config</code> for its buildsystem configuration and execution. The <code>xft-config</code> utility has been deprecated for some time, and <code>pkgconfig</code>
+ <code>*.pc</code> files have been provided for most of this time. Applications that previously used <code>xft-config</code> to obtain the <code>Cflags</code> or <code>libs</code> build options must now be updated to use <code>pkg-config</code>. </para>
+ </section>
+ </section>
</section>
</article>
--- PackageNotesJava.xml DELETED ---
More information about the Fedora-docs-commits
mailing list