release-notes ArchSpecific-en.xml, 1.1, 1.2 ArchSpecificPPC-en.xml, 1.1, 1.2 ArchSpecificx86-en.xml, 1.1, 1.2 ArchSpecificx86_64-en.xml, 1.1, 1.2 Colophon-en.xml, 1.1, 1.2 Desktop-en.xml, 1.2, 1.3 DevelopmentTools-en.xml, 1.1, 1.2 DevelopmentToolsGCC-en.xml, 1.1, 1.2 DevelopmentToolsJava-en.xml, 1.1, 1.2 FileServers-en.xml, 1.1, 1.2 I18n-en.xml, 1.1, 1.2 Installer-en.xml, 1.1, 1.2 Kernel-en.xml, 1.1, 1.2 Legacy-en.xml, 1.1, 1.2 OverView-en.xml, 1.1, 1.2 PackageChanges-en.xml, 1.1, 1.2 ProjectOverview-en.xml, 1.1, 1.2 RELEASE-NOTES-en.xml, 1.14, 1.15 Samba-en.xml, 1.1, 1.2 Security-en.xml, 1.1, 1.2 SecuritySELinux-en.xml, 1.1, 1.2 ServerTools-en.xml, 1.1, 1.2 SystemDaemons-en.xml, 1.1, 1.2 WebServers-en.xml, 1.1, 1.2 Welcome-en.xml, 1.2, 1.3
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon Jan 9 12:29:09 UTC 2006
Author: kwade
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv26339
Modified Files:
ArchSpecific-en.xml ArchSpecificPPC-en.xml
ArchSpecificx86-en.xml ArchSpecificx86_64-en.xml
Colophon-en.xml Desktop-en.xml DevelopmentTools-en.xml
DevelopmentToolsGCC-en.xml DevelopmentToolsJava-en.xml
FileServers-en.xml I18n-en.xml Installer-en.xml Kernel-en.xml
Legacy-en.xml OverView-en.xml PackageChanges-en.xml
ProjectOverview-en.xml RELEASE-NOTES-en.xml Samba-en.xml
Security-en.xml SecuritySELinux-en.xml ServerTools-en.xml
SystemDaemons-en.xml WebServers-en.xml Welcome-en.xml
Log Message:
Content merged from Wiki into -en files now. However, there is a build problem due to an XML error that I have not detected yet. Translation can begin, but the build error persists. I am going to tag the content for translatio, regardless, with the exception of a few files that need special attention.
Index: ArchSpecific-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ArchSpecific-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecific-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ArchSpecific-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,262 +1,15 @@
<section id="sn-arch-specific">
<title>Hardware Architecture Specific Notes</title>
-
- <section id="sn-hardware-reqs">
- <title>Hardware Requirements</title>
- <para>
- The following information represents the minimum hardware
- requirements necessary to successfully install &DISTRO;
- &DISTROVER;.
- </para>
- <note>
- <title>Note</title>
- <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>
- </note>
-<!-- Something like this needs to be said, but this really needs a -->
-<!-- better treatment and probably a new section devoted to help resources.
+
<para>
- This section does not address hardware compatability. To find out
- about using a specific piece of hardware with &FC; &LOCALVER;
+ This section provides notes that are specific to the supported
+ hardware architectures of &FC;.
</para>
--->
- <section>
- <title>CPU Requirements</title>
-
- <para>This section lists the CPU specifications required by
- &DISTRO; &DISTROVER;.</para>
-
- <note arch="x86">
- <title><!-- <remark os="test">(x86)</remark>--> Note</title>
-
- <para><!-- <remark os="test">(x86)</remark> --> 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 &DISTRO;.</para>
- </note>
-
- <itemizedlist arch="x86">
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Minimum:
- Pentium-class — &FC; &LOCALVER; 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. <!--
- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136254</ulink>
- %%%</remark> -->
- </para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Recommended
- for text-mode: 200 MHz Pentium-class or better</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Recommended
- for graphical: 400 MHz Pentium II or better</para>
- </listitem>
- </itemizedlist>
-
- <itemizedlist arch="x86_64">
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> AMD64
- processors (both Athlon64 and Opteron)</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Intel
- processors with <trademark
- class="registered">Intel</trademark> Extended Memory 64
- Technology (<trademark class="registered">Intel</trademark>
- EM64T)</para>
- </listitem>
- </itemizedlist>
- </section>
- <section>
- <title>Hard Disk Space Requirements</title>
-
- <para>This section lists the disk space required to install
- &DISTRO; &DISTROVER;.</para>
-
- <note>
- <title>Note</title>
-
- <para>The disk space requirements listed below represent the
- disk space taken up by &DISTRO; &DISTROVER;
- <emphasis>after</emphasis> 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
- <filename>/Fedora/base/stage2.img</filename> (on CD-ROM 1)
- plus the size of the files in
- <filename>/var/lib/rpm</filename> on the installed
- system.</para>
-
- <!-- Update these figures every release -->
- <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.</para>
-
- <para>Also, keep in mind that additional space will be required
- for any user data, and at least 5% free space should be
- maintained for proper system operation.</para>
- </note>
-
- <!-- Get actual numbers from installer, multiply by 1.1, and round -->
- <!-- up to the nearest 10MB or .1GB -->
- <para>
- This list is for 32-bit x86 systems:
- </para>
- <itemizedlist arch="x86">
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Custom
- Installation (Minimal): 620MB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Server:
- 1.1GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Personal
- Desktop: 2.3GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Workstation:
- 3.0GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Custom
- Installation (Everything): 6.9GB</para>
- </listitem>
- </itemizedlist>
- <para>
- This list is for 64-bit x86_64 systems:
- </para>
- <itemizedlist arch="x86_64">
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Custom
- Installation (Minimal): 900MB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Server:
- 1.5GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Personal
- Desktop: 2.7GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> -->
- Workstation: 3.4GB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Custom
- Installation: (Everything) 7.5GB</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Memory Requirements</title>
-
- <para>This section lists the memory required to install &DISTRO;
- &DISTROVER;.</para>
- <para>
- This list is for 32-bit x86 systems:
- </para>
- <itemizedlist arch="x86">
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Minimum for
- text-mode: 64MB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Minimum for
- graphical: 192MB</para>
- </listitem>
-
- <listitem>
- <para><!-- <remark os="test">(x86)</remark> --> Recommended
- for graphical: 256MB</para>
- </listitem>
- </itemizedlist>
- <para>
- This list is for 64-bit x86_64 systems:
- </para>
- <itemizedlist arch="x86_64">
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
- text-mode: 128MB</para>
- </listitem>
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Minimum for
- graphical: 256MB</para>
- </listitem>
+ &ARCH-SPECIFIC-PPC;
+ &ARCH-SPECIFIC-x86;
+ &ARCH-SPECIFIC-x86-64;
- <listitem>
- <para><!-- <remark os="test">(x86_64)</remark> --> Recommended
- for graphical: 512MB</para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="sn-hardware-reqs-ppc">
- <title>PPC Hardware Requirements</title>
- <para>
- This section lists the minimum PowerPC (PPC) hardware needed to
- install &FC; &LOCALVER;.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <!--<remark os="test">(ppc)</remark> --> Minimum: PowerPC G3
- / POWER4
- </para>
- </listitem>
- <listitem>
- <para>
- <!--<remark os="test">(ppc)</remark> --> &FC; &LOCALVER;
- supports the <quote>New World</quote> generation of Apple
- Power Macintosh (shipped circa 1999 onwards), Genesi Pegasos
- II, and IBM 32-bit RS/6000 machines. It also supports the
- 64-bit G5 processor, and POWER processors in the IBM eServer
- pSeries.
- </para>
- </listitem>
- <listitem>
- <para>
- <!--<remark os="test">(x86)</remark> --> Recommended for
- text-mode: 233 MHz G3 or better
- </para>
- </listitem>
- <listitem>
- <para>
- <!-- <remark os="test">(ppc)</remark> --> Recommended for
- graphical: 400 MHz G3 or better
- </para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
</section>
<!--
Local variables:
Index: ArchSpecificPPC-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ArchSpecificPPC-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificPPC-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ArchSpecificPPC-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,22 +1,22 @@
<section id="sn-arch-specific-ppc">
- <title>PPC Specifics for Fedora</title>
+ <title>PPC Specifics for &FED;</title>
<para>This section covers any specific information you may need to
- know about Fedora Core and the PPC hardware platform. </para>
+ know about &FC; and the PPC hardware platform. </para>
<section id="sn-arch-specific-ppc-hardware-reqs">
<title>PPC Hardware Requirements</title>
<para>This section lists the minimum PowerPC (PPC) hardware needed
- to install Fedora Core 4. </para>
+ to install &FC; 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>
+ <para> &FC; 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â„¢ and Genesi Pegasos II machines. </para>
+ <para> &FC; also supports IBM eServer pSeries, IBM
+ RS/6000 and Genesi Pegasos II machines. </para>
</listitem>
<listitem>
<para> Recommended for text-mode: 233 MHz G3 or better, 64MiB
@@ -32,46 +32,47 @@
<title>PPC Installation Notes</title>
<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>The DVD or first CD of the installation set of &FC; is set
+ to be bootable on supported hardware. In addition, bootable
+ CD images can be found in the <filename>images/</filename>
+ directory of the DVD or first CD. These images behave
+ differently depending on the hardware: </para>
</listitem>
<listitem>
- <para> Apple® Macintosh </para>
+ <para> Apple Macintosh </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>
+ is present in the apmud package, which is in &FEX;. &FEX;
+ for &FC; is configured by default for
+ <command>yum</command>. Following installation,
+ <filename>apmud</filename> can be installed by running
+ <command>yum install apmud</command>.
+ </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
- <para> 64-bit IBM® eServer™ pSeries™ (POWER4/POWER5) </para>
+ <para> 64-bit IBM eServer pSeries (POWER4/POWER5) </para>
<itemizedlist>
<listitem>
- <para>After using <ulink
- url='/OpenFirmware'>OpenFirmware</ulink> to boot the CD,
- the bootloader (yaboot) should automatically boot the
- 64-bit installer. </para>
+ <para>After using OpenFirmware to boot the CD, the
+ bootloader (<command>yaboot</command>) should
+ automatically boot the 64-bit installer. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
- <para> 32-bit CHRP (IBM® RS/6000 and others) </para>
+ <para> 32-bit CHRP (IBM RS/6000 and others) </para>
<itemizedlist>
<listitem>
- <para>After using <ulink
- url='/OpenFirmware'>OpenFirmware</ulink> to boot the CD,
- select the 'linux32' boot image at the 'boot:' prompt to
- start the 32-bit installer. Otherwise, the 64-bit
- installer will be started, which will not work. </para>
+ <para>After using OpenFirmware to boot the CD, select the
+ <filename>linux32</filename> boot image at the
+ <prompt>boot:</prompt> prompt to start the 32-bit
+ installer. Otherwise, the 64-bit installer is
+ started, which does not work. </para>
</listitem>
</itemizedlist>
</listitem>
@@ -81,19 +82,20 @@
<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 <ulink
- url='/OpenFirmware'>OpenFirmware</ulink> prompt, enter
- the command: </para>
+ However, the network boot image can be used. At the
+ OpenFirmware prompt, enter the command: </para>
+<screen>
+boot cd: /images/netboot/ppc32.img
+</screen>
</listitem>
</itemizedlist>
- <para>boot cd: /images/netboot/ppc32.img </para>
<itemizedlist>
<listitem>
- <para>You will also need to configure <ulink
- url='/OpenFirmware'>OpenFirmware</ulink> 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>
+ <para>You will also need to configure OpenFirmware on the
+ Pegasos manually to make the installed &FC; system
+ bootable. To do this, you need to set the
+ <envar>boot-device</envar> and <envar>boot-file</envar>
+ environment variables appropriately. </para>
</listitem>
</itemizedlist>
</listitem>
@@ -102,12 +104,14 @@
<itemizedlist>
<listitem>
<para>There are combined images containing the installer
- kernel and ramdisk in the images/netboot/ directory of the
+ kernel and ramdisk in the
+ <filename>images/netboot/</filename> 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>
+ <para><command>yaboot</command> supports tftp booting for
+ IBM eServer pSeries and Apple Macintosh, the use of
+ <command>yaboot</command> is encouraged over the netboot
+ images. </para>
</listitem>
</itemizedlist>
</listitem>
Index: ArchSpecificx86-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ArchSpecificx86-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificx86-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ArchSpecificx86-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,27 +1,26 @@
<section id="sn-arch-specific-x86">
- <title>x86 Specifics for Fedora</title>
+ <title>x86 Specifics for &FED;</title>
<para>This section covers any specific information you may need to
- know about Fedora Core and the x86 hardware platform. </para>
+ know about &FC; and the x86 hardware platform. </para>
<section id="sn-arch-specific-x86-hardware-reqs">
<title>x86 Hardware Requirements</title>
<para>The following information represents the minimum hardware
- requirements necessary to successfully install Fedora Core 5
- test1. </para>
+ requirements necessary to successfully install &FC; &LOCALVER;. </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>
<section id="sn-arch-specific-x86-cpu-reqs">
<title>CPU Requirements</title>
- <para>This section lists the CPU specifications required by Fedora
- Core 5 test1. </para>
+ <para>This section lists the CPU specifications required by &FC;
+ &LOCALVER;. </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.
+ following Intel processors may also be used with &FC;.
</para>
<itemizedlist>
<listitem>
- <para> Minimum: Pentium-class — Fedora Core 5 test1 is
+ <para> Minimum: Pentium-class — &FC; &LOCALVER; 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
@@ -43,16 +42,16 @@
<para> AMD64 processors (both Athlon64 and Opteron) </para>
</listitem>
<listitem>
- <para> Intel processors with Intel® Extended Memory 64
- Technology (Intel® EM64T) </para>
+ <para> Intel processors with Intel Extended Memory 64
+ Technology (Intel EM64T) </para>
</listitem>
</itemizedlist>
<para>
</para>
<section id="sn-arch-specific-x86-memory-reqs">
<title>Memory Requirements</title>
- <para>This section lists the memory required to install Fedora
- Core 5 test1. </para>
+ <para>This section lists the memory required to install &FC;
+ &LOCALVER;. </para>
<para>This list is for 32-bit x86 systems: </para>
<itemizedlist>
<listitem>
@@ -70,7 +69,7 @@
<section id="sn-arch-specific-x86-installation-notes">
<title>x86 Installation Notes</title>
<para>Installer package screen selection interface is being
- redesigned in the Fedora development version. Fedora Core test 1
+ redesigned in the &FED; development version. &FC; &LOCALVER;
does not provide a option to select the installation type such
as Personal Desktop, Workstation, Server and custom. </para>
</section>
Index: ArchSpecificx86_64-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ArchSpecificx86_64-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ArchSpecificx86_64-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ArchSpecificx86_64-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,12 +1,11 @@
<section id="sn-arch-specific-x86-64">
- <title>x86_64 Specifics for Fedora</title>
+ <title>x86_64 Specifics for &FED;</title>
<para>This section covers any specific information you may need to
- know about Fedora Core and the x86_64 hardware platform. </para>
+ know about &FC; and the x86_64 hardware platform. </para>
<section id="sn-arch-specific-x86-64-hardware-reqs">
<title>x86_64 Hardware Requirements</title>
<para>The following information represents the minimum hardware
- requirements necessary to successfully install Fedora Core 5
- test1. </para>
+ requirements necessary to successfully install &FC; &LOCALVER;. </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>
@@ -14,8 +13,9 @@
</para>
<section id="sn-arch-specific-x86-64-memory-reqs">
<title>Memory Requirements</title>
- <para>This section lists the memory required to install Fedora
- Core 5 test1. </para>
+ <para>This section lists the memory required to install &FC;
+ &LOCALVER;.
+ </para>
<para>This list is for 64-bit x86_64 systems: </para>
<itemizedlist>
<listitem>
Index: Colophon-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Colophon-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Colophon-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Colophon-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -13,7 +13,7 @@
accountability. </para>
</listitem>
<listitem>
- <para> Explain tools and production methods. </para>
+ <para> An explanation of tools and production methods. </para>
</listitem>
</itemizedlist>
<section>
@@ -92,7 +92,7 @@
</listitem>
<listitem>
<para>
- Stuar tElliss (editor)
+ Stuart Elliss (editor)
</para>
</listitem>
<listitem>
@@ -117,6 +117,19 @@
</section>
<section>
<title>Production Methods</title>
+ <para>
+ We write the beats in the Wiki, convert from Wiki to DocBook XML,
+ diff that content against the XML in CVS, and build a book from
+ that. CVS for the XML is:
+ </para>
+ <para>
+ cvs.fedora.redhat.com:/cvs/docs/release-notes
+ </para>
+ <para>
+ You can read more about how to get content from CVS and the
+ project overall at <ulink
+ url="http://fedora.redhat.com/About/Projects/docs.html"/>.
+ </para>
</section>
</section>
<!--
Index: Desktop-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Desktop-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Desktop-en.xml 9 Jan 2006 10:04:19 -0000 1.2
+++ Desktop-en.xml 9 Jan 2006 12:28:41 -0000 1.3
@@ -7,9 +7,10 @@
</para>
</listitem>
<listitem>
- <para>This 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>
+ GNOME 2.13.2 and KDE 3.5 Release Candidate 2 has been included
+ in &FC; &LOCALVER;. GNOME 2.14 (or a release candidate) is
+ scheduled to be available as part of &FC; 5.
</para>
<itemizedlist>
<listitem>
@@ -23,7 +24,7 @@
</para>
</listitem>
<listitem>
- <para><filename>gnome-screensaver</filename>: Provides a
+ <para><filename>gnome-screensaver</filename>: Provides an
integrated user interface to screensavers and the lock
screen dialog.
</para>
@@ -38,7 +39,7 @@
</itemizedlist>
</listitem>
<listitem>
- <para>GNOME 2.12 has removed the
+ <para>GNOME 2.12+ has removed the
<guimenuitem>terminal</guimenuitem> option from the desktop
context menu. The package
<filename>nautilus-open-terminal</filename> in &FEX;
Index: DevelopmentTools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/DevelopmentTools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DevelopmentTools-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ DevelopmentTools-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -15,6 +15,35 @@
</title>
&DEVELOPMENT-TOOLS-JAVA;
&DEVELOPMENT-TOOLS-GCC;
+ <section id="sn-fortran">
+ <title>FORTRAN</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ The GNU FORTRAN 77 front end has been replaced by a new
+ FORTRAN 90/95 recognizer.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="sn-eclipse">
+ <title>Eclipse Development Environment</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Eclipse 3.1M6 has been compiled as a native application.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The C Development Tool (CDT) has been included.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
Index: DevelopmentToolsGCC-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/DevelopmentToolsGCC-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DevelopmentToolsGCC-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ DevelopmentToolsGCC-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -9,170 +9,121 @@
]>
-->
-<!-- Content commented out, no update performed by beat writer yet.
<section id="sn-devel-gcc">
- <title>GCC Compiler Collection</title>
- <para>
- &DISTRO; &DISTROVER; has been built using <abbrev>GCC</abbrev>
- 4.0, which is included with the distribution.
- </para>
- <itemizedlist>
- <title>Caveats</title>
- <listitem>
- <para>
- <abbrev>GDB</abbrev> 6.1 or newer is needed to debug binaries
- unless compiled using the <parameter
- class="option">-fno-var-tracking</parameter> compilation
- option.
- </para>
- </listitem>
- <listitem>
- <para>
- The <parameter class="option">-fwritable-strings</parameter>
- option is no longer accepted.
- </para>
- </listitem>
- <listitem>
- <para>
- English-language diagnostic messages now use Unicode quotes;
- if you cannot read this, set your <envar>LC_CTYPE</envar>
- environment variable to "<filename>C</filename>" or
- change your terminal emulator.
- </para>
- </listitem>
- <listitem>
- <para>
- The <filename>specs</filename> file is no longer installed on
- most systems. Ordinary users will not notice, but developers
- who need to alter the file can use the <parameter
- class="option">-dumpspecs</parameter> option to generate the
- file for editing.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist>
- <title>Code Generation</title>
- <listitem>
- <para>
- The <abbrev>SSA</abbrev> code optimizer is now included and
- brings with it better constant propagation, partial redundancy
- elimination, load and store code motion, strength reduction,
- dead storage elimination, better detection of unreachable
- code, and tail recursion by accumulation.
- </para>
- </listitem>
- <listitem>
- <para>
- Autovectorization is supported. This technique achieves higher
- performance for repetitive loop code, in some circumstances.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist>
- <title>Language Extentions</title>
- <listitem>
- <para>
- A <computeroutput>sentinel</computeroutput> attribute has been
- added so that the compiler will now issue a warning if a
- function such as <function>execl(char *path, const char *arg,
- ...)</function>, which requires a <literal>NULL</literal>
- list terminator is missing the <literal>NULL</literal>.
- </para>
- </listitem>
- <listitem>
- <para>
- The <wordasword>cast-as-lvalue</wordasword>,
- <wordasword>conditional-expression-as-lvalue</wordasword>, and
- <wordasword>compund-expression-as-lvalue</wordasword>
- extentions have been removed.
- </para>
- </listitem>
- <listitem>
- <para>
- The <computeroutput>#pragma pack()</computeroutput> semantics
- have been brought closer to those used by other compilers.
- </para>
- </listitem>
- <listitem>
- <para>
- Taking the address of a variable declared with the
- <computeroutput>register</computeroutput> modifier now
- generates an error instead of a warning.
- </para>
- </listitem>
- <listitem>
- <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 (<parameter
- class="option">-O0</parameter>), 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 <parameter
- class="option">-fno-threadsafe-statics</parameter> can be
- used by embedded developers to turn off this feature, but
- ordinary users should never do this.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist>
- <title>Java</title>
- <listitem>
- <para>
- To avoid naming conflicts: <filename>rmic</filename> is now
- <filename>grmic</filename>; <filename>rmiregistry</filename>
- is now <filename>grmiregistry</filename>; and
- <filename>jar</filename> is now <filename>fastjar</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- The <application>GCJ</application> compiler can now be used as
- a just-in-time (<abbrev>JIT</abbrev>) tool by using the
- <filename>gnu.jit</filename> facilities.
- </para>
- </listitem>
- <listitem>
- <para>
- More support of the <abbrev>AWT</abbrev> and
- <abbrev>SWING</abbrev> packages have been added.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist>
- <title>FORTRAN</title>
- <listitem>
- <para>
- The <abbrev>GNU</abbrev> <application>FORTRAN 77</application>
- front end has been replaced by a new <application>FORTRAN
- 90/95</application> recognizer.
- </para>
- </listitem>
- </itemizedlist>
- <itemizedlist>
- <title>Eclipse Development Environment</title>
- <listitem>
- <para>
- Eclipse 3.1M6 has been compiled as a native application.
- </para>
- </listitem>
- <listitem>
- <para>
- The C Development Tool (<abbrev>CDT</abbrev>) has been
- included.
- </para>
- </listitem>
- </itemizedlist>
- </section>
--->
+ <title>GCC Compiler Collection</title>
+ <para>
+ &FC; &LOCALVER; has been built using <abbrev>GCC</abbrev> 4.1, which
+ is included with the distribution.
+ </para>
+ <itemizedlist>
+ <title>Caveats</title>
+ <listitem>
+ <para>
+ <abbrev>GDB</abbrev> 6.1 or newer is needed to debug binaries
+ unless compiled using the <parameter
+ class="option">-fno-var-tracking</parameter> compilation
+ option.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <parameter class="option">-fwritable-strings</parameter>
+ option is no longer accepted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ English-language diagnostic messages now use Unicode quotes; if
+ you cannot read this, set your <envar>LC_CTYPE</envar>
+ environment variable to "<filename>C</filename>" or
+ change your terminal emulator.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <filename>specs</filename> file is no longer installed on
+ most systems. Ordinary users will not notice, but developers who
+ need to alter the file can use the <parameter
+ class="option">-dumpspecs</parameter> option to generate the
+ file for editing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Code Generation</title>
+ <listitem>
+ <para>
+ The <abbrev>SSA</abbrev> code optimizer is now included and
+ brings with it better constant propagation, partial redundancy
+ elimination, load and store code motion, strength reduction,
+ dead storage elimination, better detection of unreachable code,
+ and tail recursion by accumulation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Autovectorization is supported. This technique achieves higher
+ performance for repetitive loop code, in some circumstances.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Language Extentions</title>
+ <listitem>
+ <para>
+ A <computeroutput>sentinel</computeroutput> attribute has been
+ added so that the compiler will now issue a warning if a
+ function such as <function>execl(char *path, const char *arg,
+ ...)</function>, which requires a
+ <computeroutput>NULL</computeroutput> list terminator is missing
+ the <computeroutput>NULL</computeroutput>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <option>cast-as-lvalue</option>,
+ <option>conditional-expression-as-lvalue</option>, and
+ <option>compund-expression-as-lvalue</option> extentions have
+ been removed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <computeroutput>#pragma pack()</computeroutput> semantics
+ have been brought closer to those used by other compilers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Taking the address of a variable declared with the
+ <computeroutput>register</computeroutput> modifier now generates
+ an error instead of a warning.
+ </para>
+ </listitem>
+ <listitem>
+ <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 (<parameter
+ class="option">-O0</parameter>), 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 <parameter
+ class="option">-fno-threadsafe-statics</parameter> can be used
+ by embedded developers to turn off this feature, but ordinary
+ users should never do this.
+ </para>
+ </listitem>
+ </itemizedlist>
+</section>
<!--
Local variables:
Index: DevelopmentToolsJava-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/DevelopmentToolsJava-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- DevelopmentToolsJava-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ DevelopmentToolsJava-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -24,6 +24,45 @@
<ulink
url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
</para>
+ <section id="sn-java-development">
+ <title>Java Development</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ To avoid naming conflicts the following have been renamed:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><filename>rmic</filename> is now
+ <filename>grmic</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para><filename>rmiregistry</filename> is now
+ <filename>grmiregistry</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para><filename>jar</filename> is now
+ <filename>fastjar</filename>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>
+ The GCJ compiler can now be used as a just-in-time (JIT) tool
+ by using the <filename>gnu.jit</filename> facilities.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ More support of the AWT and SWING packages have been added.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
</section>
<!--
Local variables:
Index: FileServers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/FileServers-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FileServers-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ FileServers-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -3,13 +3,12 @@
<caution>
<title>Information Out-of-Date</title>
<para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
+ The content in this section needs to be updated for &FC; &LOCALVER;
</para>
</caution>
<para>
- This section refers to file transfer and sharing servers.
- Please refer to the &WEB-SERVERS; and &SAMBA; sections for
+ 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>
@@ -23,7 +22,7 @@
<section id="sn-file-servers-netatalk-package">
<title><filename>netatalk</filename></title>
<para>
- &DISTRO; &DISTROVER; includes version 2 of Netatalk.
+ &FC; &LOCALVER; includes version 2 of Netatalk.
</para>
<caution>
<title>Take care when upgrading Netatalk versions</title>
Index: I18n-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/I18n-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- I18n-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ I18n-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -12,8 +12,7 @@
<note>
<title>IIIMF replaced</title>
<para>
- SCIM has replaced IIIMF in Fedora Core in this
- release.
+ SCIM has replaced IIIMF as the language input framework in &FC;.
</para>
</note>
</section>
Index: Installer-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Installer-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Installer-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Installer-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -2,13 +2,13 @@
<title>Installation-Related Notes</title>
<para>
This section outlines those issues that are related to Anaconda
- (the &DISTRO; installation program) and installing &DISTRO;
- &DISTROVER; in general.
+ (the &FC; installation program) and installing &FC;
+ &LOCALVER; in general.
</para>
<note>
<title>Note</title>
<para>
- If you intend to download the &DISTRO; &DISTROVER; DVD ISO image,
+ If you intend to download the &FC; &LOCALVER; DVD ISO image,
keep in mind that not all file downloading tools can accommodate
files larger than 2GiB in size. For example,
<command>wget</command> before version 1.9.1.16 in exits with a
@@ -30,95 +30,13 @@
url="http://torrent.fedoraproject.org/">http://torrent.fedoraproject.org/</ulink>
</para>
</note>
- <section id="sn-install-notes-ppc">
- <title>PPC Installation Notes</title>
- <para>
- The DVD or first CD of the installation set of &FC; is set to be
- bootable on supported hardware. In addition, bootable CD images
- can be found in the <filename>images/</filename> directory of
- the DVD or first CD. These behave differently according to the
- hardware:
- </para>
- <variablelist>
- <title>Boot Image Behavior by Hardware</title>
- <varlistentry>
- <term>Apple Macintosh </term>
- <listitem>
- <para>The bootloader automatically boots the appropriate
- 32-bit or 64-bit installer. Power management support,
- including sleep and backlight level management, is present
- in the <filename>apmud</filename> package, which is in
- &FEX;. &FEX; for &FC; is configured by default for yum.
- Following installation, <filename>apmud</filename> can be
- installed by running the command <command>yum install
- apmud</command> in a terminal.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>64-bit IBM eServer pSeries (POWER4/POWER5)</term>
- <listitem>
- <para>After using OpenFirmware to boot the CD, the
- bootloader (<command>yaboot</command>) automatically boots
- the 64-bit installer.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>32-bit CHRP (IBM RS/6000 and others)</term>
- <listitem>
- <para>After using OpenFirmware to boot the CD, select the
- <filename>linux32</filename> boot image at the
- <prompt>boot:</prompt> prompt to start the 32-bit installer.
- Otherwise, the 64-bit installer is started, which does not
- work.</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Genesi Pegasos II</term>
- <listitem>
- <para>As of &DISTRO; &DISTROVER;, 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 OpenFirmware prompt, enter the command:
- </para>
-<screen>
-<command>boot cd: /images/netboot/ppc32.img</command>
-</screen>
- <para>
- You also need to configure OpenFirmware on the Pegasos
- manually to make the installed &FC; system bootable. To do
- this, you need to set the <envar>boot-device</envar> and
- <envar>boot-file</envar> environment variables
- appropriately.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Network booting</term>
- <listitem>
- <para>There are combined images containing the installer
- kernel and ramdisk in the
- <filename>images/netboot/</filename> directory of the
- install tree. These are intended for network booting with
- TFTP, but can be used in many ways.
- </para>
- <para>
- The command <command>yaboot</command> supports TFTP
- booting for IBM eServer pSeries and Apple Macintosh. &FED;
- recommends using yaboot over the netboot images.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
<section id="sn-anaconda-notes">
<title>Anaconda Notes</title>
<itemizedlist>
<listitem>
<para>
- The &DISTRO; installation program has the ability to test
+ The &FC; 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. &RH;
recommends that you test all installation media before
@@ -148,26 +66,21 @@
</listitem>
<listitem arch="x86">
<para>
- <!-- <remark os="test">(x86)</remark> --> Memory testing may be
- performed prior to installing &DISTRO; by entering
- <command>memtest86</command> at the <prompt>boot:</prompt>
- prompt. This causes the Memtest86 standalone memory testing
- software to run. Memtest86 memory testing continues until the
- <keycap>Esc</keycap> key is pressed.
+ Memory testing may be performed prior to installing &FC; by
+ entering <command>memtest86</command> at the
+ <prompt>boot:</prompt> prompt. This causes the Memtest86
+ standalone memory testing software to run. Memtest86 memory
+ testing continues until the <keycap>Esc</keycap> key is
+ pressed.
</para>
<para>
- <!-- <remark os="test">(x86)</remark> --> NOTE: You must boot from
- CD-ROM 1 (or a rescue CD-ROM) in order to use this
- feature.
+ You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to
+ use this feature.
</para>
</listitem>
<listitem>
-<!-- <remark os="test">%%% <ulink
- url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136627</ulink>
- %%%</remark>
--->
<para>
- &DISTRO; &DISTROVER; supports graphical FTP and HTTP
+ &FC; &LOCALVER; supports graphical FTP and HTTP
installations. However, due to the necessity of containing
the installer image in RAM, only systems with more than 128MiB
of RAM (or systems booted from CD-ROM 1, which contains the
@@ -239,7 +152,7 @@
<para>
Certain hardware configurations (particularly those with
LCD displays) may experience problems while starting the
- &DISTRO; installation program. In these instances, restart
+ &FC; installation program. In these instances, restart
the installation, and add the <option>nofb</option> option
to the boot command line.
</para>
@@ -256,21 +169,18 @@
</listitem>
<listitem arch="x86">
<para>
-<!-- <remark os="test">(x86)</remark> --> Some Sony <trademark
- class="registered">VAIO</trademark> notebook systems may
- experience problems installing &DISTRO; from CD-ROM. If this
- happens, restart the installation process and add the
- following option to the boot command line:
+ Some Sony VAIO notebook systems may experience problems
+ installing &FC; from CD-ROM. If this happens, restart the
+ installation process and add the following option to the boot
+ command line:
</para>
<screen>
-<!-- <remark os="test">(x86)</remark> -->
<command>pci=off ide1=0x180,0x386</command>
</screen>
<para>
- <!-- <remark os="test">(x86)</remark> --> This option allows the
- installation to proceed normally; any devices not detected due
- to the use of this option will be configured the first time
- &DISTRO; is booted.
+ This option allows the installation to proceed normally; any
+ devices not detected due to the use of this option will be
+ configured the first time &FC; is booted.
</para>
</listitem>
<listitem>
@@ -287,8 +197,7 @@
</listitem>
<listitem arch="x86">
<para>
- <!-- <remark os="test">(x86)</remark> --> There have been
- issues observed when upgrading &RHL;
+ There have been issues observed when upgrading &RHL;
7.<replaceable><x></replaceable>, 8.0, 9, and &FC; 1, 2,
and 3 systems where third party packages are installed that
conflict with packages provided by &FP;. One example is
@@ -303,23 +212,21 @@
<orderedlist numeration="loweralpha">
<listitem>
<para>
- <!-- <remark os="test">(x86)</remark> -->You may remove
- Ximian GNOME from your system prior to upgrading to
- &DISTRO;.
+ You may remove Ximian GNOME from your system prior to
+ upgrading to &FC;.
</para>
</listitem>
<listitem>
<para>
- <!-- <remark os="test">(x86)</remark> -->You may upgrade
- your system, and then immediately reinstall Ximian GNOME.
+ You may upgrade your system, and then immediately
+ reinstall Ximian GNOME.
</para>
</listitem>
<listitem>
<para>
- <!-- <remark os="test">(x86)</remark> -->You may upgrade
- your system, and then immediately remove all remaining
- Ximian RPMs, replacing them with the corresponding
- &DISTRO; RPMs.
+ You may upgrade your system, and then immediately remove
+ all remaining Ximian RPMs, replacing them with the
+ corresponding &FC; RPMs.
</para>
</listitem>
</orderedlist>
Index: Kernel-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Kernel-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Kernel-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Kernel-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -31,6 +31,31 @@
<command>rpm -qpl kernel-<version>.src.rpm</command>
</screen>
</section>
+ <section id="sn-kernel-changelog">
+ <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 see <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
+ &FED; version is based on the Linus tree.
+ </para>
+
+ <para>
+ Customizations made for the &FED; version are available from
+ <ulink
+ url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink>
+ </para>
+ </section>
<section id="sn-kernel-flavors">
<title>Kernel Flavors</title>
<para>&FC; includes the following kernel builds: </para>
Index: Legacy-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Legacy-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Legacy-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Legacy-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -44,6 +44,16 @@
longer available in this release. NPTL has been the default
threading library since Red Hat Linux 9.
</para>
+ <para>
+ &FC; includes legacy system libraries for compatibility with older
+ software. This software is part of the "Legacy Software
+ Development" 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>
<!--
Local variables:
Index: OverView-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/OverView-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- OverView-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ OverView-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,361 +1,183 @@
-<section id="sn-overview">
- <title>Overview of What is New in &FC; &LOCALVER;</title>
- <itemizedlist>
- <listitem>
- <para>Xen virtualisation software and yum package manager are now
- well integrated within the &FED; installer. The installer
- interface is more streamlined. Remote logging and improved
- support for tracebacks is included.
- </para>
- </listitem>
- <listitem>
- <para><application>Pup</application>, a graphical updater using
- yum, has replaced <application>rhn-applet</application>.
- </para>
- </listitem>
- <listitem>
- <para>GNOME 2.12 and KDE 3.4 desktop environments are available.
- </para>
- </listitem>
- <listitem>
- <para>GNOME Power Manager and GNOME Screensaver are available as a
- technology preview within this release.
- </para>
- </listitem>
- <listitem>
- <para>
- OpenOffice.org 2.0 final release is included. OpenOffice.org now
- uses system versions for many of the libraries leading to
- increased performance and efficiency.
- </para>
- </listitem>
- <listitem>
- <para>Xorg X11R7 release candidate 2 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>
- </listitem>
- <listitem>
- <para>Kernel 2.6.14 is included. Software suspend is enabled in
- this release.
- </para>
- </listitem>
- <listitem>
- <para>SCIM has replaced IIMF in &FC; in this release.
- </para>
- </listitem>
- <listitem>
- <para>There are changes in the animated mouse cursor theme.
- </para>
- </listitem>
- <listitem>
- <para>&FP; now has a new logo.
- </para>
- </listitem>
- </itemizedlist>
- <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>.
+<section id="sn-overview-fedora-tour">
+ <title>&FC; &LOCALVER; Tour</title>
+
+ <para>
+ Welcome to Fedora. In this new exciting new release, we present you
+ a sneak preview of &FC; &LOCALVER; filled with pictures and videos
+ available at <ulink
+ url='http://fedoraproject.org/wiki/Tours/FedoraCore5'>http://fedoraproject.org/wiki/Tours/FedoraCore5</ulink>.
+ We request active participation from the community to test and
+ provide feedback to the developers for a robust and cutting edge
+ release of &FC; &LOCALVER;. Thank you for your interest in Fedora.
</para>
-</section>
-<!-- commented out until the content can be updated
- <section id="sn-overview">
- <title>New in &FC; &LOCALVER;</title>
- <para>
- &FC; &LOCALVER; is the latest version of the free and popular &FC;
- platform with a number of unique features and significant
- improvements over previous versions. This section provides an
- overview of the major highlights in this release.
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Desktop Enhancements — The &FED; desktop brings to you
- the latest software such as GNOME 2.10 and KDE 3.4 with a new
- look and feel. GNOME has the new simple and elegant Clearlooks
- default theme that is inspired by the classic Red Hat
- Bluecurve theme, as shown in <xref
- linkend="ex-desktop-screenshot-clearlooks"/>.
- </para>
- <example id="ex-desktop-screenshot-clearlooks">
- <title>New desktop featuring Clearlooks and Evince</title>
- <mediaobject id="txt-fedora-desktop-screenshot">
- <imageobject>
- <imagedata fileref="./figs/Fedora_Desktop.eps" format="EPS"/>
- </imageobject>
- <imageobject>
- <imagedata fileref="./figs/Fedora_Desktop.png" format="PNG"/>
- </imageobject>
- <textobject>
- <para>
- Screenshot of Fedora desktop showing Firefox in the
- background and the new universal document viewer Evince
- in the foreground. Evince is displaying Lawrence
- Lessig's Free Culture.
- </para>
- </textobject>
- </mediaobject>
- </example>
- </listitem>
- <listitem>
- <para>
- Improved Productivity
- </para>
- <itemizedlist>
- <listitem>
- <para>
- Evince (<ulink
- url="http://www.gnome.org/projects/evince/">http://www.gnome.org/projects/evince/</ulink>)
- is a document viewer for multiple document formats such as
- pdf, postscript, and many others. Evince replaces a whole
- category of document viewers with a single simple
- application.
- </para>
- </listitem>
- <listitem>
- <para>
- OpenOffice.org 2.0 (<ulink
- url="http://www.openoffice.org/product2/index.html">http://www.openoffice.org/product2/index.html</ulink>)
- is an office productivity suite. This latest version
- includes several enhancements such as improved Microsoft
- Office compatibility, completely revamped Impress
- presentation software, and native support for the
- OpenDocument format. This version also introduces Base, a
- fully integrated database management software. You can
- find the extensive list of new features at <ulink
- url="http://marketing.openoffice.org/2.0/featureguide.html">http://marketing.openoffice.org/2.0/featureguide.html</ulink>.</para>
- </listitem>
- <listitem>
- <para>
- Eclipse 3.1 is an open and extensible software development
- platform that is an Integrated Development Environment
- (<acronym>IDE</acronym>) useful for programming in any
- language.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- Support for PowerPC (PPC) Architecture — Refer to <xref
- linkend="sn-hardware-reqs-ppc"/> and <xref
- linkend="sn-install-notes-ppc"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- Improved Security — &SEL; is a security architecture
- that protects applications and users through finely grained
- mandatory security controls. The default targeted policy has
- been improved to cover 80 additional daemons. You can read
- more in the technical release notes
- <xref linkend="sn-overview"/>.
- </para>
- </listitem>
- <listitem>
- <para>
- Integrated Clustering Technology — Global File System
- (<acronym>GFS</acronym>) is an open source clustering file
- system that allows a cluster of Linux servers to share a
- common storage pool. &FC; &LOCALVER; has integrated GFS within
- the system to manage your storage in an efficient way. You
- can read more at <ulink
- url="http://www.redhat.com/software/rha/gfs/">http://www.redhat.com/software/rha/gfs/</ulink>
- and <ulink
- url="http://www.redhat.com/docs/manuals/enterprise/">http://www.redhat.com/docs/manuals/enterprise/</ulink>.
- </para>
- </listitem>
- <listitem>
- <para>
- Built-in Virtualization — Xen is a virtual machine that
- can securely run multiple operating systems in their own
- sandboxed domains. Xen has been integrated into &FC; to work
- in a seamless fashion. You can read more about Xen at <ulink
- url="http://fedora.redhat.com/projects/virtualization/">http://fedora.redhat.com/projects/virtualization/</ulink>.
- </para>
- </listitem>
- <listitem>
- <para>
- Solid Platform — &FC; &LOCALVER; includes and integrates
- the latest 4.0 version of GNU Compiler Collection, which has a
- rewritten optimization infrastructure and improved support for
- a native open source Java software stack. This stack includes
- parts of OpenOffice.org 2.0., Eclipse, and Apache Jakarta,
- among others.
- </para>
- </listitem>
- </itemizedlist>
- </section>
- <section id="sn-why-no-mp3">
- <title>MP3 Codecs and Other Patented or Closed Source Software</title>
- <para>
- This section is a brief explanation of why certain software is not
- included in &FC; or &FEX;. This information was drawn directly
- from the canonical wiki page:
- </para>
+ <note>
+ <title>Help With the Testing</title>
<para>
- <ulink
- url="http://fedoraproject.org/wiki/ForbiddenItems">http://fedoraproject.org/wiki/ForbiddenItems</ulink>
- </para>
- <para>
- A frequent question of the &FP; is why certain items are not
- included in &FC; or &FEX;. This briefly explains some of the
- reasons.
- </para>
- <para>
- Other items, such as file systems support, requires community
- participation. For more information, refer to <ulink
- url="http://fedoraproject.org/wiki/Wishlist">http://fedoraproject.org/wiki/Wishlist</ulink>
+ Please go through the following major changes with special care
+ and provide feedback to the <ulink
+ url="http://redhat.com/mailman/listinfo/fedora-test-list/">http://redhat.com/mailman/listinfo/fedora-test-list/</ulink>
+ mailing list.
</para>
+ </note>
+ <section id="sn-overview-newest">
+ <title>New in &FC; &LOCALVER;</title>
<variablelist>
<varlistentry>
- <term>NTFS</term>
+ <term>Desktop</term>
<listitem>
- <para>
- NTFS Support is not included in the &FC; kernel because of
- patent concerns. Using a file system natively supported by
- Linux such as ext3 is a better option. If you must share
- files between Windows and Linux on a single system, use
- FAT/FAT32 (vfat) instead. For sharing across a network,
- Samba is a good option.
+ <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 &FED;.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>MP3 encode/decode functionality</term>
+ <term>System Level Changes</term>
<listitem>
- <para>
- MP3 support is not included in any &FC; application because
- MP3 is heavily patented in several regions including the
- United States. The patent holder is unwilling to give an
- unrestricted patent grant, as required by the GPL. Other
- platforms might have paid the royalty and/or included
- proprietary software. Other Linux distributions not based in
- a region affected by the patent might ship MP3
- decoders/encoders. However, &FC; cannot and does not ship
- MP3 decoders/encoders in order to serve the goal of shipping
- only free and open source software. Using other open source
- formats such as Ogg Vorbis (a lossy codec that has better
- quality than MP3) or FLAC (a lossless codec) is highly
- recommended.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>NVIDIA 3D drivers</term>
- <listitem>
- <para>
- The NVIDIA 3D drivers are closed source. &FC; does not
- include proprietary binaries. Consider using an Intel or any
- other manufacturer that supports open source cards with full
- specifications and/or source code.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>ATI 3D drivers</term>
- <listitem>
- <para>
- The ATI 3D drivers are closed source. &FC; does not include
- proprietary binaries. Consider using an Intel or any other
- manufacturer that supports open source cards with full
- specifications and/or source code.
- </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ gcc 4.1 compiler is included and the entire set of &FED;
+ packages is now build using this new compiler version
+ which brings in new security and performance
+ enhancements.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The PCMCIA framework used by laptops and mobile devices
+ has changed with kernel version 2.6.13-rc1 onwards. The
+ older <filename>pcmcia-cs</filename> package using the
+ cardmgr/pcmcia service has been replaced with a new
+ <filename>pcmciautils</filename> package where the
+ PCMCIA devices are handled directly with the hotplug
+ system using udev dynamically in this &FED; release.
+ This increases both efficiency and performance of the
+ system. More information about these 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>
+ </listitem>
+ <listitem>
+ <para>
+ SELinux implementation has undergone a major change with
+ a switchover to the <firstterm>reference
+ policy</firstterm> (<ulink
+ url="http://serefpolicy.sourceforge.net/">http://serefpolicy.sourceforge.net/</ulink>)
+ instead of the targeted and strict policy mechanisms
+ used by previous versions of &FED;. The reference
+ policy provides better modularity, flexibility and
+ configurability, along with other enhancements. This
+ version also adds support for MCS (Multi Category
+ Security) enabled by default and MLS (Multi Level
+ Security) security sub-systems within the SELinux
+ framework.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
- <term>RealPlayer</term>
+ <term>Desktop</term>
<listitem>
- <para>
- RealPlayer is a closed source application. &FC; does not
- include proprietary binaries. Consider using open source
- codecs that do not have patent restrictions.
- </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ GNOME 2.13.2 and KDE 3.5 Release Candidate 2 desktop
+ environments are available.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ GNOME Power Manager and GNOME Screensaver are available
+ as a technology preview within this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ OpenOffice.org 2.0 final release is included.
+ OpenOffice.org now uses system versions for many of the
+ libraries leading to increased performance and
+ efficiency.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Xorg X11R7 Release Candidate 3 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>
+ </listitem>
+ <listitem>
+ <para>
+ Kernel 2.6.14 is included. Software suspend is enabled
+ in this release.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Pup, a graphical updater using yum, is available in this
+ release.
+ </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>
+ </listitem>
+ <listitem>
+ <para>
+ &FED; now sports a brand new logo and changes in the
+ animated mouse cursor theme.
+ </para>
+ </listitem>
+ </itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
- <term>DVD video playback</term>
+ <term>System Administration</term>
<listitem>
<para>
- DVD video playback (of CSS encrypted DVDs) may violate the
- US DMCA (refer to <ulink
- url="http://en.wikipedia.org/wiki/DMCA">http://en.wikipedia.org/wiki/DMCA</ulink>)
- because it may be considered circumventing an encryption
- mechanism. Additionally, MPEG2 is a patented codec, so even
- DVDs without encryption cannot be played. Consider using
- open source unencrypted mediums such as Ogg Theora formats.
+ System Tap (<ulink
+ url='http://sourceware.org/systemtap/'>http://sourceware.org/systemtap/</ulink>)
+ is an instrumentation system for debugging and analysing
+ performance bottlenecks, which is included in this release.
</para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Mono</term>
- <listitem>
<para>
- Mono packages are not currently included due to potential
- legal issues. (Pending more input.) Applications can be
- written in other languages that are open source, such as
- Python, Perl, or Ruby. Java is cross-platform and GCJ is a
- relatively mature open source implementation of it. These
- are not direct one-to-one equivalents with .NET but might
- serve your purpose.
+ Frysk (<ulink
+ url='http://sourceware.org/frysk/'>http://sourceware.org/frysk/</ulink>)
+ is an execution analysis technology for monitoring running
+ processes or threads, and is included within this release.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>Cryptology (mcrypt)</term>
+ <term>System Level Changes</term>
<listitem>
<para>
- Some cryptology related packages such as mcrypt are not
- included within &FC; due to US export restrictions. Consider
- using non-restricted cryptographical methods instead.
+ Xen Virtualisation software and <command>yum</command>
+ package manager are now well integrated within the &FED;
+ installer. The installer interface is more streamlined.
+ Remote logging and improved support for tracebacks is
+ included.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>szip</term>
- <listitem>
+ <term>Road Map</term>
<para>
- The szip license is too restrictive for inclusion in &FEX;.
- Use other open source alternatives.
- </para>
- </listitem>
+ The proposed plans for &FED; in this version are available
+ from <ulink
+ url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
+ </para>
</varlistentry>
</variablelist>
- <para>
- In conclusion:
- </para>
- <itemizedlist>
- <listitem>
- <para> If it is proprietary, it cannot be included in &FED;.
- </para>
- </listitem>
- <listitem>
- <para>
- If it is legally encumbered, it cannot be included in &FED;.
- </para>
- </listitem>
- <listitem>
- <para>
- If it violates US Federal law, it cannot be included in &FED;.
- </para>
- </listitem>
- </itemizedlist>
- <para>
- Of course, the logical followup is: "But I want to get foo and do
- bar, how can I do one of the items listed above?"
- </para>
- <para>
- The unofficial <ulink
- url="http://fedorafaq.org">http://fedorafaq.org</ulink> provides
- useful answers on commonly asked questions. However, these are
- completely unsupported by the &FP;. The &FP; encourages using free
- and open source software.
- </para>
- <para>
- The binary only drivers can be acquired from the vendors. You can
- find many interesting things with Google.
- </para>
</section>
+</section>
-->
<!--
Local variables:
@@ -364,3 +186,4 @@
fill-column: 72
End:
-->
+
Index: PackageChanges-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/PackageChanges-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PackageChanges-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ PackageChanges-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1042,7 +1042,7 @@
<para>magma-plugins-1.0-0.pre18.3 </para>
</section>
</section>
- <section id="sn-package-notes">
+ <section id="sn-package-misc">
<title>Package Notes</title>
<para>
<application>system-config-mouse</application> configuration
Index: ProjectOverview-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ProjectOverview-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ProjectOverview-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ProjectOverview-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,72 +1,82 @@
- <section id="sn-whatitis">
- <title>An Overview of the &PROJ;</title>
- <para>
- The goal of the &PROJ; 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 &DISTRO; approximately
- 2-3 times a year, with a public release schedule. The &RH;
- engineering team continues to participate in building &DISTRO;
- 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 &PROJ; website:
- </para>
- <para>
- <ulink
- url="http://fedora.redhat.com/">http://fedora.redhat.com/</ulink>
- </para>
- <para>
- In addition to the website, the following mailing lists are
- available:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- fedora-list at redhat.com — For users of &DISTRO; releases
- </para>
- </listitem>
- <listitem>
- <para>
- fedora-test-list at redhat.com — For testers of &DISTRO;
- test releases
- </para>
- </listitem>
- <listitem>
- <para>
- fedora-devel-list at redhat.com — For developers,
- developers, developers
- </para>
- </listitem>
- <listitem>
- <para>
- fedora-docs-list at redhat.com — For participants of the
- Documentation Project
- </para>
- </listitem>
+<section id="sn-whatitis">
+ <title>An Overview of the &FP;</title>
+ <para>
+ The goal of the &FP; 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 &FC; approximately 2-3 times a year,
+ with a public release schedule. The &RH; engineering team continues
+ to participate in building &FC; 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 &FP; 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 &FP; look at <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>
+ fedora-list at redhat.com — For users of &FC; releases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ fedora-test-list at redhat.com — For testers of &FC; test
+ releases
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ fedora-devel-list at redhat.com — For developers, developers,
+ developers
+ </para>
+ </listitem>
<listitem>
<para>
- fedora-ambassadors-list at redhat.com — For community
- members who represent the &PROJ; in public.
+ fedora-docs-list at redhat.com — For participants of the
+ Documentation Project
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ fedora-ambassadors-list at redhat.com — For community members
+ who represent the &FP; in public.
</para>
</listitem>
</itemizedlist>
<para>
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
- <computeroutput><replaceable><listname></replaceable>-request</computeroutput>
+ <computeroutput><replaceable><listname></replaceable>-request</computeroutput>
(where
- <computeroutput><replaceable><listname></replaceable></computeroutput>
+ <computeroutput><replaceable><listname></replaceable></computeroutput>
is one of the above list names.)
</para>
<para>
Alternately, you can subscribe through the Web interface:
</para>
<para>
- <ulink url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
+ <ulink
+ url="http://www.redhat.com/mailman/listinfo/">http://www.redhat.com/mailman/listinfo/</ulink>
</para>
<!-- Aren't we quite past this? Saving just in case we are not.
<para>
@@ -76,37 +86,37 @@
</para>
-->
<para>
- The &PROJ; 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 &PROJ; participants via IRC, access freenode IRC
- network. Initially, you can use <filename>irc.freenode.net</filename> as
- the IRC server, although you may decide to select a server that is
- geographically closer to you. Refer to the freenode website (<ulink
- url="http://www.freenode.net/">http://www.freenode.net/</ulink>) for more
- information. &PROJ; participants frequent the
- <filename>#fedora</filename> channel, while &PROJ; developers can often be
- found on the <filename>#fedora-devel</filename> channel. Some of the
- larger projects may have their own channels as well; this information can
- be found on the project pages.
- </para>
+ The &FP; 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 &FP; participants via IRC, access freenode IRC
+ network. Initially, you can use
+ <filename>irc.freenode.net</filename> as the IRC server, although
+ you may decide to select a server that is geographically closer to
+ you. Refer to the freenode website (<ulink
+ url="http://www.freenode.net/">http://www.freenode.net/</ulink>)
+ for more information. &FP; participants frequent the
+ <filename>#fedora</filename> channel, while &FP; developers can
+ often be found on the <filename>#fedora-devel</filename> channel.
+ Some of the larger projects may have their own channels as well;
+ this information can be found on the project pages.
+ </para>
+ <para>
+ In order to talk on the <filename>#fedora</filename> channel, you
+ will need to register your nickname (<firstterm>nick</firstterm>).
+ Instructions are given when you first <command>/join</command> the
+ channel.
+ </para>
+ <note>
+ <title>Note</title>
<para>
- In order to talk on the <filename>#fedora</filename> channel, you
- will need to register your nickname (<firstterm>nick</firstterm>).
- Instructions are given when you first <command>/join</command> the
- channel.
+ &RH; has no control over the &FP; IRC channels or their content.
</para>
- <note>
- <title>Note</title>
- <para>
- &RH; has no control over the &PROJ; IRC channels or their
- content.
- </para>
- </note>
- </section>
+ </note>
+</section>
<!--
Local variables:
mode: xml
Index: RELEASE-NOTES-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-en.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- RELEASE-NOTES-en.xml 6 Jan 2006 00:26:46 -0000 1.14
+++ RELEASE-NOTES-en.xml 9 Jan 2006 12:28:41 -0000 1.15
@@ -47,11 +47,11 @@
<!-- *************** Local entities *************** -->
+ <!ENTITY LOCALVER "5 test2"> <!-- Set value to your choice, when guide version is out -->
<!ENTITY DOCNAME "RELEASE-NOTES">
<!ENTITY DOCVERSION "&FCX;&DISTROVER;">
- <!ENTITY DOCDATE "2005-11-24-T23:10+0000">
+ <!ENTITY DOCDATE "2005-01-05-T16:20+0800">
<!ENTITY DOCID "&DOCNAME;-&DOCVERSION; (&DOCDATE;)"> <!-- version of manual and date -->
- <!ENTITY LOCALVER "5 test1"> <!-- Set value to your choice, when guide version is out -->
<!-- of sync with FC release, use instead of FEDVER or FEDTESTVER -->
<!ENTITY NAME "Fedora"> <!-- The project's (and software's) basic name -->
<!ENTITY PROJ "&FP;"> <!-- The project's name -->
@@ -63,11 +63,11 @@
<!ENTITY TINY-BUG-URL "http://tinyurl.com/byvk2">
]>
-<article id="index" lang="en" arch="x86;x86_64;ppc" os="test;final">
+<article id="index" lang="en">
<articleinfo>
- <title>&DISTRO; &DISTROVER; Release Notes (latest)</title>
+ <title>&FC; &LOCALVER; Release Notes (latest)</title>
<copyright>
- <year>2005</year>
+ <year>2006</year>
<holder>&FORMAL-RHI;</holder>
</copyright>
&LEGALNOTICE-RELNOTES;
Index: Samba-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Samba-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Samba-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Samba-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -6,48 +6,20 @@
of software that enables Linux to interact with Microsoft Windows
systems.
</para>
+
+ <section id="sn-samba-smb-browsing">
+ <title>SMB Browsing</title>
- <para>
- Browsing of Windows shares (also known as SMB browsing) fails
- on &DISTRO; &DISTROVER; systems that have the standard firewall
- configured. This is most easily noticed in the failure of the
- desktop to display shares.
- </para>
-
- <para>
- The firewall disrupts the broadcast mode of SMB browsing, which is the
- default. There are two workarounds:
- </para>
-
- <itemizedlist>
- <listitem>
- <para>
- Configure a WINS server on the network, and set the "wins
- server" option in smb.conf to the address of the WINS server.
- </para>
- </listitem>
- <listitem>
- <para>
- Disable the firewall.
- </para>
- </listitem>
- </itemizedlist>
-
- <warning>
- <title>Disabling the firewall may make your system vulnerable</title>
<para>
- Make sure you fully understand the risks before undertaking this
- step.
+ Browsing of Windows shares (also known as SMB browsing) is now
+ possible. In releases prior to &FC; &LOCALVER;, the firewall
+ prevented the proper function of SMB browsing. With the addition
+ of the <filename>ip_conntrack_netbios_ns</filename> kernel module
+ to the 2.6.14 kernel and corresponding enhancements to
+ <application>system-config-securitylevel</application>, the
+ firewall now properly tracks SMB browse broadcasts.
</para>
- </warning>
-
- <para>
- For additional information, refer to the following bug report:
- </para>
-
- <para>
- <ulink url="https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478">https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478</ulink>
- </para>
+ </section>
</section>
<!--
Local variables:
Index: Security-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Security-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- Security-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ Security-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,80 +1,116 @@
<section id="sn-security">
<title>Security</title>
+
<para>
This section highlights various security items from &FC;.
</para>
- <para>
- <computeroutput>Pam_stack</computeroutput> is deprecated. Linux-PAM
- 0.78 and later contain the include directive that obsoletes the
- <computeroutput>pam_stack</computeroutput> module.
- <computeroutput>pam_stack</computeroutput> module usage is logged
- with a deprecation warning. It might be removed in a future
- release.
- </para>
- <section id="sn-security-highlights">
- <title>Security Highlights</title>
+
+ <section id="sn-security-general-info">
+ <title>General Information</title>
+
<para>
- This section highlights various security items from &FC;.
+ General introduction to the many proactive security features in
+ &FED;, current status and policies is available from the <ulink
+ url="http://fedoraproject.org/wiki/Security/Security">http://fedoraproject.org/wiki/Security</ulink>
+ page.
</para>
- <variablelist>
- <varlistentry>
- <term>Buffer Overflow detection and variable reordering</term>
- <listitem>
- <para>For this release, all of the software in the &FC; and
- &FEX; software repositories is compiled using a security
- feature called <firstterm>fstack-protecter</firstterm>.
- fstack-protector puts a canary value on the stack of
- <computeroutput>key</computeroutput> functions. Just before
- the return address and just before returning from that
- value, that canary value is verified. If there was a buffer
- overflow, the canary no longer matches 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 that has been
- backported from GCC 4.1 to the version of the GCC compiler
- used in &FC; &LOCALVER;.
- </para>
- <para>
- This is in addition to using <envar>FORTIFY_SOURCE</envar>
- from &FC; 4 onwards.
- </para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>Digital certificates</term>
- <listitem>
- <para>
- Digital certificates are now centralised in directories
- under <filename>/etc/pki/</filename>. Users performing an
- upgrade must relocate their digital certificates.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>OpenSSL</term>
- <listitem>
- <para>
- For OpenSSL, the <filename>/usr/share/ssl/</filename>
- contents have moved to <filename>/etc/pki/tls/</filename>
- and <filename>/etc/pki/CA/</filename>.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Dovecot</term>
- <listitem>
- <para>
- The <filename>dovecot-openssl.cnf</filename> file is
- automatically installed in
- <filename>/etc/pki/dovecot/</filename>.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
</section>
- &SECURITY-SELINUX;
+
+ <section id="sn-security-newest">
+ <title>What's New</title>
+
+ <section>
+ <title>PAM module Deprecation</title>
+
+ <para>
+ <filename>Pam_stack</filename> is deprecated in this release.
+ Linux-PAM 0.78 and later contains the include directive, which
+ obsoletes the <filename>pam_stack</filename> module. The
+ <filename>pam_stack</filename> 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 &FC; using PAM were modified to not use
+ <filename>pam_stack</filename>. However, when a system is
+ upgraded from previous Fedora Core releases and the
+ admininstrator previously modified some service configurations,
+ those security configurations are not replaced. Instead they are
+ created as <filename>.rpmnew</filename> files and continue to
+ call upon <filename>pam_stack</filename>. Such service
+ configurations must be fixed so the
+ <filename>pam_stack</filename> module is not used. Refer to the
+ <filename>.rpmnew</filename> files for the actual changes
+ needed.
+ </para>
+
+ <para>
+ Example using <filename>/etc/pam.d/login</filename>:
+ </para>
+
+<screen>
+#%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
+#%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
+</screen>
+ </section>
+
+ <section id="sn-security-buffer-overflow-detection">
+ <title>Buffer Overflow detection and variable reordering</title>
+
+ <para>
+ All of the software in the &FC; and &FEX; software
+ repositories for this release are compiled using a security feature
+ called <firstterm>fstack-protecter</firstterm>. fstack-protector
+ puts a canary value on the stack of key functions, just before
+ the return address and just before returning from that value.
+ That 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, making it impossible to guess remotely. This is a
+ security feature written by &RH; developers as a port of the
+ IBM ProPolice/SSP (<ulink
+ url="http://www.research.ibm.com/trl/projects/security/ssp/">http://www.research.ibm.com/trl/projects/security/ssp/</ulink>
+ feature and available as part of GCC 4.1 compiler used in &FC;
+ &LOCALVER;.
+ </para>
+ <para>
+ This is in addition to using FORTIFY_SOURCE from &FC; 4
+ onwards.
+ </para>
+ </section>
+ &SECURITY-SELINUX;
+ </section>
</section>
+
+
<!--
Local variables:
mode: xml
Index: SecuritySELinux-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/SecuritySELinux-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SecuritySELinux-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ SecuritySELinux-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,8 +1,8 @@
<section id="sn-security-selinux-changes">
<title>SELinux Changes</title>
<para>
- Mult-Category Security (MCS) SELinux is included in &FC; &LOCALVER;.
- For more information, read this informative article:
+ Multi-Category Security (MCS) SELinux is included in &FC;
+ &LOCALVER;. For more information, read this informative article:
</para>
<para>
<ulink
Index: ServerTools-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/ServerTools-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- ServerTools-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ ServerTools-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,23 +1,73 @@
<section id="sn-server-sys-config">
<title>Server and System Configuration Tools</title>
- <caution>
- <title>Information Out-of-Date</title>
- <para>
- The content in this section needs to be updated for &DISTRO;
- &DISTROVER;
- </para>
- </caution>
+
<para>
- This section highlights changes and additions to the various GUI server
- and system configuration tools in &FC;.
+ This section highlights changes and additions to the various GUI
+ server and system configuration tools in &FC;.
</para>
- <section id="sn-system-config-lvm">
- <title><application>system-config-lvm</application></title>
- <para>
- The new LVM tool <application>system-config-lvm</application>
- assists you in managing logical volumes.
- </para>
- </section>
+ <variablelist>
+ <varlistentry>
+ <term><application>system-config-printer</application></term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>SMB Browsing Outside Local Network</para>
+ <para>
+ Browsing for Samba print shares across subnets is now
+ possible. In addition, if at least one WINS server has
+ been specified in
+ <filename>/etc/samba/smb.conf</filename>, the first
+ address specified will be used when browsing.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Kerberos Support for SMB Printers</para>
+ <para>
+ The <application>system-config-printer</application>
+ application supports Kerberos authentication when adding a
+ new SMB printer. To add the printer, the user must possess
+ a valid Kerberos ticket and
+ <filename>/usr/sbin/printconf-gui</filename> must be
+ launched via <command>sudo</command>. No username and
+ password is stored in
+ <filename>/etc/cups/printers.conf</filename>. Printing is
+ still possible if the SMB print queue permits anonymous
+ printing.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>system-config-securitylevel</term>
+ <listitem>
+ <itemizedlist>
+ <listitem>
+ <para>Trusted Service Additions</para>
+ <para>
+ Samba is now listed in the "Trusted services" list and can
+ thus be enabled to permit the firewall to pass SMB
+ traffic.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Port Ranges</para>
+ <para>
+ When defining <guilabel>Other Ports</guilabel> in the
+ <application>system-config-securitylevel</application>
+ tool, port ranges can now be specified. For example,
+ specifying <userinput>6881-6999:tcp</userinput> results in
+ the addition of the following line to
+ <filename>/etc/sysconfig/iptables</filename> :
+ </para>
+<screen>
+A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 -j ACCEPT
+</screen>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</section>
<!--
Local variables:
Index: SystemDaemons-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/SystemDaemons-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SystemDaemons-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ SystemDaemons-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,4 +1,4 @@
-<section id="sn-daemons">
+<!-- <section id="sn-daemons">
<title>System Services</title>
<caution>
<title>Information Out-of-Date</title>
@@ -28,6 +28,7 @@
</screen>
</section>
</section>
+-->
<!--
Local variables:
mode: xml
Index: WebServers-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/WebServers-en.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- WebServers-en.xml 5 Jan 2006 19:22:24 -0000 1.1
+++ WebServers-en.xml 9 Jan 2006 12:28:41 -0000 1.2
@@ -1,25 +1,171 @@
<section id="sn-web-servers">
<title>Web Servers</title>
+
<para>
This section contains information on Web-related applications.
</para>
+
+ <section id="sn-web-servers-apache">
+ <title><command>httpd</command> a.k.a. Apache HTTP Server.</title>
+
+ <para>
+ Version 2.2 of the Apache HTTP Server is now included in &FC;.
+ This release brings a number of improvements since the 2.0 series,
+ including:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ greatly improved caching modules
+ (<filename>mod_cache</filename>,
+ <filename>mod_disk_cache</filename>,
+ <filename>mod_memcache</filename>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ refactored authentication and authorization support
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ support for proxy load balancing
+ (<filename>mod_proxy_balance</filename>)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ large file support for 32-bit platforms (including support for
+ >2Gb request bodies)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ new modules <filename>mod_dbd</filename> and
+ <filename>mod_filter</filename> bring SQL database support and
+ enhanced filtering
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The following changes have been made to the default
+ <command>httpd</command> configuration:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ the <filename>mod_cern_meta</filename> and
+ <filename>mod_asis</filename> modules are no longer loaded by
+ default
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ the <filename>mod_ext_filter</filename> module is now loaded
+ by default
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Any third-party modules compiled for <filename>httpd</filename>
+ 2.0 must be rebuilt for <filename>httpd</filename> 2.2.
+ </para>
+
+ <para>
+ Any existing configuration files might need adapting for 2.2;
+ refer to <ulink
+ url="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</ulink>
+ for more information.
+ </para>
+ </section>
+
<section>
- <title><command>httpd</command></title>
+ <title>php</title>
+
<para>
- The following changes have been made to the default <command>httpd</command>
- configuration:
+ Version 5.1 of PHP is now included in &FC;. This release brings a
+ number of improvements since PHP 5.0, including:
</para>
+
<itemizedlist>
<listitem>
- <para>The <computeroutput>mod_cern_meta</computeroutput> and
- <computeroutput>mod_asis</computeroutput> modules are no
- longer loaded by default.
- </para>
+ <para>
+ improved performance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ addition of the PDO database abstraction module
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The following extension modules have been added:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>pdo</filename> (in the <filename>php-pdo</filename>
+ package)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>pdo_sqlite</filename> (in the
+ <filename>php-sqlite</filename> package)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>pdo_mysql</filename> (in the
+ <filename>php-mysql</filename> package)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>pdo_pgsql</filename> (in the
+ <filename>php-pgsql</filename> package)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>pdo_odbc</filename> (in the
+ <filename>php-odbc</filename> package)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>xmlreader</filename> (in the
+ <filename>php-xml</filename> package)
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The following extension modules are no longer built:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ <filename>dbx</filename>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <filename>dio</filename>
+ </para>
</listitem>
<listitem>
- <para>The <computeroutput>mod_ext_filter</computeroutput> module
- is now loaded by default.
- </para>
+ <para>
+ <filename>yp</filename>
+ </para>
</listitem>
</itemizedlist>
</section>
Index: Welcome-en.xml
===================================================================
RCS file: /cvs/docs/release-notes/Welcome-en.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Welcome-en.xml 9 Jan 2006 10:04:19 -0000 1.2
+++ Welcome-en.xml 9 Jan 2006 12:28:41 -0000 1.3
@@ -15,24 +15,28 @@
users.
</para>
<para>
- Subscribe to the <ulink url="https://www.redhat.com/mailman/listinfo/fedora-test-list/">fedora-test</ulink> and <ulink url="https://www.redhat.com/mailman/listinfo/fedora-devel-list">fedora-devel</ulink> mailing lists to
- keep track of important changes in the current development
- versions and provide feedback to the developers. &FP; requests you
- to file bug reports and enhancements to provide a improved final
- release to end users. For more information on this, refer to the
- following document:
+ Subscribe to the <ulink
+ url="https://www.redhat.com/mailman/listinfo/fedora-test-list/">fedora-test</ulink>
+ and <ulink
+ url="https://www.redhat.com/mailman/listinfo/fedora-devel-list">fedora-devel</ulink>
+ mailing lists to keep track of important changes in the current
+ development versions and provide feedback to the developers. &FP;
+ requests you to file bug reports and enhancements to provide a
+ improved final release to end users. For more information on this,
+ refer to the following document:
</para>
<para>
<ulink
url="http://fedoraproject.org/wiki/BugsAndFeatureRequests">http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>.
+
</para>
</caution>
<tip>
<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>
+ url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
to view the latest release notes for &DISTRO; &DISTROVER;.
</para>
</tip>
@@ -66,25 +70,26 @@
</listitem>
<listitem>
<para>
- <ulink url="http://fedoraproject.org/wiki/FAQ/">Fedora FAQ</ulink>
+ <ulink url="http://fedoraproject.org/wiki/FAQ/">Fedora
+ FAQ</ulink>
</para>
</listitem>
<listitem>
<para>
Help and Support (<ulink
- url="http://fedora.redhat.com/participate/communicate/">http://fedora.redhat.com/participate/communicate/</ulink>)
+ url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>)
</para>
</listitem>
<listitem>
<para>
- Participate in the &FP; (<ulink
- url="http://fedora.redhat.com/participate/">http://fedora.redhat.com/participate/</ulink>)
+ Participate in the Fedora Project (<ulink
+ url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>)
</para>
</listitem>
<listitem>
<para>
- About the &FP; (<ulink
- url="http://fedora.redhat.com/about/">http://fedora.redhat.com/about/</ulink>)
+ About the Fedora Project (<ulink
+ url='http://fedora.redhat.com/About/'>http://fedora.redhat.com/About/</ulink>)
</para>
</listitem>
</itemizedlist>
More information about the Fedora-docs-commits
mailing list