release-notes/devel/en_US ArchSpecific.xml, NONE, 1.1 ArchSpecificPPC.xml, NONE, 1.1 ArchSpecificx86.xml, NONE, 1.1 ArchSpecificx86_64.xml, NONE, 1.1 BackwardsCompatibility.xml, NONE, 1.1 Colophon.xml, NONE, 1.1 DatabaseServers.xml, NONE, 1.1 Desktop.xml, NONE, 1.1 DevelTools.xml, NONE, 1.1 DevelToolsGCC.xml, NONE, 1.1 Entertainment.xml, NONE, 1.1 Extras.xml, NONE, 1.1 Feedback.xml, NONE, 1.1 FileServers.xml, NONE, 1.1 FileSystems.xml, NONE, 1.1 I18n.xml, NONE, 1.1 Installer.xml, NONE, 1.1 Java.xml, NONE, 1.1 Kernel.xml, NONE, 1.1 Legacy.xml, NONE, 1.1 Multimedia.xml, NONE, 1.1 Networking.xml, NONE, 1.1 OverView.xml, NONE, 1.1 PackageChanges.xml, NONE, 1.1 PackageNotes.xml, NONE, 1.1 Printing.xml, NONE, 1.1 ProjectOverview.xml, NONE, 1.1 RELEASE-NOTES.xml, NONE, 1.1 Samba.xml, NONE, 1.1 Security.xml, NONE, 1.1 SecuritySELinux.xml, NONE, 1.1 ServerTools.xml, NONE, 1.1 SystemDaemons.xml, NONE, 1.1 Virtualization.xml, NONE, 1.1 WebServers.xml, NONE, 1.1 Welcome.xml, NONE, 1.1 Xorg.xml, NONE, 1.1
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Tue Jun 27 21:54:43 UTC 2006
- Previous message (by thread): release-notes/devel/css content.css, NONE, 1.1 docbook.css, NONE, 1.1 layout.css, NONE, 1.1 print.css, NONE, 1.1
- Next message (by thread): release-notes/devel/figs Fedora_Desktop.eps, NONE, 1.1 Fedora_Desktop.png, NONE, 1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: pfrields
Update of /cvs/docs/release-notes/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv7999/en_US
Added Files:
ArchSpecific.xml ArchSpecificPPC.xml ArchSpecificx86.xml
ArchSpecificx86_64.xml BackwardsCompatibility.xml Colophon.xml
DatabaseServers.xml Desktop.xml DevelTools.xml
DevelToolsGCC.xml Entertainment.xml Extras.xml Feedback.xml
FileServers.xml FileSystems.xml I18n.xml Installer.xml
Java.xml Kernel.xml Legacy.xml Multimedia.xml Networking.xml
OverView.xml PackageChanges.xml PackageNotes.xml Printing.xml
ProjectOverview.xml RELEASE-NOTES.xml Samba.xml Security.xml
SecuritySELinux.xml ServerTools.xml SystemDaemons.xml
Virtualization.xml WebServers.xml Welcome.xml Xorg.xml
Log Message:
Add content copied from FC-5 branch; this directory is where we will builg FC-6 release notes
--- NEW FILE ArchSpecific.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ArchSpecific">
<title>Architecture Specific Notes</title>
<para>This section provides notes that are specific to the supported hardware architectures of Fedora Core. </para>
<!-- Arch Specific PPC -->
<xi:include href="./ArchSpecificPPC.xml" xpointer="element(sn-ArchSpecificPPC)"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- Arch Specific x86 -->
<xi:include href="./ArchSpecificx86.xml" xpointer="element(sn-ArchSpecificx86)"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<!-- Arch Specific x86_64 -->
<xi:include href="./ArchSpecificx86_64.xml" xpointer="element(sn-ArchSpecificx86_64)"
xmlns:xi="http://www.w3.org/2001/XInclude" />
</section>
</article>
--- NEW FILE ArchSpecificPPC.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ArchSpecificPPC">
<title>PPC Specifics for Fedora</title>
<para>
This section covers any specific information you may need to know
about Fedora Core and the PPC hardware platform.
</para>
<section>
<title>PPC Hardware Requirements</title>
<section>
<title>Processor and Memory</title>
<itemizedlist>
<listitem>
<para>
Minimum CPU: PowerPC G3 / POWER4
</para>
</listitem>
<listitem>
<para>
Fedora Core 5 supports only the “New World†generation
of Apple Power Macintosh, shipped from circa 1999 onward.
</para>
</listitem>
<listitem>
<para>
Fedora Core 5 also supports IBM eServer pSeries, IBM
RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine
machines.
</para>
</listitem>
<listitem>
<para>
Recommended for text-mode: 233 MHz G3 or better, 128MiB
RAM.
</para>
</listitem>
<listitem>
<para>
Recommended for graphical: 400 MHz G3 or better, 256MiB
RAM.
</para>
</listitem>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the disk
space taken up by Fedora Core 5 after installation is
complete. However, additional disk space is required during
installation to support the installation environment. This
additional disk space corresponds to the size of
<code>/Fedora/base/stage2.img</code>
(on Installtion Disc 1) plus the size of the files in
<code>/var/lib/rpm</code>
on the installed system.
</para>
<para>
In practical terms, additional space requirements may range
from as little as 90 MiB for a minimal installation to as
much as an additional 175 MiB for an "everything"
installation. The complete packages can occupy over 9 GB of
disk space.
</para>
<para>
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
</para>
</section>
</section>
<section>
<title>The Apple keyboard</title>
<para>
The <code>Option</code> key on Apple systems is equivalent to the
<code>Alt</code> key on the PC. Where documentation and the installer
refer to the <code>Alt</code> key, use the <code>Option</code> key.
For some key combinations you may need to use the <code>Option</code>
key in conjunction with the <code>Fn</code> key, such as
<code>Option</code> - <code>Fn</code> - <code>F3</code> to switch to
virtual terminal tty3.
</para>
</section>
<section>
<title>PPC Installation Notes</title>
<para>
Fedora Core Installation Disc 1 is bootable on supported
hardware. In addition, a bootable CD image appears in the
<code>images/</code>
directory of this disc. These images will behave differently
according to your system hardware:
</para>
<itemizedlist>
<listitem>
<para>
Apple Macintosh
</para>
<para>
The bootloader should automatically boot the appropriate
32-bit or 64-bit installer.
</para>
<para>
The default
<code>gnome-power-manager</code>
package includes power management support, including sleep
and backlight level management. Users with more complex
requirements can use the
<code>apmud</code>
package in Fedora Extras. Following installation, you can
install
<code>apmud</code>
with the following command:
</para>
<itemizedlist>
<listitem>
<screen>su -c 'yum install apmud'</screen>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
64-bit IBM eServer pSeries (POWER4/POWER5)
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to boot
the CD, the bootloader (yaboot) should automatically boot
the 64-bit installer.
</para>
</listitem>
<listitem>
<para>
32-bit CHRP (IBM RS/6000 and others)
</para>
<para>
After using Open<emphasis role='strong'/>Firmware to boot
the CD, select the
<code>linux32</code>
boot image at the
<code>boot:</code>
prompt to start the 32-bit installer. Otherwise, the
64-bit installer starts, which does not work.
</para>
</listitem>
<listitem>
<para>
Genesi Pegasos II
</para>
<para>
At the time of writing, firmware with full support for
ISO9660 file systems is not yet released for the Pegasos.
However, you can use the network boot image. At the
Open<emphasis role='strong'/>Firmware prompt, enter the
command:
</para>
<itemizedlist>
<listitem>
<screen>boot cd: /images/netboot/ppc32.img</screen>
</listitem>
</itemizedlist>
<para>
You must also configure
Open<emphasis role='strong'/>Firmware on the Pegasos
manually to make the installed Fedora Core system
bootable. To do this, set the
<code>boot-device</code>
and
<code>boot-file</code>
environment variables appropriately.
</para>
</listitem>
<listitem>
<para>
Network booting
</para>
<para>
You can find combined images containing the installer
kernel and ramdisk in the
<code>images/netboot/</code>
directory of the installation tree. These are intended for
network booting with TFTP, but can be used in many ways.
</para>
<para>
<code>yaboot</code>
supports TFTP booting for IBM eServer pSeries and Apple
Macintosh. The Fedora Project encourages the use of
<code>yaboot</code>
over the
<code>netboot</code>
images.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE ArchSpecificx86.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ArchSpecificx86">
<title>x86 Specifics for Fedora</title>
<para>
This section covers any specific information you may need to know
about Fedora Core and the x86 hardware platform.
</para>
<section>
<title>x86 Hardware Requirements</title>
<para>
In order to use specific features of Fedora Core during or after
installation, you may need to know details of other hardware
components such as video and network cards.
</para>
<section>
<title>Processor and Memory Requirements</title>
<para>
The following CPU specifications are stated in terms of Intel
processors. Other processors, such as those from AMD, Cyrix,
and VIA that are compatible with and equivalent to the
following Intel processors, may also be used with Fedora Core.
</para>
<itemizedlist>
<listitem>
<para>
Minimum: Pentium-class — Fedora Core is optimized for
Pentium 4 CPUs, but also supports earlier CPUs such as
Pentium, Pentium Pro, Pentium II, Pentium III, and
compatible AMD and VIA processors. Fedora takes this
approach because Pentium-class optimizations actually
result in reduced performance for non-Pentium class
processors. In addition, scheduling for Pentium 4
processors, which make up the bulk of today's processors,
is sufficiently different to warrant this change.
</para>
</listitem>
<listitem>
<para>
Recommended for text-mode: 200 MHz Pentium-class or better
</para>
</listitem>
<listitem>
<para>
Recommended for graphical: 400 MHz Pentium II or better
</para>
</listitem>
<listitem>
<para>
AMD64 processors (both Athlon64 and Opteron)
</para>
</listitem>
<listitem>
<para>
Intel processors with Intel® Extended Memory 64
Technology (Intel® EM64T)
</para>
</listitem>
<listitem>
<para>
Minimum RAM for text-mode: 128MiB
</para>
</listitem>
<listitem>
<para>
Minimum RAM for graphical: 192MiB
</para>
</listitem>
<listitem>
<para>
Recommended for graphical: 256MiB
</para>
</listitem>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the disk
space taken up by Fedora Core after the installation is
complete. However, additional disk space is required during
the installation to support the installation environment.
This additional disk space corresponds to the size of
<code>/Fedora/base/stage2.img</code>
on Installation Disc 1 plus the size of the files in
<code>/var/lib/rpm</code>
on the installed system.
</para>
<para>
In practical terms, additional space requirements may range
from as little as 90 MiB for a minimal installation to as
much as an additional 175 MiB for an "everything"
installation. The complete packages can occupy over 9 GB of
disk space.
</para>
<para>
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
</para>
</section>
</section>
</section>
</section>
</article>
--- NEW FILE ArchSpecificx86_64.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ArchSpecificx86_64">
<title>x86_64 Specifics for Fedora</title>
<para>
This section covers any specific information you may need to know
about Fedora Core and the x86_64 hardware platform.
</para>
<note>
<title>x86_64 Does Not Use a Separate SMP Kernel</title>
<para>
The default kernel in x86_64 architecture provides SMP
(Symmetric Multi-Processor) capabilities to handle multiple CPUs
efficiently. This architecture does not have a separate SMP
kernel unlike x86 and PPC systems.
</para>
</note>
<section>
<title>x86_64 Hardware Requirements</title>
<para>
In order to use specific features of Fedora Core 5 during or
after installation, you may need to know details of other
hardware components such as video and network cards.
</para>
<section>
<title>Memory Requirements</title>
<para>
This list is for 64-bit x86_64 systems:
</para>
<itemizedlist>
<listitem>
<para>
Minimum RAM for text-mode: 128MiB
</para>
</listitem>
<listitem>
<para>
Minimum RAM for graphical: 256MiB
</para>
</listitem>
<listitem>
<para>
Recommended RAM for graphical: 512MiB
</para>
</listitem>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
<para>
The disk space requirements listed below represent the disk space
taken up by Fedora Core 5 after the installation is complete.
However, additional disk space is required during the installation
to support the installation environment. This additional disk space
corresponds to the size of <code>/Fedora/base/stage2.img</code> on
Installation Disc 1 plus the size of the files in
<code>/var/lib/rpm</code> on the installed system.
</para>
<para>
In practical terms, additional space requirements may range
from as little as 90 MiB for a minimal installation to as
much as an additional 175 MiB for an "everything"
installation. The complete packages can occupy over 9 GB of
disk space.
</para>
<para>
Additional space is also required for any user data, and at
least 5% free space should be maintained for proper system
operation.
</para>
</section>
</section>
<section>
<title>RPM Multiarch Support on x86_64</title>
<para>
<emphasis role='strong'>RPM</emphasis> supports parallel installation
of multiple architectures of the same package. A default package
listing such as <code>rpm -qa</code> might appear to include duplicate
packages, since the architecture is not displayed. Instead, use the
<code>repoquery</code> command, part of the <code>yum-utils</code>
package in Fedora Extras, which displays architecture by default. To
install <code>yum-utils</code>, run the following command:
</para>
<screen>
su -c 'yum install yum-utils'
</screen>
<para>
To list all packages with their architecture using
<code>rpm</code>, run the following command:
</para>
<screen>
rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"
</screen>
<para>
You can add this to <code>/etc/rpm/macros</code> (for a system wide
setting) or <code>~/.rpmmacros</code> (for a per-user setting). It
changes the default query to list the architecture:
</para>
<screen>
%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}
</screen>
</section>
</section>
</section>
</article>
--- NEW FILE BackwardsCompatibility.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-BackwardsCompatibility">
<title>Docs/Beats/BackwardsCompatibility</title>
<section>
<title>Backwards Compatibility</title>
<para>
Fedora Core provides legacy system libraries for compatibility
with older software. This software is part of the
<emphasis
role='strong'>Legacy Software
Development</emphasis> group, which is not installed by default.
Users who require this functionality may select this group
either during installation, or after the installation process is
complete. To install the package group on a Fedora system, use
<emphasis>Applications=>Add/Remove Software</emphasis>,
<emphasis
role='strong'>Pirut</emphasis> or enter the
following command in a terminal window:
</para>
<screen>
su -c 'yum groupinstall "Legacy Software Development"'
</screen>
<para>
Enter the password for the
<code>root</code>
account when prompted.
</para>
</section>
</section>
</article>
--- NEW FILE Colophon.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Colophon">
<title>Colophon</title>
<para>
As we use the term, a <emphasis>colophon</emphasis>:
</para>
<itemizedlist>
<listitem>
<para>
recognizes contributors and provides accountability, and
</para>
</listitem>
<listitem>
<para>
explains tools and production methods.
</para>
</listitem>
</itemizedlist>
<section>
<title>Contributors</title>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/AndrewMartynov'>Andrew
Martynov</ulink> (translator, Russian)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/AnthonyGreen'>Anthony
Green</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/BobJensen'>Bob
Jensen</ulink> (beat writer, editor, co-publisher)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DaveMalcolm'>Dave
Malcolm</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/DavidWoodhouse'>David
Woodhouse</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/FrancescoTombolini'>Francesco
Tombolini</ulink> (translator, Italian)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/GavinHenry'>Gavin
Henry</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/HugoCisneiros'>Hugo
Cisneiros</ulink> (translator, Brazilian Portuguese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JensPetersen'>Jens
Petersen</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JoeOrton'>Joe
Orton</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/JoshBressers'>Josh
Bressers</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/KarstenWade'>Karsten
Wade</ulink> (beat writer, editor, co-publisher)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/LuyaTshimbalanga'>Luya
Tshimbalanga</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PatrickBarnes'>Patrick
Barnes</ulink>(beat writer, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/PaulWFrields'>Paul
W. Frields</ulink> (tools, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/RahulSundaram'>Rahul
Sundaram</ulink> (beat writer, editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SekineTatsuo'>Sekine
Tatsuo</ulink> (translator, Japanese)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SteveDickson'>Steve
Dickson</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/StuartEllis'>Stuart
Ellis</ulink> (editor)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/ThomasGraf'>Thomas
Graf</ulink> (beat writer)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/TommyReynolds'>Tommy
Reynolds</ulink> (tools)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/YoshinariTakaoka'>Yoshinari
Takaoka</ulink> (translator, tools)
</para>
</listitem>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/YuanYijun'>Yuan
Yijun</ulink> (translator, Simplified Chinese)
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Production Methods</title>
<para>
Beat writers produce the release notes directly on the Fedora
Project Wiki. They collaborate with other subject matter experts
during the test release phase of Fedora Core to explain
important changes and enhancements. The editorial team ensures
consistency and quality of the finished beats, and ports the
Wiki material to DocBook XML in a revision control repository.
At this point, the team of translators produces other language
versions of the release notes, and then they become available to
the general public as part of Fedora Core. The publication team
also makes them, and subsequent errata, available via the Web.
</para>
</section>
</section>
</article>
--- NEW FILE DatabaseServers.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-DatabaseServers">
<title>Docs/Beats/DatabaseServers</title>
<section>
<title>MySQL</title>
<para>
Fedora now provides <emphasis role='strong'>MySQL</emphasis>
5.0. For a list of the enhancements provided by this version,
refer to
<ulink url='http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html'>http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html</ulink>.
</para>
<para>
For more information on upgrading databases from previous
releases of <emphasis role='strong'>MySQL</emphasis>, refer to
the <emphasis role='strong'>MySQL</emphasis> web site at
<ulink url='http://dev.mysql.com/doc/refman/5.0/en/upgrade.html'>http://dev.mysql.com/doc/refman/5.0/en/upgrade.html</ulink>.
</para>
</section>
<section>
<title>PostgreSQL</title>
<para>
This release of Fedora includes
<emphasis role='strong'>PostgreSQL</emphasis> 8.1. For more
information on this new version, refer to
<ulink url='http://www.postgresql.org/docs/whatsnew'>http://www.postgresql.org/docs/whatsnew</ulink>.
</para>
<important>
<title>Upgrading Databases</title>
<para>
Fedora Core 4 provided version 8.0 of PostgreSQL. If you upgrade an
existing Fedora system with a PostgreSQL database, you must upgrade
the database to access the data.
</para>
<para>
To upgrade a database from a previous version of PostgreSQL, follow
the procedure described at <ulink
url='http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html'>http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html</ulink>.
</para>
</important>
</section>
</section>
</article>
--- NEW FILE Desktop.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Desktop">
<title>Fedora Desktop</title>
<para>
GNOME 2.14 (or a release candidate) and KDE 3.5.1 are included in
Fedora Core 5. The following list includes notable changes to the
desktop interface in this release.
</para>
<itemizedlist>
<listitem>
<para>
<emphasis>gnome-power-manager</emphasis>
</para>
<itemizedlist>
<listitem>
<para>
The <emphasis role='strong'>GNOME Power Manager</emphasis>
is a session daemon for the GNOME desktop environment that
makes it easy to manage your laptop or desktop system. It
takes advantage of HAL (which provides a hardware
abstraction layer) and DBUS (Inter Process Communication
software) written and maintained by Fedora Core
developers.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
<emphasis>gnome-screensaver</emphasis>
</para>
<itemizedlist>
<listitem>
<para>
The <emphasis role='strong'>GNOME Screensaver</emphasis>
provides an integrated user interface to screensavers and
the lock screen dialog.
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
Memory optimizations in the fontconfig and shared-mime-info
packages. These now use shared memory-mapped caches for this
data.
</para>
</listitem>
<listitem>
<para>
Starting with GNOME 2.12, the terminal option has been removed
from the desktop context menu. The
<code>nautilus-open-terminal</code>
package in Fedora Extras provides a enhanced replacement for
those who require it. You can install it with the following
command.
</para>
<screen>
su -c 'yum install nautilus-open-terminal'
</screen>
</listitem>
<listitem>
<para>
In Fedora Core 5, only a small assortment of screensavers is
installed by default. Some users find certain screensavers
unpleasant, and other screensavers may abruptly terminate the
graphical interface. This tends to happen more often with
OpenGL animated screensavers provided within the
<code>xscreensaver-gl-extras</code>
package, when used with poorly-supported video hardware. To
install these extra screensavers, run the following command:
</para>
<screen>
su -c 'yum install xscreensaver-extras xscreensaver-gl-extras'
</screen>
</listitem>
</itemizedlist>
</section>
</article>
--- NEW FILE DevelTools.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-DevelTools">
<title>Developer Tools</title>
<para>
This section covers various developer tools.
</para>
<section>
<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>
<title>Eclipse Development Environment</title>
<itemizedlist>
<listitem>
<para>
Eclipse 3.1M6 is compiled as a native application.
</para>
</listitem>
<listitem>
<para>
The C Development Tool (CDT) has been included.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE DevelToolsGCC.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-DevelToolsGCC">
<title>GCC Compiler Collection</title>
<para>
This release of Fedora has been built with GCC 4.1 as the system
compiler, which is included with the distribution.
</para>
<section>
<title>Caveats</title>
<itemizedlist>
<listitem>
<para>
You need GDB 6.1 or newer to debug binaries, unless they are
compiled using the
<code>-fno-var-tracking</code>
compilation option.
</para>
</listitem>
<listitem>
<para>
The
<code>-fwritable-strings</code>
option is no longer accepted.
</para>
</listitem>
<listitem>
<para>
English-language diagnostic messages now use Unicode quotes.
If you cannot read this, set your
<code>LC_CTYPE</code>
environment variable to
<code>C</code>
or change your terminal emulator.
</para>
</listitem>
<listitem>
<para>
The
<code>specs</code>
file is no longer installed on most systems. Ordinary users
will not notice, but developers who need to alter the file
can use the
<code>-dumpspecs</code>
option to generate the file for editing.
</para>
</listitem>
</itemizedlist>
<section>
<title>Code Generation</title>
<itemizedlist>
<listitem>
<para>
The SSA 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>
</section>
<section>
<title>Language Extensions</title>
<itemizedlist>
<listitem>
<para>
The new sentinel attribute causes the compiler to issue a
warning if a function such as
<code>execl(char *path, const char *arg, ...)</code>
, which requires a NULL list terminator, is missing the
NULL.
</para>
</listitem>
<listitem>
<para>
The
<code>cast-as-lvalue</code>
,
<code>conditional-expression-as-lvalue</code>
, and
<code>compund-expression-as-lvalue</code>
extensions have been removed.
</para>
</listitem>
<listitem>
<para>
The
<code>#pragma pack()</code>
semantics are now closer to those used by other compilers.
</para>
</listitem>
<listitem>
<para>
Taking the address of a variable declared with the
register modifier now generates an error instead of a
warning.
</para>
</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 (
<code>-O0</code>
), has been measured as much as 25% faster in real-world
code.
</para>
</listitem>
<listitem>
<para>
Libraries may now contain function-scope static variables
in multi-threaded programs. Embedded developers can use
the
<code>-fno-threadsafe-statics</code>
to turn off this feature, but ordinary users should never
do this.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE Entertainment.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Entertainment">
<title>Games and Entertainment</title>
<para>
Fedora Core and Fedora Extras provide a selection of games that
cover a variety of genres. By default, Fedora Core includes a
small package of games for GNOME (called
<code>gnome-games</code>
). To install other games available from Fedora Core and Fedora
Extras, select
<emphasis>Applications</emphasis>><emphasis>Add/Remove
Software</emphasis> from the main desktop menu.
</para>
</section>
</article>
--- NEW FILE Extras.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Extras">
<title>Fedora Extras</title>
<section>
<title>Using the Repository</title>
<para>
Fedora Extras provides a repository of packages that complement Fedora
Core. This volunteer-based community effort is part of the larger Fedora
Project.
</para>
<note>
<title>Fedora Extras are Available by Default</title>
<para>
Fedora systems automatically use both the Fedora Core and Fedora
Extras repositories to install and update software.
</para>
</note>
<para>
To install software from either the Core or Extras repositories, choose
<emphasis>Applications > Add/Remove Software</emphasis>. Enter the
<code>root</code> password when prompted. Select the software you
require from the list, and choose <emphasis>Apply</emphasis>.
</para>
<para>
Alternatively, you may install software with the <code>yum</code>
command-line utility. For example, this command automatically installs
the <code>abiword</code> package, and all of the dependencies that are
required:
</para>
<screen>su -c 'yum install abiword'</screen>
<para>
Enter the <code>root</code> password when prompted.
</para>
</section>
<section>
<title>About Fedora Extras</title>
<para>
As of the release of Fedora Core 5, there are approximately
2,000 packages in Fedora Extras, built from 1,350 source
packages. The following list includes some popular and
well-known applications that are maintained by community members
in Fedora Extras:
</para>
<itemizedlist>
<listitem>
<para>
<code>abiword</code>
- elegant word-processing application
</para>
</listitem>
<listitem>
<para>
<code>balsa</code>
- lightweight e-mail reader
</para>
</listitem>
<listitem>
<para>
<code>bash-completion</code>
- advanced command-line completion for power users
</para>
</listitem>
<listitem>
<para>
<code>bluefish</code>
- HTML editor
</para>
</listitem>
<listitem>
<para>
<code>clamav</code>
- open source anti-virus scanner for servers and desktops
</para>
</listitem>
<listitem>
<para>
<code>fuse</code>
- tool for attaching non-standard devices and network
services as directories
</para>
</listitem>
<listitem>
<para>
<code>fwbuilder</code>
- graphical utility for building Linux and Cisco firewall
rulesets
</para>
</listitem>
<listitem>
<para>
<code>gaim-guifications</code>
- enhancements to the Gaim Instant Messenger
</para>
</listitem>
<listitem>
<para>
<code>gdesklets</code>
- widgets for the GNOME desktop
</para>
</listitem>
<listitem>
<para>
<code>gnumeric</code>
- powerful spreadsheet application
</para>
</listitem>
<listitem>
<para>
<code>inkscape</code>
- illustration and vector drawing application
</para>
</listitem>
<listitem>
<para>
<code>koffice</code>
- complete office suite for the KDE desktop
</para>
</listitem>
<listitem>
<para>
<code>mail-notification</code>
- alerts you as new mail arrives
</para>
</listitem>
<listitem>
<para>
<code>mediawiki</code>
- the Wikipedia solution for collaborative websites
</para>
</listitem>
<listitem>
<para>
<code>nautilus-open-terminal</code>
- extension to the GNOME file manager
</para>
</listitem>
<listitem>
<para>
<code>pan</code>
- the Usenet news reader
</para>
</listitem>
<listitem>
<para>
<code>revelation</code>
- password management utility
</para>
</listitem>
<listitem>
<para>
<code>scribus</code>
- desktop publishing (DTP) application
</para>
</listitem>
<listitem>
<para>
<code>xfce</code>
- lightweight desktop environment
</para>
</listitem>
<listitem>
<para>
<code>xmms</code>
- the popular audio player
</para>
</listitem>
<listitem>
<para>
lots of Perl and Python tools and libraries
</para>
</listitem>
<listitem>
<para>
...and much more!
</para>
</listitem>
</itemizedlist>
<para>
Is your favorite open source application missing from Fedora
Extras? Package the application as an RPM, and submit it for
review to Fedora Extras. After a successful review, import it to
Extras and you can maintain it there. If you don't know how to
create RPM packages, there are many other ways to get involved
in Fedora Extras and help drive it forward.
</para>
<para>
To learn more about how to use Fedora Extras or how to get
involved, refer to
<ulink url='http://fedoraproject.org/wiki/Extras'>http://fedoraproject.org/wiki/Extras</ulink>.
</para>
</section>
</section>
</article>
--- NEW FILE Feedback.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Feedback">
<title>Providing Feedback for Release Notes</title>
<note>
<title>Feedback for Release Notes Only</title>
<para>
This section concerns feedback on the release notes themselves. To
provide feedback on Fedora software or other system elements, please
refer to <ulink
url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>.
A list of commonly reported bugs and known issues for this release is
available from <ulink
url='http://fedoraproject.org/wiki/Bugs/FC5Common'>http://fedoraproject.org/wiki/Bugs/FC5Common</ulink>.
</para>
</note>
<para>
Thanks for your interest in giving feedback for these release
notes. If you feel these release notes could be improved in any
way, you can provide your feedback directly to the beat writers.
Here are several ways to do so, in order of preference:
</para>
<itemizedlist>
<listitem>
<para>
Edit content directly at
<ulink url='http://fedoraproject.org/wiki/Docs/Beats'>http://fedoraproject.org/wiki/Docs/Beats</ulink>
</para>
</listitem>
<listitem>
<para>
Fill out a bug request using this template:
<ulink url='http://tinyurl.com/8lryk'>http://tinyurl.com/8lryk</ulink>
- <emphasis role='strong'>This link is ONLY for feedback on
the release notes themselves.</emphasis> (Refer to the
admonition above for details.)
</para>
</listitem>
<listitem>
<para>
Email
<ulink url='mailto:relnotes at fedoraproject.org'>relnotes at fedoraproject.org</ulink>
</para>
</listitem>
</itemizedlist>
<para>
A release note beat is an area of the release notes that is the
responsibility of one or more content contributors to oversee. For
more ifnormation about beats, refer to
<ulink url='http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats'>http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats</ulink>.
</para>
<para>
Thank you (in advance) for your feedback!
</para>
</section>
</article>
--- NEW FILE FileServers.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-FileServers">
<title>File Servers</title>
<para>
This section refers to file transfer and sharing servers. Refer to
<ulink url='http://fedoraproject.org/wiki/Docs/Beats/WebServers'>http://fedoraproject.org/wiki/Docs/Beats/WebServers</ulink>
and
<ulink url='http://fedoraproject.org/wiki/Docs/Beats/Samba'>http://fedoraproject.org/wiki/Docs/Beats/Samba</ulink>
for information on HTTP (Web) file transfer and Samba (Windows)
file sharing services.
</para>
<section>
<title>Netatalk (Macintosh Compatibility)</title>
<para>
Fedora includes version 2 of Netatalk, a suite of software that
enables Linux to interact with Macintosh systems using the
AppleTalk network protocols.
</para>
<caution>
<title>Use Caution When Upgrading</title>
<para>
You may experience data loss when upgrading from Netatalk version 1 to
version 2.
</para>
<para>
Version 2 of Netatalk stores file resource forks using a different
method from the previous version, and may require a different file
name encoding scheme. Please read the documentation and plan your
migration before upgrading. Refer to the upgrade information available
directly from the Netatalk site at <ulink
url='http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>.
</para>
</caution>
<para>
The documentation is also included in the
<code>netatalk</code>
package. Refer to either
<code>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html</code>
or
<code>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf</code>
(numbered page 25, document page 33).
</para>
</section>
</section>
</article>
--- NEW FILE FileSystems.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-FileSystems">
<title>File Systems</title>
<para>
There were no significant or noteworthy changes for the file system for
this release. If you believe otherwise, please file a bug against the
release-notes, as detailed in <xref linkend="sn-Feedback"/>.
</para>
</section>
</article>
--- NEW FILE I18n.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-I18n">
<title>Internationalization (i18n)</title>
<para>
This section includes information related to the support of
various languages under Fedora Core.
</para>
<section>
<title>Input Methods</title>
<para>
SCIM (Simple Common Input Method) has replaced IIIMF as the
input method system for Asian and other languages in Fedora Core
in this release. SCIM uses
<code>Ctrl-Space</code>
as the default trigger key to toggle on and off the input
method, though it is easy to change the hotkey or add hotkeys
with the SCIM setup configuration tool. Japanese users can now
use the
<code>Zenkaku_Hankaku</code>
key to toggle between native and ASCII input.
</para>
<section>
<title>Installation</title>
<para>
SCIM should be installed and run by default for Asian language
desktops. Otherwise the required packages can be installed
using the language support section of the package manager (
<code>pirut</code>
) or running:
</para>
<screen>
su -c 'yum groupinstall <language>-support'
</screen>
<para>
where <code><language></code> is one of <code>assamese</code> ,
<code>bengali</code>, <code>chinese</code>, <code>gujarati</code> ,
<code>hindi</code>, <code>japanese</code>, <code>kannada</code> ,
<code>korean</code>, <code>punjabi</code>, <code>tamil</code>, or
<code>thai</code>.
</para>
<para>
The list of IMEs included is:
</para>
<itemizedlist>
<listitem>
<para>
Japanese:
<code>scim-anthy</code>
</para>
<para>
Korean:
<code>scim-hangul</code>
</para>
<para>
Simplified Chinese:
<code>scim-pinyin scim-tables-chinese</code>
</para>
<para>
Traditional Chinese:
<code>scim-chewing scim-tables-chinese</code>
</para>
<para>
Indian and other languages:
<code>scim-m17n m17n-db-<language></code>
</para>
</listitem>
</itemizedlist>
<para>
If your desktop is not running in an Asian locale, to activate
it in your user account, run these commands, then logout and
login again to your desktop.
</para>
<screen>
mkdir ~/.xinput.d
ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default
</screen>
</section>
<section>
<title>SCIM applet and toolbar</title>
<para>
When SCIM is running, an applet icon appears in the
notification area of the desktop panel. The icon is a grey
keyboard icon when SCIM is inactive, and an Input Method
Engine (IME) icon when it is active. When SCIM is active, by
default the SCIM input method toolbar with status information
also appears.
</para>
<para>
Clicking the left mouse button on the applet activates a SCIM
language switching menu for changing the current Input Method
Engine. The menu only appears when an application using the
Input Method has focus. Clicking the right mouse button on the
applet or SCIM toolbar activates the setup menu.
</para>
</section>
<section>
<title>SCIM configuration</title>
<para>
You can configure SCIM and IMEs using the setup configuration
tool available from the setup menu. In the IME general
configuration panel, you can select which languages or IMEs
appear on the language switching menu.
</para>
</section>
<section>
<title>New conversion engines</title>
<para>
<code>anthy</code>
, a new Japanese conversion engine replaces the old Canna
server system, and
<code>libchewing</code>
, a new Traditional Chinese conversion engine, has been added.
</para>
</section>
</section>
<section>
<title>Fonts</title>
<para>
Support is now available for synthetic emboldening of fonts that
do not have a bold face.
</para>
<para>
New fonts for Chinese have been added: AR PL ShanHeiSun Uni
(<code>uming.ttf</code>) and AR PL ZenKai Uni (<code>ukai.ttf</code>).
The default font is AR PL ShanHeiSun Uni, which contains embedded
bitmaps. If you prefer outline glyphs you can put the following section
in your <code>~/.font.conf</code> file:
</para>
<screen>
<fontconfig>
<match target="font">
<test name="family" compare="eq">
<string>AR PL ShanHeiSun Uni</string>
</test>\n<edit name="embeddedbitmap" mode="assign">
<bool>false</bool>
</edit>\n</match>
</fontconfig>
</screen>
</section>
<section>
<title>gtk2 IM submenu</title>
<para>
The Gtk2 context menu IM submenu no longer appears by default.
You can enable it on the command line with the following
command; the <computeroutput>\</computeroutput> is for printing purposes
and this should appear all on one line:
</para>
<screen>
gconftool-2 --type bool --set \
'/desktop/gnome/interface/show_input_method_menu' true
</screen>
</section>
<section>
<title>Pango Support in Firefox</title>
<para>
Firefox in Fedora Core is built with Pango, which provides
better support for certain scripts, such as Indic and some CJK
scripts. Fedora has the permission of the Mozilla Corporation to
use the Pango system for text renderering.
</para>
<para>
To disable the use of Pango, set
<code>MOZ_DISABLE_PANGO=1</code>
in your environment before launching Firefox.
</para>
</section>
</section>
</article>
--- NEW FILE Installer.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Installer">
<title>Installation-Related Notes</title>
<para>
This section outlines those issues that are related to
<emphasis role='strong'>Anaconda</emphasis> (the Fedora Core
installation program) and installing Fedora Core in general.
</para>
<tip>
<title>Downloading Large Files</title>
<para>
If you intend to download the Fedora Core DVD ISO image, keep in mind
that not all file downloading tools can accommodate files larger than
2GB in size. <code>wget</code> 1.9.1-16 and above, <code>curl</code> and
<code>ncftpget</code> do not have this limitation, and can successfully
download files larger than 2GB. <emphasis
role='strong'>BitTorrent</emphasis> is another method for downloading
large files. For information about obtaining and using the torrent file,
refer to <ulink
url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
</para>
</tip>
</section>
<section>
<title>Anaconda Notes</title>
<itemizedlist>
<listitem>
<para>
<emphasis role='strong'>Anaconda</emphasis> tests the
integrity of installation media by default. This function
works with the CD, DVD, hard drive ISO, and NFS ISO
installation methods. The Fedora Project recommends that you
test all installation media before starting the installation
process, and before reporting any installation-related bugs.
Many of the bugs reported are actually due to
improperly-burned CDs. To use this test, type
<code>linux mediacheck</code>
at the
<code>boot:</code>
prompt.
</para>
<para>
The
<code>mediacheck</code>
function is highly sensitive, and may report some usable discs
as faulty. This result is often caused by disc writing
software that does not include padding when creating discs
from ISO files. For best results with
<code>mediacheck</code>
, boot with the following option:
</para>
<screen>
linux ide=nodma
</screen>
<para>
Use the
<code>sha1sum</code>
utility to verify discs before carrying out an installation.
This test accurately identifies discs that are not valid or
identical to the ISO image files.
</para>
<note>
<title>BitTorrent Automatically Verifies File Integrity</title>
<para>
If you use <emphasis role='strong'>BitTorrent</emphasis>, any files
you download are automatically validated. If your file completes
downloading, you do not need to check it. Once you burn your CD,
however, you should still use <code>mediacheck</code> .
</para>
</note>
</listitem>
<listitem>
<para>
You may perform memory testing before you install Fedora Core
by entering
<code>memtest86</code>
at the
<code>boot:</code>
prompt. This option runs the
<emphasis role='strong'>Memtest86</emphasis> standalone memory
testing software in place of
<emphasis role='strong'>Anaconda</emphasis>.
<emphasis role='strong'>Memtest86</emphasis> memory testing
continues until the
<code>Esc</code>
key is pressed.
</para>
<tip>
<title><code>Memtest86</code> Availability</title>
<para>
You must boot from Installation Disc 1 or a rescue CD in order to
use this feature.
</para>
</tip>
</listitem>
<listitem>
<para>
Fedora Core supports graphical FTP and HTTP installations. However,
the installer image must either fit in RAM or appear on local storage
such as Installation Disc 1. Therefore, only systems with more than
192MiB of RAM, or which boot from Installation Disc 1, can use the
graphical installer. Systems with 192MiB RAM or less will fall back to
using the text-based installer automatically. If you prefer to use the
text-based installer, type <code>linux text</code> at the
<code>boot:</code> prompt.
</para>
</listitem>
</itemizedlist>
<section>
<title>Changes in Anaconda</title>
<itemizedlist>
<listitem>
<para>
The installer checks hardware capability and installs either
the uniprocessor or SMP (Symmetric Multi Processor) kernel
as appropriate in this release. Previous releases installed
both variants and used the appropriate one as default.
</para>
</listitem>
<listitem>
<para>
<emphasis role='strong'>Anaconda</emphasis> now supports
installation on several IDE software RAID chipsets using
<code>dmraid</code>
. To disable this feature, add the
<code>nodmraid</code>
option at the
<code>boot:</code>
prompt. For more information, refer to
<ulink url='http://fedoraproject.org/wiki/DmraidStatus'>http://fedoraproject.org/wiki/DmraidStatus</ulink>
.
</para>
<warning>
<title>Do not boot only half of a <code>dmraid</code> RAID1
(mirror)</title>
<para>
Various situations may occur that cause <code>dmraid</code> to
break the mirror, and if you boot in read/write mode into only one
of the mirrored disks, it causes the disks to fall out of sync. No
symptoms arise, since the primary disk is reading and writing to
itself. But if you attempt to re-establish the mirror without
first synchronizing the disks, you could corrupt the data and have
to reinstall from scratch without a chance for recovery.
</para>
<para>
If the mirror is broken, you should be able to resync from within
the RAID chipset BIOS or by using the <code>dd</code> command.
Reinstallation is always an option.
</para>
</warning>
</listitem>
<listitem>
<para>
Serial mice are no longer formally supported in
<emphasis role='strong'>Anaconda</emphasis> or Fedora Core.
</para>
</listitem>
<listitem>
<para>
The disk partitioning screen has been reworked to be more
user friendly.
</para>
</listitem>
<listitem>
<para>
The package selection screen has been revamped. The new,
simplified screen only displays the optional groups
<emphasis>Office and Productivity</emphasis> (enabled by
default), <emphasis>Software Development</emphasis>,
<emphasis>Web Server</emphasis>, and
<emphasis>Virtualization (Xen)</emphasis>. The
<emphasis>Minimal</emphasis> and
<emphasis>Everything</emphasis> shortcut groups have been
removed from this screen. However, you may still fully
customize your package selection. The right-click context
menu provides an easy way to select all of the optional
packages within a group. Refer to
<ulink url='http://fedoraproject.org/wiki/Anaconda/PackageSelection'>http://fedoraproject.org/wiki/Anaconda/PackageSelection</ulink>
for more details.
</para>
</listitem>
<listitem>
<para>
Optional package selection has also been enhanced. In the
custom package selection dialog, you can right-click any
package group, and select or deselect all optional packages
at one time.
</para>
</listitem>
<listitem>
<para>
Firewall and SELinux configuration has been moved to the
<emphasis>Setup Agent</emphasis> (
<code>firstboot</code>
), the final phase of the graphical installation process.
</para>
</listitem>
<listitem>
<para>
The timezone configuration screen now features zooming areas
on the location selection map.
</para>
</listitem>
<listitem>
<para>
This release supports remote logging via
<code>syslog</code>
. To use this feature, add the option
<code>syslog=host:port</code>
at the boot prompt. The
<code>:port</code>
specifier is optional.
</para>
</listitem>
<listitem>
<para>
<emphasis role='strong'>Anaconda</emphasis> now renders
release notes with the
<code>gtkhtml</code>
widget for better capability.
</para>
</listitem>
<listitem>
<para>
Kickstart has been refactored into its own package,
<code>pykickstart</code>
, and contains a parser and writers. As a result of this
change, validation and extension is now much easier.
</para>
</listitem>
<listitem>
<para>
<emphasis role='strong'>Anaconda</emphasis> now uses
<code>yum</code>
as the backend for solving package dependencies. Additional
repositories such as Fedora Extras are expected to be
supported during installation in a future release.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Installation Related Issues</title>
<itemizedlist>
<listitem>
<para>
Some Sony VAIO notebook systems may experience problems
installing Fedora Core from CD-ROM. If this happens, restart
the installation process and add the following option to the
boot command line:
</para>
<itemizedlist>
<listitem>
<screen>
pci=off ide1=0x180,0x386
</screen>
</listitem>
</itemizedlist>
<para>
Installation should proceed normally, and any devices not
detected are configured the first time Fedora Core is
booted.
</para>
</listitem>
<listitem>
<para>
Not all IDE RAID controllers are supported. If your RAID
controller is not yet supported by
<code>dmraid</code>
, you may combine drives into RAID arrays by configuring
Linux software RAID. For supported controllers, configure
the RAID functions in the computer BIOS.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Upgrade Related Issues</title>
<para>
Refer to
<ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink>
for detailed recommended procedures for upgrading Fedora.
</para>
<para>
In general, fresh installations are recommended over upgrades,
particularly for systems which include software from third-party
repositories. Third-party packages remaining from a previous
installation may not work as expected on an upgraded Fedora
system. If you decide to perform an upgrade anyway, the
following information may be helpful.
</para>
<itemizedlist>
<listitem>
<para>
Before you upgrade, back up the system completely. In particular,
preserve <code>/etc</code> , <code>/home</code> , and possibly
<code>/opt</code> and <code>/usr/local</code> if customized packages
are installed there. You may wish to use a multi-boot approach with
a "clone" of the old installation on alternate partition(s) as a
fallback. In that case, creating alternate boot media such as GRUB
boot floppy.
</para>
<note>
<title>System Configuration Backups</title>
<para>
Backups of configurations in <code>/etc</code> are also useful in
reconstructing system settings after a fresh installation.
</para>
</note>
</listitem>
<listitem>
<para>
After you complete the upgrade, run the following command:
</para>
<itemizedlist>
<listitem>
<screen>
rpm -qa --last > RPMS_by_Install_Time.txt
</screen>
</listitem>
</itemizedlist>
<para>
Inspect the end of the output for packages that pre-date the
upgrade. Remove or upgrade those packages from third-party
repositories, or otherwise deal with them as necessary.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE Java.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Java">
<title>Java and java-gcj-compat</title>
<para>
A free and open source Java environment is available within this Fedora
Core release, called <code>java-gcj-compat</code>.
<code>java-gcj-compat</code>includes a tool suite and execution
environment that is capable of building and running many useful programs
that are written in the Java programming language.
</para>
<note>
<title>Fedora Core Does Not Include Java</title>
<para>
Java is a trademark of Sun Microsystems. <code>java-gcj-compat</code> is
an entirely free software stack that is <emphasis
role='strong'>not</emphasis> Java, but may run Java software.
</para>
</note>
<para>
The infrastructure has three key components: a <emphasis role='strong'>GNU
Java</emphasis> runtime (<code>libgcj</code>), the <emphasis
role='strong'>Eclipse Java</emphasis> compiler (<code>ecj</code>), and
a set of wrappers and links (<code>java-gcj-compat</code>) that present
the runtime and compiler to the user in a manner similar to other Java
environments.
</para>
<para>
The Java software packages included in this Fedora release use the new,
integrated environment <code>java-gcj-compat</code>. These packages
include <emphasis role='strong'>OpenOffice.org Base</emphasis>, <emphasis
role='strong'>Eclipse</emphasis>, and <emphasis role='strong'>Apache
Tomcat</emphasis>.
</para>
<para>
Refer to the Java FAQ at <ulink
url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
for more information on the <code>java-gcj-compat</code> free Java
environment in Fedora.
</para>
<tip>
<title>Include location and version information in bug reports</title>
<para>
When making a bug report, be sure to include the output from these
commands:
</para>
<screen>
which java && java -version && which javac && javac -version
</screen>
</tip>
<section>
<title>Handling Java and Java-like Packages</title>
<para>
In addition to the <code>java-gcj-compat</code> free software stack,
Fedora Core is designed to let you install multiple Java implementations
and switch between them using the <code>alternatives</code> command line
tool. However, every Java system you install must be packaged using the
JPackage Project packaging guidelines to take advantage of
<code>alternatives</code> .
</para>
<para>
Once installed properly, the <code>root</code> user should be able to
switch between <code>java</code> and <code>javac</code> implementations
using the <code>alternatives</code> command:
</para>
<screen>
alternatives --config java
alternatives --config javac
</screen>
</section>
<section>
<title>Fedora and the JPackage Java Packages</title>
<para>
Fedora Core includes many packages derived from the JPackage
Project, which provides a Java software repository. These
packages have been modified in Fedora to remove proprietary
software dependencies and to make use of GCJ's ahead-of-time
compilation feature. Fedora users should use the Fedora
repositories for updates to these packages, and may use the
JPackage repository for packages not provided by Fedora.
</para>
<para>
Refer to the JPackage website at
<ulink url='http://jpackage.org'>http://jpackage.org</ulink> for
more information on the project and the software that it
provides.
</para>
<warning>
<title>Mixing Packages from Fedora and JPackage</title>
<para>
Research package compatibility before you install software from both
the Fedora and JPackage repositories on the same system. Incompatible
packages may cause complex issues.
</para>
</warning>
</section>
</section>
</article>
--- NEW FILE Kernel.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Kernel">
<title>Linux Kernel</title>
<para>
This section covers changes and important information regarding
the kernel in Fedora Core 5.
</para>
<section>
<title>Version</title>
<para>
This distribution is based on the 2.6 series of the Linux
kernel. Fedora Core may include additional patches for
improvements, bug fixes, or additional features. For this
reason, the Fedora Core kernel may not be line-for-line
equivalent to the so-called <emphasis>vanilla kernel</emphasis>
from the kernel.org web site:
</para>
<para>
<ulink url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
</para>
<para>
To obtain a list of these patches, download the source RPM
package and run the following command against it:
</para>
<screen>
rpm -qpl kernel-<version>.src.rpm
</screen>
</section>
<section>
<title>Changelog</title>
<para>
To retrieve a log of changes to the package, run the following
command:
</para>
<screen>
rpm -q --changelog kernel-<version>
</screen>
<para>
If you need a user friendly version of the changelog, refer to
<ulink url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.kernelnewbies.org/LinuxChanges</ulink>.
A short and full diff of the kernel is available from
<ulink url='http://kernel.org/git'>http://kernel.org/git</ulink>.
The Fedora version kernel is based on the Linus tree.
</para>
<para>
Customizations made for the Fedora version are available from
<ulink url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink>
.
</para>
</section>
<section>
<title>Kernel Flavors</title>
<anchor id='Kernel_Flavors'/>
<para></para>
<para>
Fedora Core includes the following kernel builds:
</para>
<itemizedlist>
<listitem>
<para>
Native kernel, in both uni-processor and SMP (Symmetric
Multi-Processor) varieties. SMP kernels provide support for
multiple CPUs. Configured sources are available in the
<code>kernel-[smp-]devel-<version>.<arch>.rpm</code>
package.
</para>
</listitem>
<listitem>
<para>
Virtual kernel hypervisor for use with the Xen emulator
package. Configured sources are available in the
<code>kernel-xen0-devel-<version>.<arch>.rpm</code>
package.
</para>
</listitem>
<listitem>
<para>
Virtual kernel guest for use with the Xen emulator package.
Configured sources are available in the
<code>kernel-xenU-devel-<version>.<arch>.rpm</code>
package.
</para>
</listitem>
<listitem>
<para>
Kdump kernel for use with kexec/kdump capabilities.
Configured sources are available in the
<code>kernel-kdump-devel-<version>.<arch>.rpm</code>
package.
</para>
</listitem>
</itemizedlist>
<para>
You may install kernel headers for all kernel flavors at the
same time. The files are installed in the
<code>/usr/src/kernels/<version>-[xen0|xenU|kdump]-<arch>/</code>
tree. Use the following command:
</para>
<screen>
su -c 'yum install kernel-{xen0,xenU,kdump}-devel'
</screen>
<para>
Select one or more of these flavors, separated by commas and no
spaces, as appropriate. Enter the root password when prompted.
</para>
<tip>
<title>x86_64 Default Kernel Provides SMP</title>
<para>
There is no separate SMP kernel available for the x86_64 architecture
in Fedora Core 5.
</para>
</tip>
<tip>
<title>PowerPC Kernel Support</title>
<para>
There is no support for Xen or kdump for the PowerPC architecture in
Fedora Core 5.
</para>
</tip>
</section>
<section>
<title>Kexec and Kdump</title>
<para>
Kexec and kdump are new features in the 2.6 mainstream kernel.
Major portions of these features are now in Fedora Core 5.
Currently these features are available on x86, x86_64, and ppc64
platforms.
</para>
<para>
The purpose of these features is to ensure faster boot up and
creation of reliable kernel vmcores for diagnostic purposes.
Instructions on the kexec and kdump pages verify that the
features work on your systems. For more information refer to:
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/Kernel/kexec'>http://fedoraproject.org/wiki/Kernel/kexec</ulink>
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/Kernel/kdump'>http://fedoraproject.org/wiki/Kernel/kdump</ulink>
</para>
</section>
<section>
<title>Reporting Bugs</title>
<para>
Refer to
<ulink url='http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html'>http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html</ulink>
for information on reporting bugs in the Linux kernel. You may
also use
<ulink url='http://bugzilla.redhat.com'>http://bugzilla.redhat.com</ulink>
for reporting bugs which are specific to Fedora.
</para>
</section>
<section>
<title>Following Generic Textbooks</title>
<para>
Many of the tutorials, examples, and textbooks about Linux
kernel development assume the kernel sources are installed under
the
<code>/usr/src/linux/</code>
directory. If you make a symbolic link, as shown below, you
should be able to use those learning materials with the Fedora
Core packages. Install the appropriate kernel sources, as shown
earlier, and then run the following command:
</para>
<screen>
su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux'
</screen>
<para>
Enter the <code>root</code> password when prompted.
</para>
</section>
<section>
<title>Preparing for Kernel Development</title>
<para>
Fedora Core does not include the kernel-source package provided
by older versions since only the kernel-devel package is
required now to build external modules. Configured sources are
available, as described in this kernel flavors section.
</para>
<note>
<title>Instructions Refer to Current Kernel</title>
<para>
To simplify the following directions, we have assumed that you want to
configure the kernel sources to match your currently-running kernel.
In the steps below, the expression <version> refers to the kernel
version shown by the command: <code>uname -r</code> .
</para>
</note>
<para>
Users who require access to Fedora Core original kernel sources
can find them in the kernel .src.rpm package. To create an
exploded source tree from this file, perform the following
steps:
</para>
<caution>
<title>Do Not Build Packages as Super-user (root)</title>
<para>
Building packages as the superuser is inherently dangerous and is not
required, even for the kernel. These instructions allow you to install
the kernel source as a normal user. Many general information sites
refer to <code>/usr/src/linux</code> in their kernel instructions. If
you use these instructions, simply substitute
<code>~/rpmbuild/BUILD/kernel-<version>/linux-<version></code> .
</para>
</caution>
<orderedlist numeration='arabic'>
<listitem>
<para>
Prepare a RPM package building environment in your home
directory. Run the following commands:
</para>
<screen>
su -c 'yum install fedora-rpmdevtools yum-utils'
fedora-buildrpmtree
</screen>
<para>
Enter the
<code>root</code>
password when prompted.
</para>
</listitem>
<listitem>
<para>
Enable the appropriate <code>source</code> repository definition. In
the case of the kernel released with Fedora Core 5, enable
<code>core-source</code> by editing the file
<code>/etc/yum.repos.d/fedora-core.repo</code>, setting the option
<code>enabled=1</code>. In the case of update or testing kernels,
enable the <code>source</code> definitions in
<code>/etc/yum.repos.d/fedora-updates.repo</code> or
<code>/etc/yum.repos.d/fedora-updates-testing.repo</code> as
appropriate.
</para>
</listitem>
<listitem>
<para>
Download the
<code>kernel-<version>.src.rpm</code>
file:
</para>
<screen>
yumdownloader --source kernel
</screen>
<para>
Enter the <code>root</code> password when prompted.
</para>
</listitem>
<listitem>
<para>
Install
<code>kernel-<version>.src.rpm</code>
using the command:
</para>
<screen>
rpm -Uvh kernel-<version>.src.rpm
</screen>
<para>
This command writes the RPM contents into
<code>${HOME}/rpmbuild/SOURCES</code> and
<code>${HOME}/rpmbuild/SPECS</code>, where <code>${HOME}</code>
is your home directory.
</para>
<tip>
<title>Space Required</title>
<para>
The full kernel building process may require several gigabytes of
extra space on the file system containing your home directory.
</para>
</tip>
</listitem>
<listitem>
<para>
Prepare the kernel sources using the commands:
</para>
<screen>
cd ~/rpmbuild/SPECS
rpmbuild -bp --target $(uname -m) kernel-2.6.spec
</screen>
<para>
The kernel source tree is located in the
<code>${HOME}/rpmbuild/BUILD/kernel-<version>/</code> directory.
</para>
</listitem>
<listitem>
<para>
The configurations for the specific kernels shipped in
Fedora Core are in the
<code>configs/</code>
directory. For example, the i686 SMP configuration file is
named
<code>configs/kernel-<version>-i686-smp.config</code>
. Issue the following command to place the desired
configuration file in the proper place for building:
</para>
<screen>
cp configs/<desired-config-file> .config
</screen>
<para>
You can also find the <code>.config</code> file that matches your
current kernel configuration in the
<code>/lib/modules/<version>/build/.config</code> file.
</para>
</listitem>
<listitem>
<para>
Every kernel gets a name based on its version number. This is the
value the <code>uname -r</code> command displays. The kernel name is
defined by the first four lines of the kernel <code>Makefile</code>.
The <code>Makefile</code> has been changed to generate a kernel with
a <emphasis>different</emphasis> name from that of the running
kernel. To be accepted by the running kernel, a module must be
compiled for a kernel with the correct name. To do this, you must
edit the kernel <code>Makefile</code>.
</para>
<para>
For example, if the <code>uname -r</code> returns the string
<code>2.6.15-1.1948_FC5</code> , change the
<code>EXTRAVERSION</code> definition from this:
</para>
<screen>
EXTRAVERSION = -prep
</screen>
<para>
to this:
</para>
<screen>
EXTRAVERSION = -1.1948_FC5
</screen>
<para>
That is, substitute everything from the final dash onward.
</para>
</listitem>
<listitem>
<para>
Run the following command:
</para>
<screen>
make oldconfig
</screen>
<para>
You may then proceed as usual.
</para>
</listitem>
</orderedlist>
</section>
<section>
<title>Building Only Kernel Modules</title>
<para>
An exploded source tree is not required to build a kernel
module, such as your own device driver, against the currently
in-use kernel. Only the
<code>kernel-devel</code>
package is required to build external modules. If you did not
select it during installation, use
<emphasis role='strong'>Pirut</emphasis> to install it, going to
<emphasis role='strong'>Applications > Add/Remove</emphasis>
software or use
<code>yum</code>
to install it. Run the following command to install the
<code>kernel-devel</code>
package using
<code>yum</code>
.
</para>
<screen>
su -c 'yum install kernel-devel'
</screen>
<para>
For example, to build the <code>foo.ko</code> module, create the
following <code>Makefile</code> in the directory containing the
<code>foo.c</code> file:
</para>
<screen>
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) M=$(PWD) modules
</screen>
<para>
Issue the <code>make</code> command to build the <code>foo.ko</code>
module.
</para>
</section>
<section>
<title>User Space Dependencies on the Kernel</title>
<para>
Fedora Core has support for clustered storage through the Global
File System (GFS). GFS requires special kernel modules that work
in conjunction with some user-space utilities, such as
management daemons. To remove such a kernel, perhaps after an
update, use the
<code>su -c 'yum remove kernel-<version>'</code>
command instead. The
<code>yum</code>
command automatically removes dependent packages, if necessary.
</para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>PowerPC does not support
GFS</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para>
The GFS kernel modules are not built for the PowerPC
architecture in Fedora Core 5.
</para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE Legacy.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Legacy">
<title>Fedora Legacy - Community Maintenance Project</title>
<para>
The Fedora Legacy Project is a community-supported open source
project to extend the lifecycle of select "maintenance mode" Red
Hat Linux and Fedora Core distributions. The Fedora Legacy Project
works with the Linux community to provide security and critical
bug fix errata packages. This work extends the effective lifetime
of older distributions in environments where frequent upgrades are
not possible or desirable. For more information about the Fedora
Legacy Project, refer to
<ulink url='http://fedoraproject.org/wiki/Legacy'>http://fedoraproject.org/wiki/Legacy</ulink>.
</para>
<note>
<title>Legacy Repo Included in Fedora Core 5</title>
<para>
Fedora Core 5 ships with a software repository configuration for Fedora
Legacy. This is a huge step in integrating Fedora Legacy with the Fedora
Project at large and Fedora Core specifically. This repository is not
enabled by default in this release.
</para>
</note>
<para>
Currently the Fedora Legacy Project maintains the following
distributions and releases in maintenance mode:
</para>
<itemizedlist>
<listitem>
<para>
Red Hat Linux 7.3 and 9
</para>
</listitem>
<listitem>
<para>
Fedora Core 1, 2, and 3
</para>
</listitem>
</itemizedlist>
<para>
The Fedora Legacy Project provides updates for these releases
as long as there is community interest. When interest is not
sustained further, maintenance mode ends with the second test
release for the third subsequent Core release. For example,
maintenance mode for Fedora Core 4, if not sustained by the
community, ends with the release of Fedora Core 7 test2. This
provides an effective supported lifetime (Fedora Core plus Fedora
Legacy Support) of about 18 months.
</para>
<para>
The Fedora Legacy Project always needs volunteers to perform
quality assurance testing on packages waiting to be published as
updates. Refer to
<ulink url='http://fedoraproject.org/wiki/Legacy/QATesting'>http://fedoraproject.org/wiki/Legacy/QATesting</ulink>
for more information. Also visit our issues list at
<ulink url='http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html'>http://www.redhat.com/archives/fedora-legacy-list/2005-August/msg00079.html</ulink>
for further information and pointers to bugs we have in the queue.
</para>
<para>
If you need help in getting started, visit the project home page
on the Wiki at
<ulink url='http://fedoraproject.org/wiki/Legacy'>http://fedoraproject.org/wiki/Legacy</ulink>,
or the Mentors page at
<ulink url='http://fedoraproject.org/wiki/Mentors'>http://fedoraproject.org/wiki/Mentors</ulink>.
If you are looking for others ways to participate in Fedora, refer
to
<ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>.
</para>
<para>
<ulink url='/CategoryLegacy'>CategoryLegacy</ulink>
</para>
</section>
</article>
--- NEW FILE Multimedia.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Multimedia">
<title>Multimedia</title>
<para>
Fedora Core includes applications for assorted multimedia
functions, including playback, recording and editing. Additional
packages are available through the Fedora Extras repository.
</para>
<section>
<title>Multimedia Players</title>
<para>
The default installation of Fedora Core includes <emphasis
role='strong'>Rhythmbox</emphasis>, <emphasis
role='strong'>Totem</emphasis>, and <emphasis role='strong'>Helix
Player</emphasis> for media playback. Many other programs are
available in the Fedora Core and Fedora Extras repositories, including
the popular <code>XMMS</code> package. Both GNOME and KDE have a
selection of players that can be used with a variety of formats.
Additional programs are available from third parties to handle other
formats.
</para>
<para>
Fedora Core also takes full advantage of the Advanced Linux
Sound Architecture (ALSA) sound system. Many programs can play
sound simultaneously, which was once difficult on Linux systems.
When all multimedia software is configured to use ALSA for sound
support, this limitation disappears. For more information about
ALSA, visit the project website at
<ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>.
</para>
</section>
<section>
<title>Ogg and Xiph.Org Foundation Formats</title>
<para>
Fedora includes complete support for the Ogg media container
format, and the Vorbis audio, Theora video, Speex audio, and
FLAC lossless audio formats. These freely-distributable formats
are not encumbered by patent or license restrictions. They
provide powerful and flexible alternatives to more popular,
restricted formats. The Fedora Project encourages the use of
open source formats in place of restricted ones. For more
information on these formats and how to use them, refer to the
Xiph.Org Foundation's web site at
<ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>.
</para>
</section>
<section>
<title>MP3, DVD and Other Excluded Multimedia</title>
<para>
Fedora Core and Fedora Extras cannot include support for MP3 or
DVD playback or recording, because the MP3 and MPEG (DVD)
formats are patented, and the patent owners have not provided
the necessary licenses. Fedora also excludes several multimedia
application programs due to patent or license restrictions, such
as Flash Player and Real Player. For more on this subject,
please refer to
<ulink url='http://fedoraproject.org/wiki/ForbiddenItems'>http://fedoraproject.org/wiki/ForbiddenItems</ulink>.
</para>
</section>
<section>
<title>CD and DVD Authoring and Burning</title>
<para>
Fedora Core and Extras include a variety of tools for easily mastering
and burning CDs and DVDs. GNOME users can burn directly from the
Nautilus file manager, or choose the <code>gnomebaker</code> or
<code>graveman</code> packages from Fedora Extras, or the older
<code>xcdroast</code> package from Fedora Core. KDE users can use the
robust <code>k3b</code> package for these tasks. Console tools include
<code>cdrecord</code>, <code>readcd</code>, <code>mkisofs</code>, and
other typical Linux applications.
</para>
</section>
<section>
<title>Screencasts</title>
<para>
You can use Fedora to create and play back
<emphasis>screencasts</emphasis>, which are recorded desktop sessions,
using open technologies. Fedora Extras 5 includes <code>istanbul</code>,
which creates screencasts using the Theora video format. These videos
can be played back using one of several players included in Fedora Core.
This is the preferred way to submit screencasts to the Fedora Project
for either developer or end-user use. For a more comprehensive how-to,
refer to <ulink
url='http://fedoraproject.org/wiki/ScreenCasting'>http://fedoraproject.org/wiki/ScreenCasting</ulink>.
</para>
</section>
<section>
<title>Extended Support through Plugins</title>
<para>
Most of the media players in Fedora Core and Fedora Extras support the
use of plugins to add support for additional media formats and sound
output systems. Some use powerful backends, like <code>gstreamer</code>,
to handle media format support and sound output. Plugin packages for
these backends and for individual applications are available in Fedora
Core and Fedora Extras, and additional plugins may be available from
third parties to add even greater capabilities.
</para>
</section>
</section>
</article>
--- NEW FILE Networking.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Networking">
<title>Networking</title>
<section>
<title>User Tools</title>
<section>
<title>NetworkManager</title>
<para>
<emphasis role='strong'>NetworkManager</emphasis> now has support for
DHCP hostname, NIS, ISDN, WPA, WPA supplicant
(<code>wpa_supplicant</code>), and WPA-Enteprise. It has a new
wireless security layer. The VPN and dial up support has been
enhanced. Applications such as <emphasis
role='strong'>Evolution</emphasis> now integrate with <emphasis
role='strong'>NetworkManager</emphasis> to provide dynamic
networking capabilities. <emphasis
role='strong'>NetworkManager</emphasis> is disabled by default in
Fedora as it is not yet suitable for certain configurations, such as
system-wide static IPs, bonding devices, or starting a wireless
network connection before login.
</para>
<para>
To enable <emphasis role='strong'>NetworkManager</emphasis>
from the desktop:
</para>
<orderedlist numeration='arabic'>
<listitem>
<para>
Open the <emphasis role='strong'>Services</emphasis>
application from the menu <emphasis>System >
Administration Services</emphasis>
</para>
</listitem>
<listitem>
<para>
From the <emphasis>Edit Runlevel menu</emphasis>, choose
<emphasis>Runlevel All</emphasis>
</para>
</listitem>
<listitem>
<para>
Ensure that the 3 boxes next to the
<emphasis>dhcdbd</emphasis> item in left-side list are
checked
</para>
</listitem>
<listitem>
<para>
Select <emphasis>dhcdbd</emphasis> in the list, and click
the <emphasis>Start</emphasis> button
</para>
</listitem>
<listitem>
<para>
Ensure that the 3 boxes next to the
<emphasis>named</emphasis> item in left-hand list are
checked
</para>
</listitem>
<listitem>
<para>
Select <emphasis>named</emphasis> in the list, and click
the <emphasis>Start</emphasis> button
</para>
</listitem>
<listitem>
<para>
Ensure that the 3 boxes next to the
<emphasis><ulink url='/NetworkManager'>NetworkManager</ulink>
</emphasis> item in left-side list are checked
</para>
</listitem>
<listitem>
<para>
Select
<emphasis><ulink url='/NetworkManager'>NetworkManager</ulink>
</emphasis> in the list, and click the
<emphasis>Start</emphasis> button
</para>
</listitem>
</orderedlist>
<para>
To enable <emphasis role='strong'>NetworkManager</emphasis>
from the command line or terminal:
</para>
<orderedlist numeration='arabic'>
<listitem>
<para>
su -c '/sbin/chkconfig --level 345 dhcdbd on'
</para>
</listitem>
<listitem>
<para>
su -c '/sbin/service dhcdbd start'
</para>
</listitem>
<listitem>
<para>
su -c '/sbin/chkconfig --level 345 named on'
</para>
</listitem>
<listitem>
<para>
su -c '/sbin/service named start'
</para>
</listitem>
<listitem>
<para>
su -c '/sbin/chkconfig --level 345
<ulink url='/NetworkManager'>NetworkManager</ulink> on'
</para>
</listitem>
<listitem>
<para>
su -c '/sbin/service
<ulink url='/NetworkManager'>NetworkManager</ulink> start'
</para>
</listitem>
</orderedlist>
<para>
For a list of common wireless cards and drivers that
<emphasis role='strong'>NetworkManager</emphasis> supports,
refer to the
<ulink url='http://live.gnome.org/NetworkManagerHardware'>NetworkManager
Hardware</ulink> page.
</para>
</section>
<section>
<title>iproute</title>
<para>
The IPv4 address deletion algorithm did not take the prefix length
into account up to kernel version 2.6.12. Since this has changed, the
<code>ip</code> tool from the <code>iproute</code> package now issues
a warning if no prefix length is provided, to warn about possible
unintended deletions:
</para>
<itemizedlist>
<listitem>
<screen>
ip addr list dev eth0
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
inet 10.0.0.3/24 scope global eth0
</screen>
<screen>
su -c 'ip addr del 10.0.0.3 dev eth0'
Warning: Executing wildcard deletion to stay compatible with old
scripts. Explicitly specify the prefix length (10.0.0.3/32) to
avoid this warning. This special behaviour is likely to disappear
in further releases, fix your scripts!
</screen>
</listitem>
</itemizedlist>
<para>
The correct method of deleting the address and thus avoiding
the warning is:
</para>
<screen>
su -c 'ip addr del 10.0.0.3/24 dev eth0'
</screen>
<para>
Previously, it was not possible to tell if an interface was down
administratively or because no carrier was found, such as if a cable
were unplugged. The new flag <code>NO-CARRIER</code> now appears as a
link flag if the link is administratively up but no carrier can be
found.
</para>
<para>
The <code>ip</code> command now supports a batch mode via the argument
<code>-batch</code>, which works similar to the <code>tc</code>
command to speed up batches of tasks.
</para>
</section>
</section>
<section>
<title>Major Kernel Changes 2.6.11 - 2.6.15</title>
<para>
Refer to
<ulink url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.kernelnewbies.org/LinuxChanges</ulink>
for a list of major changes. Some of them are highlighted below.
</para>
<section>
<title>IPv4 Address Promotion</title>
<para>
Starting with version 2.6.12 of the kernel, a new feature has been
added called <emphasis>named address promotion</emphasis>. This
feature allows secondary IPv4 addresses to be promoted to primary
addresses. Usually when the primary address is deleted, all secondary
addresses are deleted as well. If you enable the new
<code>sysctl</code> key
<code>net.ipv4.conf.all.promote_secondaries</code>, or one of the
interface specific variants, you can change this behavior to promote
one of the secondary addresses to be the new primary address.
</para>
</section>
<section>
<title>Configurable Source Address for ICMP Errors</title>
<para>
By default, when selecting the source address for ICMP error messages,
the kernel uses the address of the interface on which the ICMP error
is going to be sent. Kernel version 2.6.12 introduces the new
<code>sysctl</code> key
<code>net.ipv4.icmp_errors_use_inbound_ifaddr</code>. If you enable
this option the kernel uses the address of the interface that received
the original error-causing packet.
</para>
<para>
Suppose the kernel receives a packet on interface <code>eth0</code>
which generates an ICMP error, and the routing table causes the error
message to be generated on interface <code>eth1</code>. If the new
<code>sysctl</code> option is enabled, the ICMP error message
indicates the source address as interface <code>eth0</code>, instead
of the default <code>eth1</code>. This feature may ease network
debugging in asynchronous routing setups.
</para>
</section>
<section>
<title>LC-Trie Based Routing Lookup Algorithm</title>
<para>
A new routing lookup algorithm called
<emphasis>trie</emphasis> has been added. It is intended for
large routing tables and shows a clear performance improvement
over the original hash implementation, at the cost of
increased memory consumption and complexity.
</para>
</section>
<section>
<title>Pluggable Congestion Control Algorithm Infrastructure</title>
<para>
TCP congestion control algorithms are now pluggable and thus
modular. The legacy New<emphasis role='strong'/>Reno algorithm
remains the default, and acts as the fallback algorithm. The
following new congestion control algorithms have been added:
</para>
<itemizedlist>
<listitem>
<para>
High Speed TCP congestion control
</para>
</listitem>
<listitem>
<para>
TCP Hybla congestion avoidance
</para>
</listitem>
<listitem>
<para>
H-TCP congestion control
</para>
</listitem>
<listitem>
<para>
Scalable TCP congestion control
</para>
</listitem>
</itemizedlist>
<para>
All existing congestion control modules have been converted to
this new infrastructure, and the BIC congestion control has
received enhancements from BICTCP 1.1 to handle low latency
links.
</para>
<note>
<title>Affecting the Congestion Control Algorithm</title>
<para>
The congestion control algorithm is socket specific, and may be
changed via the socket option <code>TCP_CONGESTION</code>.
</para>
</note>
</section>
<section>
<title>Queue Avoidance upon Carrier Loss</title>
<para>
When a network driver notices a carrier loss, such as when the
cable is pulled out, the driver stops the queue in front of
the driver. In the past, this stoppage caused the packets to
be queued at the queueing discipline layer for an unbound
period of time causing unexpected effects. In order to prevent
this effect, the core networking stack now refuses to queue
any packets for a device that is operationally down, that is,
has its queue disabled.
</para>
</section>
<section>
<title>DCCP Protocol Support</title>
<para>
Kernel version 2.6.14-rc1 was the first version to receive
support for the DCCP protocol. The implementation is still
experimental, but is known to work. Developers have begun work
to make userspace applications aware of this new protocol.
</para>
</section>
<section>
<title>Wireless</title>
<para>
A new HostAP driver appears in the kernel starting in
2.6.14-rc1, which allows the emulation of a wireless access
point through software. Currently this driver only works for
Intersil Prism2-based cards (PC Card/PCI/PLX). Support for
wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been
added.
</para>
</section>
<section>
<title>Miscellaneous</title>
<itemizedlist>
<listitem>
<para>
Many TCP Segmentation Offloading (TSO) related fixes are
included.
</para>
</listitem>
<listitem>
<para>
A new textsearch infrastructure has been added, and is
usable with corresponding iptables and extended match.
</para>
</listitem>
<listitem>
<para>
Both the IPv4 and IPv6 multicast joining interface visible
by userspace have been reworked and brought up to the
latest standards.
</para>
</listitem>
<listitem>
<para>
The SNMPv2 MIB counter ipInAddrErrors is supported for
IPv4.
</para>
</listitem>
<listitem>
<para>
Various new socket options proposed in Advanced API
(RFC3542) have been added.
</para>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE OverView.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-OverView">
<title>Fedora Core 5 Tour</title>
<para>
You can find a tour filled with pictures and videos of this exciting new
release at <ulink
url='http://fedoraproject.org/wiki/Tours/FedoraCore5'>http://fedoraproject.org/wiki/Tours/FedoraCore5</ulink>.
</para>
<section>
<title>What Is New In Fedora Core 5</title>
<para>
This release is the culmination of nine months of development, and
includes significant new versions of many key products and technologies.
The following sections provide a brief overview of major changes from
the last release of Fedora Core.
</para>
<section>
<title>Desktop</title>
<para>
Some of the highlights of this release include:
</para>
<itemizedlist>
<listitem>
<para>
There is a completely revamped appearance with a bubbly new theme
and the first use of the new Fedora logo.
</para>
</listitem>
<listitem>
<para>
Early work from the Fedora Rendering Project is integrated into
the desktop. This new project (<ulink
url='http://fedoraproject.org/wiki/RenderingProject'>http://fedoraproject.org/wiki/RenderingProject</ulink>)
is going to provide the technical foundations for advanced desktop
interfaces based on OpenGL.
</para>
</listitem>
<listitem>
<para>
Innovative new versions of the popular desktop environments GNOME
and KDE are included in this release. The GNOME desktop is based
on the 2.14 release (<ulink
url='http://www.gnome.org/start/2.14/notes/C/'>http://www.gnome.org/start/2.14/notes/C/</ulink>),
and the KDE 3.5 desktop is the general 3.5 release (<ulink
url='http://kde.org/announcements/announce-3.5.php'>http://kde.org/announcements/announce-3.5.php</ulink>).
</para>
</listitem>
<listitem>
<para>
The latest versions of <emphasis role='strong'>GNOME Power
Manager</emphasis> (<ulink
url='http://www.gnome.org/projects/gnome-power-manager/'>http://www.gnome.org/projects/gnome-power-manager/</ulink>)
and <emphasis role='strong'>GNOME Screensaver</emphasis>(<ulink
url='http://live.gnome.org/GnomeScreensaver/'>http://live.gnome.org/GnomeScreensaver/</ulink>)
provide new and integrated power management capabilities.
</para>
</listitem>
<listitem>
<para>
The new <emphasis role='strong'>GNOME User Share</emphasis>
facility provides simple and efficient file sharing.
</para>
</listitem>
<listitem>
<para>
LUKS (<ulink
url='http://luks.endorphin.org/'>http://luks.endorphin.org/</ulink>)
hard disk encryption is integrated with <emphasis
role='strong'>HAL</emphasis> and <emphasis
role='strong'>GNOME</emphasis> in this release. Refer to <ulink
url='http://fedoraproject.org/wiki/Software/LUKS'>http://fedoraproject.org/wiki/Software/LUKS</ulink>
for more information.
</para>
</listitem>
<listitem>
<para>
Software suspend (hibernate) capability is now provided for a wide
variety of hardware. Suspend to RAM feature has also been improved
due to infrastructure work done to support hiberation.
</para>
</listitem>
<listitem>
<para>
The previous graphical software management utilities have been
replaced with the first versions of a new generation of tools.
This release includes <emphasis role='strong'>Pup</emphasis>, a
simple interface for system updates, and <emphasis
role='strong'>Pirut</emphasis>, a new package manager that
replaces <code>system-config-packages</code>. These applications
are built on the <code>yum</code> utility to provide consistent
software installation and update facilities throughout the system.
</para>
</listitem>
<listitem>
<para>
This release of Fedora includes Mono support for the first time,
and Mono applications such as <emphasis
role='strong'>Beagle</emphasis>, a desktop search interface;
<emphasis role='strong'>F-Spot</emphasis>, a photo management
utility; and <emphasis role='strong'>Tomboy</emphasis>, a
note-taking application.
</para>
</listitem>
<listitem>
<para>
Desktop applications now built using the fully-open
<code>java-gcj-compat</code> include <emphasis
role='strong'>Azureus</emphasis>, a <ulink
url='/BitTorrent'>BitTorrent</ulink> client, and <emphasis
role='strong'>RSSOwl</emphasis>, a RSS feed reader, now
available in Fedora Extras.
</para>
</listitem>
<listitem>
<para>
You can now enjoy enhanced multimedia support with version 0.10 of
the <emphasis role='strong'>Gstreamer</emphasis> media framework.
This milestone release brings major improvements in robustness,
compatibility, and features over previous versions of <emphasis
role='strong'>Gstreamer</emphasis>. The <emphasis
role='strong'>Totem</emphasis> movie player and other media
software in this release have been updated to use the new
framework.
</para>
</listitem>
<listitem>
<para>
There is dramatically improved internationalization support with
<emphasis role='strong'>SCIM</emphasis> in Fedora Core 5. The
<emphasis role='strong'>SCIM</emphasis> language input framework
provides an easy to use interface for inputting many different
non-English languages. <emphasis role='strong'>SCIM</emphasis>
replaces the <emphasis role='strong'>IIIMF</emphasis> system used
in previous Fedora releases.
</para>
</listitem>
<listitem>
<para>
The default Web browser is the latest in the <emphasis
role='strong'>Firefox</emphasis> 1.5.0.x series (<ulink
url='http://www.mozilla.com/firefox/releases/1.5.html'>http://www.mozilla.com/firefox/releases/1.5.html</ulink>),
which has many new features for faster, safer, and more efficient
browsing.
</para>
</listitem>
<listitem>
<para>
The office applications suite <emphasis
role='strong'>OpenOffice.org</emphasis> 2.0.2 (<ulink
url='http://www.openoffice.org/product/index.html'>http://www.openoffice.org/product/index.html</ulink>)
now makes better use of general system libraries for increased
performance and efficiency.
</para>
</listitem>
<listitem>
<para>
A large number of <emphasis role='strong'>GTK</emphasis> and
<emphasis role='strong'>GNOME</emphasis> programs take advantage
of the <emphasis role='strong'>Cairo</emphasis> 2D graphics
library (<ulink
url='http://cairographics.org/'>http://cairographics.org/</ulink>),
included in this release, to provide streamlined attractive
graphical interfaces.
</para>
</listitem>
<listitem>
<para>
There are new experimental drivers that provide support for the
widely-used Broadcom 43xx wireless chipsets (<ulink
url='http://bcm43xx.berlios.de/'>http://bcm43xx.berlios.de/</ulink>).
</para>
</listitem>
<listitem>
<para>
<emphasis role='strong'>NetworkManager</emphasis> (<ulink
url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink>)
has received numerous menu, user interface, and functionality
improvements. However, it is disabled by default in this release
as it is not yet suitable for certain configurations, such as
system-wide static IPs or bonding devices.
</para>
</listitem>
<listitem>
<para>
This release includes <code>libnotify</code>, a library that
features simple and attractive notifications for the desktop.
</para>
</listitem>
<listitem>
<para>
Fedora Core now uses <code>gnome-mount</code>, a more efficient
mechanism that replaces <code>fstab-sync</code>, and uses HAL to
handle mounting.
</para>
</listitem>
<listitem>
<para>
Printing support is improved in this release with the inclusion of
the <code>hplip</code> utility, which replaces <code>hpijs</code>.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Administration</title>
<para>
Improvements for administrators and developers include:
</para>
<itemizedlist>
<listitem>
<para>
The <emphasis role='strong'>Xen</emphasis> virtualization system
has enhanced support. The tools to configure <emphasis
role='strong'>Xen</emphasis> virtual machines on your Fedora
Core system now use the standard graphical installation process,
run as a window on your desktop. Fedora developers have also
created <code>gnome-applet-vm</code>, which provides a simple
virtual domains monitor applet, and <code>libvirt</code> (<ulink
url='http://libvirt.org/'>http://libvirt.org/</ulink>), a
library providing an API to use Xen virtualization capabilities.
</para>
</listitem>
<listitem>
<para>
The industry-leading <code>anaconda</code> installation system
continues to evolve. New features for this release include remote
logging and improved support for tracebacks. Package management in
the installation system is now provided by <code>yum</code>. This
enhancement is the first step in enabling access to Fedora Extras
from within the installation process.
</para>
</listitem>
<listitem>
<para>
Version 2.2 of the <emphasis role='strong'>Apache</emphasis> HTTP
server is now included. This release provides enhancements to
authentication, database support, proxy facilities, and content
filtering.
</para>
</listitem>
<listitem>
<para>
The latest generation of database servers are packaged in this
release, including both <emphasis role='strong'>MySQL</emphasis>
5.0 and <emphasis role='strong'>PostgreSQL</emphasis> 8.1.
</para>
</listitem>
<listitem>
<para>
Several native Java programs are now available compiled with
<code>GCJ</code>, such as the <emphasis
role='strong'>Geronimo</emphasis> J2EE server and the <emphasis
role='strong'>Apache Jakarta</emphasis> Project, in addition to
the Java programs and development capabilities in the previous
releases.
</para>
</listitem>
<listitem>
<para>
There are new tools for system monitoring and performance
analysis. This release includes <emphasis
role='strong'>SystemTap</emphasis> (<ulink
url='http://fedoraproject.org/wiki/SystemTap'>http://fedoraproject.org/wiki/SystemTap</ulink>),
an instrumentation system for debugging and analyzing performance
bottle necks, and <emphasis role='strong'>Frysk</emphasis> (<ulink
url='http://fedoraproject.org/wiki/Frysk'>http://fedoraproject.org/wiki/Frysk</ulink>),
an execution analysis technology for monitoring running processes
or threads which are provided as technology previews in this
release.
</para>
</listitem>
<listitem>
<para>
This release includes <code>system-config-cluster</code>, a
utility that allows you to manage cluster configuration in a
graphical setting.
</para>
</listitem>
<listitem>
<para>
The combination of <emphasis role='strong'>Kexec</emphasis> and
<emphasis role='strong'>Kdump</emphasis> (<ulink
url='http://lse.sourceforge.net/kdump/'>http://lse.sourceforge.net/kdump/</ulink>)
utilities provides modern crash dumping facilities and potential
for faster bootup, bypassing the firmware on reboots. <emphasis
role='strong'>Kexec</emphasis> loads a new kernel from a running
kernel, and <emphasis role='strong'>Kdump</emphasis> can provide a
memory dump of the previous kernel for debugging.
</para>
</listitem>
<listitem>
<para>
This release includes <code>iscsi-initiator-utils</code>, iSCSI
daemon and utility programs that provide support for hardware
using the iSCSI interface.
</para>
</listitem>
<listitem>
<para> <code>fedora-release</code> now includes the software
repositories for debuginfo packages and source
<code>rpm</code> packages.
</para>
</listitem>
<listitem>
<para> <code>fedora-release</code> now includes the software
repositories for Fedora Legacy community maintenance project.
(disabled by default)
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Level Changes</title>
<itemizedlist>
<listitem>
<para>
X.org X11R7.0 is included in this release. The new modular
architecture of R7.0 enables easier driver upgrades and simplifies
development, opening the way for rapid improvement in Linux
graphics.
</para>
</listitem>
<listitem>
<para>
The GCC 4.1 compiler (<ulink
url='http://gcc.gnu.org/gcc-4.1/changes.html'>http://gcc.gnu.org/gcc-4.1/changes.html</ulink>)
is included, and the entire set of Fedora packages is built with
this technology. This provides security and performance
enhancements throughout the system.
</para>
</listitem>
<listitem>
<para>
The kernels for this release are based on Linux 2.6.16. Refer to
the section on the kernel in these release notes for other
details.
</para>
</listitem>
<listitem>
<para>
The PCMCIA framework used by laptop and mobile devices has
changed. The older <code>pcmcia-cs</code> package using the
<code>cardmgr/pcmcia</code> service has been replaced with a new
<code>pcmciautils</code> package. With <code>pcmciautils</code>,
PCMCIA devices are handled directly and dynamically by the
<code>hotplug</code> and <code>udev</code> subsystems. This update
increases both efficiency and performance of the system. For more
information about these changes, refer to <ulink
url='http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html'>http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html</ulink>.
</para>
</listitem>
<listitem>
<para>
SELinux implementation has undergone a major change, with a switch
to the SELinux reference policy (<ulink
url='http://serefpolicy.sourceforge.net/'>http://serefpolicy.sourceforge.net/</ulink>).
The SELinux reference policy can support binary policy modules. It
is now possible to move SELinux policies into individual packages,
making it easier for users to ship site-specific policy
customizations when required. This version also adds support for
Multi-Category Security (MCS), enabled by default, and Multi-Level
Security (MLS). SELinux continues to offer support for TE (Type
Enforcement), enabled by default, and RBAC (Role-Based Access
Control). Refer to the section on SELinux in these release notes
for other details and links to SELinux resources on the Fedora
Project pages.
</para>
</listitem>
</itemizedlist>
<anchor id='udev'/>
<para></para>
<itemizedlist>
<listitem>
<para>
<code>udev</code> provides a new linking for device names that
includes the physical name of the device. For example, if your
CD-ROM is <code>/dev/hdc</code>, it gets symlinked to the friendly
name <code>/dev/cdrom-hdc</code>. If you have additional matching
devices, the same rule applies, so <code>/dev/hdd</code> is
symlinked to <code>/dev/cdrom-hdd</code>. This is true for
<code>/dev/scanner</code>, <code>/dev/floppy</code>,
<code>/dev/changer</code>, and so forth.
</para>
<para>
The typical name <code>/dev/cdrom</code> is also created, and
<code>udev</code> assigns it randomly to one of the
<code>/dev/cdrom-hdX</code> devices. This random assignment usually
sticks, but in some configurations the symlink may change on boot
to a different device. This does not affect CD burning
applications, but some CD player applications such as
<code>kscd</code> may be affected. If you wish, you can set your CD
player application to point at a specific CD-ROM device, such as
<code>/dev/cdrom-hdc</code>. This situation only occurs if you
have more than one of a type of device.
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Road Map</title>
<para>
The proposed plans for the next release of Fedora are available at
<ulink
url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>.
</para>
</section>
</section>
</article>
--- NEW FILE PackageChanges.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-PackageChanges">
<title>Package Changes</title>
<note>
<title>This list is automatically generated</title>
<para>
This list is automatically generated. It is not a good choice for
translation.
</para>
</note>
<para>
This list was made using the <code>treediff</code> utility, ran as
<code>treediff newtree oldtree</code> against the rawhide tree of 28 Feb.
2006.
</para>
<para>
For a list of which packages were updated since the previous
release, refer to this page:
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages'>http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/UpdatedPackages</ulink>
</para>
<para>
You can also find a comparison of major packages between all Fedora
versions at <ulink
url='http://distrowatch.com/fedora'>http://distrowatch.com/fedora</ulink>
</para>
<screen>
New package adaptx
AdaptX
New package agg
Anti-Grain Geometry
New package amtu
Abstract Machine Test Utility (AMTU)
New package anthy
Japanese character set input library
New package aspell-ru
Russian dictionaries for Aspell.
New package aspell-sl
Slovenian dictionaries for Aspell.
New package aspell-sr
Serbian dictionaries for Aspell.
New package avahi
Local network service discovery
New package axis
A SOAP implementation in Java
New package beagle
The Beagle Search Infrastructure
New package bsf
Bean Scripting Framework
New package bsh
Lightweight Scripting for Java
New package cairo
A vector graphics library
New package cairo-java
Java bindings for the Cairo library
New package castor
An open source data binding framework for Java
New package concurrent
Utility classes for concurrent Java programming
New package dev86
A real mode 80x86 assembler and linker.
New package dhcdbd
DHCP D-BUS daemon (dhcdbd) controls dhclient sessions with D-BUS, stores
and presents DHCP options.
New package ekiga
A Gnome based SIP/H323 teleconferencing application
New package elilo
ELILO linux boot loader for EFI-based systems
New package evolution-sharp
Evolution Data Server Mono Bindings
New package f-spot
Photo management application
New package frysk
Frysk execution analysis tool
New package gecko-sharp2
Gecko bindings for Mono
New package geronimo-specs
Geronimo J2EE server J2EE specifications
New package giflib
Library for manipulating GIF format image files
New package glib-java
Base Library for the Java-GNOME libraries
New package gmime
Library for creating and parsing MIME messages
New package gnome-applet-vm
Simple virtual domains monitor which embed themselves in the GNOME panel
New package gnome-mount
Mount replacement which uses HAL to do the mounting
New package gnome-power-manager
GNOME Power Manager
New package gnome-python2-desktop
The sources for additional PyGNOME Python extension modules for the
GNOME desktop.
New package gnome-screensaver
GNOME Sreensaver
New package gnome-user-share
Gnome user file sharing
New package gnu-efi
Development Libraries and headers for EFI
New package gpart
A program for recovering corrupt partition tables.
New package gsf-sharp
Mono bindings for libgsf
New package gstreamer-plugins-base
GStreamer streaming media framework base plug-ins
New package gstreamer-plugins-good
GStreamer plug-ins with good code and licensing
New package gtk-sharp
GTK+ and GNOME bindings for Mono
New package gtk-sharp2
GTK+ and GNOME bindings for Mono
New package hplip
HP Linux Imaging and Printing Project
New package hsqldb
Hsqldb Database Engine
New package icon-naming-utils
A script to handle icon names in desktop icon themes
New package icu
International Components for Unicode
New package imake
imake source code configuration and build system
New package iscsi-initiator-utils
iSCSI daemon and utility programs
New package iso-codes
ISO code lists and translations
New package jakarta-commons-codec
Jakarta Commons Codec Package
New package jakarta-commons-daemon
Jakarta Commons Daemon Package
New package jakarta-commons-discovery
Jakarta Commons Discovery
New package jakarta-commons-httpclient
Jakarta Commons HTTPClient Package
New package javacc
A parser/scanner generator for java
New package jdom
Java alternative to DOM and SAX
New package jgroups
Toolkit for reliable multicast communication.
New package jrefactory
JRefactory and Pretty Print
New package kasumi
An anthy dictionary management tool.
New package kexec-tools
The kexec/kdump userspace component.
New package lcms
Color Management System
New package libFS
X.Org X11 libFS runtime library
New package libICE
X.Org X11 libICE runtime library
New package libSM
X.Org X11 libSM runtime library
New package libX11
X.Org X11 libX11 runtime library
New package libXScrnSaver
X.Org X11 libXss runtime library
New package libXTrap
X.Org X11 libXTrap runtime library
New package libXau
X.Org X11 libXau runtime library
New package libXaw
X.Org X11 libXaw runtime library
New package libXcomposite
X.Org X11 libXcomposite runtime library
New package libXcursor
X.Org X11 libXcursor runtime library
New package libXdamage
X.Org X11 libXdamage runtime library
New package libXdmcp
X.Org X11 libXdmcp runtime library
New package libXevie
X.Org X11 libXevie runtime library
New package libXext
X.Org X11 libXext runtime library
New package libXfixes
X.Org X11 libXfixes runtime library
New package libXfont
X.Org X11 libXfont runtime library
New package libXfontcache
X.Org X11 libXfontcache runtime library
New package libXft
X.Org X11 libXft runtime library
New package libXi
X.Org X11 libXi runtime library
New package libXinerama
X.Org X11 libXinerama runtime library
New package libXmu
X.Org X11 libXmu/libXmuu runtime libraries
New package libXp
X.Org X11 libXp runtime library
New package libXpm
X.Org X11 libXpm runtime library
New package libXrandr
X.Org X11 libXrandr runtime library
New package libXrender
X.Org X11 libXrender runtime library
New package libXres
X.Org X11 libXres runtime library
New package libXt
X.Org X11 libXt runtime library
New package libXtst
X.Org X11 libXtst runtime library
New package libXv
X.Org X11 libXv runtime library
New package libXvMC
X.Org X11 libXvMC runtime library
New package libXxf86dga
X.Org X11 libXxf86dga runtime library
New package libXxf86misc
X.Org X11 libXxf86misc runtime library
New package libXxf86vm
X.Org X11 libXxf86vm runtime library
New package libchewing
Intelligent phonetic input method library for Traditional Chinese
New package libdaemon
library for writing UNIX daemons
New package libdmx
X.Org X11 libdmx runtime library
New package libdrm
libdrm Direct Rendering Manager runtime library
New package libevent
Abstract asynchronous event notification library
New package libfontenc
X.Org X11 libfontenc runtime library
New package libgdiplus
libgdiplus: An Open Source implementation of the GDI+ API
New package libgpod
Library to access the contents of an iPod
New package libgssapi
Generic Security Services Application Programming Interface Library
New package libiec61883
Streaming library for IEEE1394
New package liblbxutil
X.Org X11 liblbxutil runtime library
New package libnl
Convenience library for kernel netlink sockets
New package libnotify
libnotify notification library
New package liboil
Library of Optimized Inner Loops, CPU optimized functions
New package liboldX
X.Org X11 liboldX runtime library
New package libpfm
a performance monitoring library for Linux/ia64
New package librtas
Libraries to provide access to RTAS calls and RTAS events.
New package libsemanage
SELinux binary policy manipulation library
New package libsetrans
SELinux Translation library
New package libstdc++so7
libstdc++.so.7 preview
New package libunwind
An unwinding library for ia64.
New package libvirt
Library providing an API to use the Xen virtualization
New package libvte-java
Wrapper library for GNOME VTE
New package libxkbfile
X.Org X11 libxkbfile runtime library
New package libxkbui
X.Org X11 libxkbui runtime library
New package lucene
High-performance, full-featured text search engine
New package m17n-db
Multilingualization datafiles for m17n-lib
New package m17n-lib
Multilingual text library
New package mesa
Mesa graphics libraries
New package mlocate
An utility for finding files by name
New package mockobjects
Java MockObjects package
New package mono
a .NET runtime environment
New package mysql-connector-odbc
ODBC driver for MySQL
New package mysqlclient14
Backlevel MySQL shared libraries.
New package nautilus-sendto
Nautilus context menu for sending files
New package nfs-utils-lib
Network File System Support Library
New package notify-daemon
Notification Daemon
New package nspr
Netscape Portable Runtime
New package opal
Open Phone Abstraction Library
New package openCryptoki
Implementation of Cryptoki v2.11 for IBM Crypto Hardware
New package opensp
SGML and XML parser
New package pcmciautils
PCMCIA utilities and initialization programs
New package perl-Net-IP
Perl module for manipulation of IPv4 and IPv6 addresses
New package perl-String-CRC32
Perl interface for cyclic redundency check generation
New package perl-XML-Simple
Easy API to maintain XML in Perl
New package pfmon
a performance monitoring tool for Linux/ia64
New package php-pear
PHP Extension and Application Repository framework
New package pirut
Package Installation, Removal and Update Tools
New package prctl
Utility to perform process operations
New package pycairo
Python bindings for the cairo library
New package pykickstart
A python library for manipulating kickstart files
New package python-pyblock
Python modules for dealing with block devices
New package rhpxl
Python library for configuring and running X.
New package s390utils
Linux/390 specific utilities.
New package salinfo
SAL info tool.
New package scim
Smart Common Input Method platform
New package scim-anthy
SCIM IMEngine for anthy for Japanese input
New package scim-chewing
Chewing Chinese input method for SCIM
New package scim-hangul
Hangul Input Method Engine for SCIM
New package scim-m17n
SCIM IMEngine for m17n-lib
New package scim-pinyin
Smart Pinyin IMEngine for Smart Common Input Method platform
New package scim-qtimm
SCIM input method module for Qt
New package scim-tables
SCIM Generic Table IMEngine
New package squashfs-tools
squashfs utilities
New package system-config-cluster
system-config-cluster is a utility which allows you to manage cluster
configuration in a graphical setting.
New package systemtap
Instrumentation System
New package tanukiwrapper
Java Service Wrapper
New package tog-pegasus
OpenPegasus WBEM Services for Linux
New package tomboy
Tomboy is a desktop note-taking application for Linux and Unix.
New package velocity
Java-based template engine
New package werken.xpath
XPath implementation using JDOM
New package wpa_supplicant
WPA/WPA2/IEEE 802.1X Supplicant
New package wsdl4j
Web Services Description Language Toolkit for Java
New package xdoclet
XDoclet Attribute Orientated Programming Framework
New package xjavadoc
The XJavaDoc engine
New package xmlrpc
Java XML-RPC implementation
New package xorg-x11-apps
X.Org X11 applications
New package xorg-x11-drivers
X.Org X11 driver installation package
New package xorg-x11-drv-acecad
Xorg X11 acecad input driver
New package xorg-x11-drv-aiptek
Xorg X11 aiptek input driver
New package xorg-x11-drv-apm
Xorg X11 apm video driver
New package xorg-x11-drv-ark
Xorg X11 ark video driver
New package xorg-x11-drv-ati
Xorg X11 ati video driver
New package xorg-x11-drv-calcomp
Xorg X11 calcomp input driver
New package xorg-x11-drv-chips
Xorg X11 chips video driver
New package xorg-x11-drv-cirrus
Xorg X11 cirrus video driver
New package xorg-x11-drv-citron
Xorg X11 citron input driver
New package xorg-x11-drv-cyrix
Xorg X11 cyrix video driver
New package xorg-x11-drv-digitaledge
Xorg X11 digitaledge input driver
New package xorg-x11-drv-dmc
Xorg X11 dmc input driver
New package xorg-x11-drv-dummy
Xorg X11 dummy video driver
New package xorg-x11-drv-dynapro
Xorg X11 dynapro input driver
New package xorg-x11-drv-elo2300
Xorg X11 elo2300 input driver
New package xorg-x11-drv-elographics
Xorg X11 elographics input driver
New package xorg-x11-drv-evdev
Xorg X11 evdev input driver
New package xorg-x11-drv-fbdev
Xorg X11 fbdev video driver
New package xorg-x11-drv-fpit
Xorg X11 fpit input driver
New package xorg-x11-drv-glint
Xorg X11 glint video driver
New package xorg-x11-drv-hyperpen
Xorg X11 hyperpen input driver
New package xorg-x11-drv-i128
Xorg X11 i128 video driver
New package xorg-x11-drv-i740
Xorg X11 i740 video driver
New package xorg-x11-drv-i810
Xorg X11 i810 video driver
New package xorg-x11-drv-jamstudio
Xorg X11 jamstudio input driver
New package xorg-x11-drv-joystick
Xorg X11 joystick input driver
New package xorg-x11-drv-keyboard
Xorg X11 keyboard input driver
New package xorg-x11-drv-magellan
Xorg X11 magellan input driver
New package xorg-x11-drv-magictouch
Xorg X11 magictouch input driver
New package xorg-x11-drv-mga
Xorg X11 mga video driver
New package xorg-x11-drv-microtouch
Xorg X11 microtouch input driver
New package xorg-x11-drv-mouse
Xorg X11 mouse input driver
New package xorg-x11-drv-mutouch
Xorg X11 mutouch input driver
New package xorg-x11-drv-neomagic
Xorg X11 neomagic video driver
New package xorg-x11-drv-nsc
Xorg X11 nsc video driver
New package xorg-x11-drv-nv
Xorg X11 nv video driver
New package xorg-x11-drv-palmax
Xorg X11 palmax input driver
New package xorg-x11-drv-penmount
Xorg X11 penmount input driver
New package xorg-x11-drv-rendition
Xorg X11 rendition video driver
New package xorg-x11-drv-s3
Xorg X11 s3 video driver
New package xorg-x11-drv-s3virge
Xorg X11 s3virge video driver
New package xorg-x11-drv-savage
Xorg X11 savage video driver
New package xorg-x11-drv-siliconmotion
Xorg X11 siliconmotion video driver
New package xorg-x11-drv-sis
Xorg X11 sis video driver
New package xorg-x11-drv-sisusb
Xorg X11 sisusb video driver
New package xorg-x11-drv-spaceorb
Xorg X11 spaceorb input driver
New package xorg-x11-drv-summa
Xorg X11 summa input driver
New package xorg-x11-drv-tdfx
Xorg X11 tdfx video driver
New package xorg-x11-drv-tek4957
Xorg X11 tek4957 input driver
New package xorg-x11-drv-trident
Xorg X11 trident video driver
New package xorg-x11-drv-tseng
Xorg X11 tseng video driver
New package xorg-x11-drv-ur98
Xorg X11 ur98 input driver
New package xorg-x11-drv-v4l
Xorg X11 v4l video driver
New package xorg-x11-drv-vesa
Xorg X11 vesa video driver
New package xorg-x11-drv-vga
Xorg X11 vga video driver
New package xorg-x11-drv-via
Xorg X11 via video driver
New package xorg-x11-drv-vmware
Xorg X11 vmware video driver
New package xorg-x11-drv-void
Xorg X11 void input driver
New package xorg-x11-drv-voodoo
Xorg X11 voodoo video driver
New package xorg-x11-filesystem
X.Org X11 filesystem layout
New package xorg-x11-font-utils
X.Org X11 font utilities
New package xorg-x11-fonts
X.Org X11 fonts
New package xorg-x11-proto-devel
X.Org X11 Protocol headers
New package xorg-x11-resutils
X.Org X11 X resource utilities
New package xorg-x11-server
X.Org X11 X server
New package xorg-x11-server-utils
X.Org X11 X server utilities
New package xorg-x11-twm
X.Org X11 twm window manager
New package xorg-x11-util-macros
X.Org X11 Autotools macros
New package xorg-x11-utils
X.Org X11 X client utilities
New package xorg-x11-xauth
X.Org X11 X authority utilities
New package xorg-x11-xbitmaps
X.Org X11 application bitmaps
New package xorg-x11-xdm
X.Org X11 xdm - X Display Manager
New package xorg-x11-xfs
X.Org X11 xfs font server
New package xorg-x11-xfwp
X.Org X11 X firewall proxy
New package xorg-x11-xinit
X.Org X11 X Window System xinit startup scripts
New package xorg-x11-xkb-utils
X.Org X11 xkb utilities
New package xorg-x11-xkbdata
xkb data files for the X.Org X11 X server
New package xorg-x11-xsm
X.Org X11 X Session Manager
New package xorg-x11-xtrans-devel
X.Org X11 developmental X transport library
Removed package Canna
Removed package 4Suite
Removed package MyODBC
Removed package apel
Removed package VFlib2
Removed package anaconda-help
Removed package aqhbci
Removed package cdicconf
Removed package fonts-xorg
Removed package gimp-gap
Removed package gnome-kerberos
Removed package gnomemeeting
Removed package hotplug
Removed package howl
Removed package hpijs
Removed package hpoj
Removed package iiimf
Removed package iiimf-le-chinput
Removed package iiimf-le-xcin
Removed package libgal2
Removed package libungif
Removed package lvm2-cluster
Removed package mod_jk
Removed package nvi-m17n
Removed package openh323
Removed package openmotif21
Removed package pcmcia-cs
Removed package perl-Filter
Removed package perl-Filter-Simple
Removed package perl-Parse-Yapp
Removed package perl-RPM2
Removed package perl-Time-HiRes
Removed package perl-XML-Encoding
Removed package perl-libxml-enno
Removed package python-twisted
Removed package sash
Removed package schedutils
Removed package selinux-policy-targeted
Removed package selinux-policy-strict
Removed package slocate
Removed package struts11
Removed package system-config-mouse
Removed package system-config-packages
Removed package taipeifonts
Removed package w3c-libwww
Removed package xinitrc
Removed package usbview
</screen>
</section>
</article>
--- NEW FILE PackageNotes.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-PackageNotes">
<title>Package Notes</title>
<para>
The following sections contain information regarding software
packages that have undergone significant changes for Fedora Core .
For easier access, they are generally organized using the same
groups that are shown in the installation system.
</para>
<section>
<title>Core utilities POSIX changes</title>
<para>
The
<code>coreutils</code> package now follows the POSIX standard version 200112. This
change in behavior might affect scripts and command arguments
that were previously deprecated. For example, if you have a
newer system but are running software that assumes an older
version of POSIX and uses <code>sort +1</code> or <code>tail +10</code>, you can work around any compatibility problems by setting <code>_POSIX2_VERSION=199209</code> in your environment. Refer to the section on standards in the <code>coreutils</code> info manual for more information on this. You can run the
following command to read this information.
</para>
<screen>
info coreutils Standards
</screen>
</section>
<section>
<title>Pango Text Renderer for Firefox</title>
<para>
Fedora is building Firefox with the Pango system as the text
renderer. This provides better support for certain language
scripts, such as Indic and some CJK scripts. Pango is included
with with permission of the Mozilla Corporation. This change is
known to break rendering of MathML, and may negatively impact
performance on some pages. To disable the use of Pango, set your
environment before launching Firefox:
</para>
<screen>
MOZ_DISABLE_PANGO=1 /usr/bin/firefox
</screen>
<para>
Alternately, you can include this environment variable as part
of a wrapper script.
</para>
</section>
<section>
<title>Smbfs deprecated</title>
<para>
The kernel implementation of
<emphasis role='strong'>smbfs</emphasis> to support the Windows
file sharing protocol has been deprecated in favor of
<emphasis role='strong'>cifs</emphasis>, which is backwards
compatible with <emphasis role='strong'>smbfs</emphasis> in
features and maintenance. It is recommended that you use the
<emphasis role='strong'>cifs</emphasis> filesystem in place of
<emphasis role='strong'>smbfs</emphasis>.
</para>
</section>
<section>
<title>Yum kernel handling plugin</title>
<para>
A <code>yum</code> plugin written by Red Hat developers is provided by default
within the yum package which only retains the latest two kernels
in addition to the one being installed when you perform updates
on your system. This feature can be fine tuned to retain more or
less kernels or disabled entirely through the <code>/etc/yum/pluginconf.d/installonlyn.conf</code> file. There are other plugins and utilities available as part of <code>yum-utils</code> package in Fedora Extras software repository. You can install
them using the following command.
</para>
<screen>
yum install yum-utils
</screen>
</section>
<section>
<title>Yum cache handling behavior changes</title>
<para>
By default, <code>yum</code> is now configured to remove headers and
packages downloaded after a successful install to reduce the ongoing
disk space requirements of updating a Fedora system. Most users have
little or no need for the packages once they have been installed on the
system. For cases where you wish to preserve the headers and packages
(for example, if you share your <code>/var/cache/yum</code> directory
between multiple machines), modify the keepcache option to
<code>1</code> in <code>/etc/yum.conf</code>.
</para>
</section>
<section>
<title>Kernel device, module loading, and hotplug changes</title>
<para>
The hotplug and device handling subsystem has undergone significant
changes in Fedora Core. The <code>udev</code> method now handles all
module loading, both on system boot and for hotplugged devices. The
<code>hotplug</code> package has been removed, as it is no longer
needed.
</para>
<para>
Support for hotplug helpers via the <code>/etc/hotplug</code>,
<code>/etc/hotplug.d</code>, and <code>/etc/dev.d</code> directories is
deprecated, and may be removed in a future Fedora Core release. These
helpers should be converted to <code>udev</code> rules. Please see
<ulink
url='http://www.reactivated.net/writing_udev_rules.html'>http://www.reactivated.net/writing_udev_rules.html</ulink>
for examples.
</para>
</section>
<section>
<title>Systemwide Search Changes</title>
<note>
<title role="strong"><code>mlocate</code> Has Replaced
<code>slocate</code></title>
<para>
The new <code>mlocate</code> package provides the implementations of
<code>/usr/bin/locate</code> and <code>/usr/bin/updatedb</code>.
Previous Fedora releases included the <code>slocate</code> versions of
these programs.
</para>
</note>
<itemizedlist>
<listitem>
<para>
The <code>locate</code> command should be completely compatible.
</para>
</listitem>
<listitem>
<para>
The configuration file <code>/etc/updatedb.conf</code> is
compatible.
</para>
</listitem>
<listitem>
<para>
Syntax errors that <code>slocate</code> would not detect are now
reported.
</para>
</listitem>
<listitem>
<para>
The <code>DAILY_UPDATE</code> variable is not supported.
</para>
</listitem>
<listitem>
<para>
The <code>updatedb</code> command is <emphasis>not</emphasis>
compatible, and custom scripts that use <code>updatedb</code> may
have to be updated.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Mouse Configuration Utility Removed</title>
<para>
The <code>system-config-mouse</code> configuration utility has been dropped in this release because <code>synaptic</code> and three-button mouse configuration is handled automatically.
Serial mice are no longer supported.
</para>
</section>
<section>
<title>Up2date and RHN applet are removed</title>
<para>
The <code>up2date</code> and <code>rhn-applet</code> packages have been
removed from Fedora Core 5. Users are encouraged to use the
<code>yum</code> tool from the command line, and the <emphasis
role='strong'>Pirut</emphasis> software manager and <emphasis
role='strong'>Pup</emphasis> update tool from the desktop.
</para>
</section>
<section>
<title>NetworkManager</title>
<para>
Fedora systems use <code>Network</code> <code>Manager</code> to
automatically detect, select, and configure wired and wireless network
connections. Wireless network devices may require third-party software
or manual configuration to activate after the installation process
completes. For this reason, Fedora Core provides <code>Network</code>
<code>Manager</code> as an optional component.
</para>
<para>
Refer to <ulink
url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink>
for more information on how to install and enable <code>Network
Manager</code>.
</para>
</section>
<section>
<title>Dovecot</title>
<para>
Fedora Core includes a new version of the <code>dovecot</code> IMAP
server software, which has many changes in its configuration file. These
changes are of particular importance to users upgrading from a previous
release. Refer to <ulink
url='http://wiki.dovecot.org/UpgradingDovecot'>http://wiki.dovecot.org/UpgradingDovecot</ulink>
for more information on the changes.
</para>
</section>
<section>
<title>Kudzu</title>
<para>
The <code>kudzu</code> utility, <code>libkudzu</code> library, and
<code>/etc/sysconfig/hwconf</code> hardware listing are all deprecated,
and will be removed in a future release of Fedora Core. Applications
which need to probe for available hardware should be ported to use the
HAL library. More information on HAL is available at <ulink
url='http://freedesktop.org/wiki/Software/hal'>http://freedesktop.org/wiki/Software/hal</ulink>.
</para>
</section>
<section>
<title>No automatic fstab editing for removable media</title>
<para>
The <code>fstab-sync</code> facility has been removed. In Fedora Core ,
the <code>fstab-sync</code> program is removed in favor of desktop
specific solutions for mounting removable media. Entries for hotplug
devices or inserted media are no longer automatically added to the
<code>/etc/fstab</code> file. Command-line users may migrate to
<code>gnome-mount</code>, which provides similar functionality.
</para>
</section>
<section>
<title>Mounting of Fixed Disks in Gnome and KDE</title>
<para>
As part of the changes to the mounting infrastructure, the desktop's
automatic mountable devices detection now includes policy definitions
that ignore all fixed disk devices from. This was done to increase
security on multi-user systems. People on multi-user systems who want to
make changes to disk mounting that could impact the multi-user
environment are advised to understand the implications of the default
HAL policy decisions and to review the HAL policy files in
<code>/usr/share/hal/fdi/policy/</code>.
</para>
<para>
If you are on a single-user system and would like to recover the
functionality to mount fixed disk items such as IDE partitions from the
desktop, you can modify the default HAL policy. To enable deskop
mounting for all fixed disks:
</para>
<screen>
su -c 'mv /usr/share/hal/fdi/policy/10osvendor/99-redhat-storage-policy-\
fixed-drives.fdi /root/'
su -c '/sbin/service haldaemon restart'
</screen>
<para>
If you need more fine-grained control and only want to expose
certain fixed disks for desktop mounting, read over how to
create additional HAL policy to selectively ignore/allow fixed
disk devices.
</para>
</section>
<section>
<title>GnuCash</title>
<para>
The PostgreSQL backend for
<emphasis role='strong'>GnuCash</emphasis> has been removed, as
it is unmaintained upstream, does not support the full set of
<emphasis role='strong'>GnuCash</emphasis> features, and can
lead to crashes. Users who use the PostgreSQL backend should
load their data and save it as an XML file
<emphasis role='strong'>before</emphasis> upgrading
<emphasis role='strong'>GnuCash</emphasis>.
</para>
</section>
<section>
<title>Mozilla</title>
<para>
The <emphasis role='strong'>Mozilla</emphasis> application suite is
deprecated. It is shipped in Fedora Core and applications can expect to
build against <code>mozilla-devel</code>, however it will be removed in
a future release of Fedora Core.
</para>
</section>
<section>
<title>Booting without initrd</title>
<para>
Booting Fedora Core without the use of an initrd is deprecated.
Support for booting the system without an initrd may be removed
in future releases of Fedora Core.
</para>
</section>
<section>
<title>libstc++ preview</title>
<para>
The <code>libstdc++so7</code> package has been added. This package
contains a preview of the GNU Standard C++ Library from
<code>libstdcxx_so_7-branch</code>. It is considered experimental and
unsupported. Do not build any production software against it, as its ABI
and so-version will change in future upgrades. To build software using
this library, invoke <code>g++-libstdc++so_7</code> instead of
<code>g++</code>.
</para>
</section>
<section>
<title>LinuxThreads support removed</title>
<para>
The LinuxThreads library is no longer available. LinuxThreads
was deprecated in Fedora Core 4 and is no longer available in
this release. The Native POSIX Threading Library (NPTL), which
has been the default threading library since Red Hat Linux 9,
has replaced LinuxThreads completely.
</para>
</section>
</section>
</article>
--- NEW FILE Printing.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Printing</title>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/rightsidebar/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject>
REMOVE ME Before Publishing - Beat Comment
</para>
</td>
</tr>
<tr>
<td>
<para>
This page is a stub for content. If you have a contribution
for this release notes beat for the test release of Fedora
Core, add it to this page or create a sub-page.
</para>
</td>
</tr>
<tr>
<td>
<para>
Beat writers: this is where you want to fill in with
instructions about how to post relevant information. Any
questions that come up can be taken to a bugzilla report for
discussion to resolution, or to fedora-docs-list for wider
discussions.
</para>
</td>
</tr>
</table>
</section>
</article>
--- NEW FILE ProjectOverview.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ProjectOverview">
<title>About the Fedora Project</title>
<para>
The goal of the Fedora Project is to work with the Linux community
to build a complete, general-purpose operating system exclusively
from open source software. Development is done in a public forum.
The project produces time-based releases of Fedora Core
approximately 2-3 times a year, with a public release schedule
available at
<ulink url='http://fedora.redhat.com/About/schedule/'>http://fedora.redhat.com/About/schedule/</ulink>.
The Red Hat engineering team continues to participate in building
Fedora Core and invites and encourages more outside participation
than was possible in the past. By using this more open process, we
hope to provide an operating system more in line with the ideals
of free software and more appealing to the open source community.
</para>
<para>
For more information, refer to the Fedora Project website:
</para>
<para>
<ulink url='http://fedora.redhat.com/'>http://fedora.redhat.com/</ulink>
</para>
<para>
The Fedora Project is driven by the individuals that contribute to
it. As a tester, developer, documenter or translator, you can make
a difference. See
<ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>
for details.
</para>
<para>
This page explains the channels of communication for Fedora users
and contributors:
</para>
<para>
<ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>.
</para>
<para>
In addition to the website, the following mailing lists are
available:
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='mailto:fedora-list at redhat.com'>fedora-list at redhat.com</ulink>
— For users of Fedora Core releases
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-test-list at redhat.com'>fedora-test-list at redhat.com</ulink>
— For testers of Fedora Core test releases
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-devel-list at redhat.com'>fedora-devel-list at redhat.com</ulink>
— For developers, developers, developers
</para>
</listitem>
<listitem>
<para>
<ulink url='mailto:fedora-docs-list at redhat.com'>fedora-docs-list at redhat.com</ulink>
— For participants of the Documentation Project
</para>
</listitem>
</itemizedlist>
<para>
To subscribe to any of these lists, send an email with the word
"subscribe" in the subject to
<emphasis><listname>-request</emphasis>, where
<emphasis><listname></emphasis> is one of the above list names.
</para>
<para>
Alternately, you can subscribe to Fedora mailing lists through the
Web interface:
</para>
<para>
<ulink url='http://www.redhat.com/mailman/listinfo/'>http://www.redhat.com/mailman/listinfo/</ulink>
</para>
<para>
The Fedora Project also uses several IRC (Internet Relay Chat)
channels. IRC is a real-time, text-based form of communication,
similar to Instant Messaging. With it, you may have conversations
with multiple people in an open channel, or chat with someone
privately one-on-one.
</para>
<para>
To talk with other Fedora Project participants via IRC, access the
Freenode IRC network. Refer to the Freenode website
(<ulink url='http://www.freenode.net/'>http://www.freenode.net/</ulink>)
for more information.
</para>
<para>
Fedora Project participants frequent the <code>#fedora</code> channel on
the Freenode network, whilst Fedora Project developers may often be found
on the <code>#fedora-devel</code> channel. Some of the larger projects may
have their own channels as well; this information may be found on the
webpage for the project, and at <ulink
url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>.
</para>
<para>
In order to talk on the <code>#fedora</code> channel, you will need to
register your nickname, or <emphasis>nick</emphasis>. Instructions are
given when you <code>/join</code> the channel.
</para>
<note>
<title>IRC Channels</title>
<para>
The Fedora Project or Red Hat have no control over the Fedora Project
IRC channels or their content.
</para>
</note>
</section>
</article>
***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES.xml'
--- NEW FILE Samba.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Samba">
<title>Samba (Windows Compatibility)</title>
<para>
This section contains information related to Samba, the suite of
software Fedora uses to interact with Microsoft Windows systems.
</para>
<section>
<title>Windows Network Browsing</title>
<para>
Fedora can now browse Windows shares, a feature known as SMB browsing.
In releases prior to Fedora Core 5, the firewall prevented the proper
function of SMB browsing. With the addition of the
<code>ip_conntrack_netbios_ns</code> kernel module to the 2.6.14 kernel,
and corresponding enhancements to <emphasis
role='strong'>system-config-securitylevel</emphasis>, the firewall now
properly handles SMB broadcasts and permits network browsing.
</para>
</section>
</section>
</article>
--- NEW FILE Security.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Security">
<title>Security</title>
<para>
This section highlights various security items from Fedora Core.
</para>
<section>
<title>General Information</title>
<para>
A general introduction to the many proactive security features
in Fedora, current status and policies is available at
<ulink url='http://fedoraproject.org/wiki/Security'>http://fedoraproject.org/wiki/Security</ulink>.
</para>
</section>
<section>
<title>What's New</title>
<section>
<title>PAM module Deprecation</title>
<para>
<code>Pam_stack</code> is deprecated in this release. Linux-PAM 0.78
and later contains the <code>include</code> directive which obsoletes
the <code>pam_stack</code> module. <code>pam_stack</code> module usage
is logged with a deprecation warning. It might be removed in a future
release. It must not be used in individual service configurations
anymore. All packages in Fedora Core using PAM were modified so they
do not use it.
</para>
<tip>
<title>Upgrading and PAM Stacks</title>
<para>
When a system is upgraded from previous Fedora Core releases and the
system admininstrator previously modified some service
configurations, those modified configuration files are
<emphasis>not</emphasis> replaced when new packages are installed.
Instead, the new configuration files are created as
<code>.rpmnew</code> files. Such service configurations must be
fixed so the <code>pam_stack</code> module is not used. Refer to the
<code>.rpmnew</code> files for the actual changes needed.
</para>
<screen>
diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew
</screen>
</tip>
<para>
The following example shows the <code>/etc/pam.d/login</code>
configuration file in its original form using <code>pam_stack</code>,
and then revised with the <code>include</code> directive.
</para>
<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
</screen>
<screen>
#%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>
<title>Buffer Overflow detection and variable reordering</title>
<para>
All of the software in Fedora Core and Extras software repository for
this release is compiled using a security feature called a
<emphasis>stack protector</emphasis>. This was using the compiler
option <code>-fstack-protector</code>, which places a canary value on
the stack of functions containing a local character array. Before
returning from a protected function, the canary value is verified. If
there was a buffer overflow, the canary will no longer match the
expected value, aborting the program. The canary value is random each
time the application is started, making remote exploitation very
difficult. The stack protector feature does not protect against
heap-based buffer overflows.
</para>
<para>
This is a security feature written by Red Hat developers (<ulink
url='http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html'>http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01193.html</ulink>),
reimplementing the IBM ProPolice/SSP feature. For more information
about ProPolice/SSP, refer to <ulink
url='http://www.research.ibm.com/trl/projects/security/ssp/'>http://www.research.ibm.com/trl/projects/security/ssp/</ulink>.
This feature is available as part of the GCC 4.1 compiler used in
Fedora Core 5.
</para>
<para>
The <code>FORTIFY_SOURCE</code> security feature for <code>gcc</code>
and <code>glibc</code> introduced in Fedora Core 4 remains available.
For more information about security features in Fedora, refer to
<ulink
url='http://fedoraproject.org/wiki/Security/Features'>http://fedoraproject.org/wiki/Security/Features</ulink>.
</para>
</section>
</section>
</section>
</article>
--- NEW FILE SecuritySELinux.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-SecuritySELinux">
<title>SELinux</title>
<para>
The new SELinux project pages have troubleshooting tips,
explanations, and pointers to documentation and references. Some
useful links include the following:
</para>
<itemizedlist>
<listitem>
<para>
New SELinux project pages:
<ulink url='http://fedoraproject.org/wiki/SELinux'>http://fedoraproject.org/wiki/SELinux</ulink>
</para>
</listitem>
<listitem>
<para>
Troubleshooting tips:
<ulink url='http://fedoraproject.org/wiki/SELinux/Troubleshooting'>http://fedoraproject.org/wiki/SELinux/Troubleshooting</ulink>
</para>
</listitem>
<listitem>
<para>
Frequently Asked Questions:
<ulink url='http://fedora.redhat.com/docs/selinux-faq/'>http://fedora.redhat.com/docs/selinux-faq/</ulink>
</para>
</listitem>
<listitem>
<para>
Listing of SELinux commands:
<ulink url='http://fedoraproject.org/wiki/SELinux/Commands'>http://fedoraproject.org/wiki/SELinux/Commands</ulink>
</para>
</listitem>
<listitem>
<para>
Details of confined domains:
<ulink url='http://fedoraproject.org/wiki/SELinux/Domains'>http://fedoraproject.org/wiki/SELinux/Domains</ulink>
</para>
</listitem>
</itemizedlist>
<section>
<title>Multi Category Security (MCS)</title>
<para>
MCS is a general-use implementation of the more stringent Multilevel
Security (MLS). MCS is an enhancement to SELinux to allow users to label
files with <emphasis>categories</emphasis>. Categories might include
<code>Company_Confidential</code>, <code>CEO_EYES_ONLY</code>, or
<code>Sysadmin_Passwords</code>. For more information about MCS, refer
to <ulink
url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>,
an article by the author of MCS.
</para>
<section>
<title>Multilevel Security (MLS)</title>
<para>
MLS is a specific Mandatory Access Control (MAC) scheme that labels
processes and objects with special security levels. For example, an
object such as a document file can have the security level of <code>{
Secret, ProjectMeta }</code>, where <code>Secret</code> is the
sensitivity level, and <code>ProjectMeta</code> is the category. For
more information about MLS, refer to <ulink
url='http://james-morris.livejournal.com/5020.html'>http://james-morris.livejournal.com/5020.html</ulink>.
</para>
</section>
</section>
</section>
</article>
--- NEW FILE ServerTools.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-ServerTools">
<title>Server Tools</title>
<para>
This section highlights changes and additions to the various GUI
server and system configuration tools in Fedora Core.
</para>
<section>
<title>system-config-printer</title>
<section>
<title>SMB Browsing Outside Local Network</title>
<para>
You can now browse for Samba print shares across subnets. If you
specify at least one WINS server in <code>/etc/samba/smb.conf</code>,
the first address is used when browsing.
</para>
</section>
<section>
<title>Kerberos Support for SMB Printers</title>
<para>
The <emphasis role='strong'>system-config-printer</emphasis>
application supports Kerberos authentication when adding a new SMB
printer. To add the printer, the user must possess a valid Kerberos
ticket and launch the printer configuration tool. Select
<emphasis>System > Administration > Printing</emphasis>
from the main menu, or use the following command:
</para>
<screen>
su -c 'system-config-printer'
</screen>
<para>
No username and password is stored in
<code>/etc/cups/printers.conf</code>. Printing is still possible if
the SMB print queue permits anonymous printing.
</para>
</section>
</section>
<section>
<title>system-config-securitylevel</title>
<section>
<title>Trusted Service Additions</title>
<para>
Samba is now listed in the <emphasis>Trusted services</emphasis> list.
To permit the firewall to pass SMB traffic, enable this option.
</para>
</section>
<section>
<title>Port Ranges</title>
<para>
When you define <emphasis>Other Ports</emphasis> in the <emphasis
role='strong'>system-config-securitylevel</emphasis> tool, you may
now specify port ranges. For example, if you specify
<code>6881-6999:tcp</code>, the following line is added to
<code>/etc/sysconfig/iptables</code>:
</para>
<screen>
A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 \
-j ACCEPT
</screen>
</section>
</section>
</section>
</article>
--- NEW FILE SystemDaemons.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-SystemDaemons">
<title>System Daemons</title>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/rightsidebar/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject>
REMOVE ME Before Publishing - Beat Comment
</para>
</td>
</tr>
<tr>
<td>
<para>
This page is a stub for content. If you have a contribution
for this release notes beat for the test release of Fedora
Core, add it to this page or create a sub-page.
</para>
</td>
</tr>
<tr>
<td>
<para>
Beat writers: this is where you want to fill in with
instructions about how to post relevant information. Any
questions that come up can be taken to a bugzilla report for
discussion to resolution, or to fedora-docs-list for wider
discussions.
</para>
</td>
</tr>
</table>
<para></para>
</section>
<section>
<title>System Services</title>
</section>
</article>
--- NEW FILE Virtualization.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Virtualization">
<title>Virtualization</title>
<para>
Virtualization in Fedora Core is based on Xen. Xen 3.0 is
integrated within Fedora Core 5 in the installer. Refer to
<ulink url='http://fedoraproject.org/wiki/Tools/Xen'>http://fedoraproject.org/wiki/Tools/Xen</ulink>
for more information about Xen.
</para>
<section>
<title>Types of Virtualization</title>
<para>
There are several types of virtualization: full virtualization,
paravirtualization, and single kernel image virtualization.
Under Fedora Core using Xen 3.0, paravirtualization is the most
common type. With VM hardware, it is also possible to implement
full virtualization.
</para>
<section>
<title>Benefits of Paravirtualization</title>
<itemizedlist>
<listitem>
<para>
Allows low overhead virtualization of system resources.
</para>
</listitem>
<listitem>
<para>
Can provide direct hardware access in special cases (e.g.,
dedicated NICs for each guest OS).
</para>
</listitem>
<listitem>
<para>
Allows hypervisor-assisted security mechanisms for guest
OS.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Requirements of Paravirtualization</title>
<itemizedlist>
<listitem>
<para>
A guest OS that has been modified to enabled
paravirtualization
</para>
</listitem>
<listitem>
<para>
Host OS must use GRUB as its bootloader (default with
Fedora Core)
</para>
</listitem>
<listitem>
<para>
Enough hard drive space to hold each guest OS (600MiB-6GiB
per OS)
</para>
</listitem>
<listitem>
<para>
At least 256 MiB of RAM for each guest, plus at least 256 MiB ram
for the host; use more RAM for the guest if you get out of memory
errors or for troubleshooting failed guest installations
</para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Installing Xen, Configuring and Using Xen</title>
<para>
Xen must be installed on the host OS and the host OS must be
booted into the Hypervisor Kernel. Fedora Core 5 includes an
installation program for the guest OS that will use an existing
installation tree of a paravirtualized-enabled OS to access that
OS's existing installation program. Currently, Fedora Core 5 is
the only available paravirtualized-enabled guest OS. Other OSs
can be installed using existing images, but not through the OS's
native installation program.
</para>
<para>
Full instructions can be found here:
<ulink url='http://fedoraproject.org/wiki/FedoraXenQuickstartFC5'>http://fedoraproject.org/wiki/FedoraXenQuickstartFC5</ulink>
</para>
<note>
<title>No PowerPC Support</title>
<para>
Xen is not supported on the PowerPC architecture in Fedora Core 5.
</para>
</note>
</section>
</section>
</article>
--- NEW FILE WebServers.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-WebServers">
<title>Web Servers</title>
<para>
This section contains information on Web-related applications.
</para>
<section>
<title>httpd</title>
<para>
Fedora Core now includes version 2.2 of the Apache HTTP Server. This
release brings a number of improvements over the 2.0 series, including:
</para>
<itemizedlist>
<listitem>
<para>
greatly improved caching modules ( <code>mod_cache</code>,
<code>mod_disk_cache</code>, <code>mod_mem_cache</code> )
</para>
</listitem>
<listitem>
<para>
a new structure for authentication and authorization support,
replacing the security modules provided in previous versions
</para>
</listitem>
<listitem>
<para>
support for proxy load balancing (<code>mod_proxy_balance</code>)
</para>
</listitem>
<listitem>
<para>
large file support for 32-bit platforms (including support for
serving files larger than 2GB)
</para>
</listitem>
<listitem>
<para>
new modules <code>mod_dbd</code> and <code>mod_filter</code>, which
bring SQL database support and enhanced filtering
</para>
<important>
<title>Upgrading and Security Modules</title>
<para>
If you upgrade from a previous version of <code>httpd</code>,
update your server configuration to use the new authentication and
authorization modules. Refer to the page listed below for more
details.
</para>
</important>
</listitem>
</itemizedlist>
<para>
The following changes have been made to the default <code>httpd</code>
configuration:
</para>
<itemizedlist>
<listitem>
<para>
The <code>mod_cern_meta</code> and <code>mod_asis</code> modules are
no longer loaded by default.
</para>
</listitem>
<listitem>
<para>
The <code>mod_ext_filter</code> module is now loaded by default.
</para>
<important>
<title>Third-party Modules</title>
<para>
Any third-party modules compiled for <code>httpd</code> 2.0 must
be rebuilt for <code>httpd</code> 2.2.
</para>
</important>
</listitem>
</itemizedlist>
<para>
The complete list of new features is available at <ulink
url='http://httpd.apache.org/docs/2.2/new_features_2_2.html'>http://httpd.apache.org/docs/2.2/new_features_2_2.html</ulink>
</para>
<para>
For more information on upgrading existing installations, refer to
<ulink
url='http://httpd.apache.org/docs/2.2/upgrading.html'>http://httpd.apache.org/docs/2.2/upgrading.html</ulink>.
</para>
</section>
<section>
<title>php</title>
<para>
Version 5.1 of PHP is now included in Fedora Core. This release brings a
number of improvements since PHP 5.0, including:
</para>
<itemizedlist>
<listitem>
<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>
<code>date</code>, <code>hash</code>, and <code>Reflection</code>
(built-in with the <code>php</code> package)
</para>
</listitem>
<listitem>
<para>
<code>pdo</code> and <code>pdo_psqlite</code> (in the
<code>php-pdo</code> package
</para>
</listitem>
<listitem>
<para>
<code>pdo_mysql</code> (in the <code>php-mysql</code> package)
</para>
</listitem>
<listitem>
<para>
<code>pdo_pgsql</code> (in the <code>php-pgsql</code> package)
</para>
</listitem>
<listitem>
<para>
<code>pdo_odbc</code> (in the <code>php-odbc</code> package)
</para>
</listitem>
<listitem>
<para>
<code>xmlreader</code> and <code>xmlwriter</code> (in the
<code>php-xml</code> package)
</para>
</listitem>
</itemizedlist>
<para>
The following extension modules are no longer built:
</para>
<itemizedlist>
<listitem>
<para>
<code>dbx</code>
</para>
</listitem>
<listitem>
<para>
<code>dio</code>
</para>
</listitem>
<listitem>
<para>
<code>yp</code>
</para>
</listitem>
</itemizedlist>
<section>
<title>The PEAR framework</title>
<para>
The PEAR framework is now packaged in the <code>php-pear</code>
package. Only the following PEAR components are included in Fedora
Core:
</para>
<itemizedlist>
<listitem>
<para>
<code>Archive_Tar</code>
</para>
</listitem>
<listitem>
<para>
<code>Console_Getopt</code>
</para>
</listitem>
<listitem>
<para>
<code>XML_RPC</code>
</para>
</listitem>
</itemizedlist>
<para>
Additional components may be packaged in Fedora Extras.
</para>
</section>
</section>
</section>
</article>
--- NEW FILE Welcome.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Welcome">
<title>Welcome to Fedora Core</title>
<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>
to view the latest release notes for Fedora Core 5.
</para>
</tip>
<para>
You can help the Fedora Project community continue to improve
Fedora if you file bug reports and enhancement requests. Refer to
<ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>
for more information about bugs. Thank you for your participation.
</para>
<para>
To find out more general information about Fedora, refer to the
following Web pages:
</para>
<itemizedlist>
<listitem>
<para>
Fedora Overview
(<ulink url='http://fedoraproject.org/wiki/Overview'>http://fedoraproject.org/wiki/Overview</ulink>)
</para>
</listitem>
<listitem>
<para>
Fedora FAQ
(<ulink url='http://fedoraproject.org/wiki/FAQ'>http://fedoraproject.org/wiki/FAQ</ulink>)
</para>
</listitem>
<listitem>
<para>
Help and Support
(<ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>)
</para>
</listitem>
<listitem>
<para>
Participate in the Fedora Project
(<ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink>)
</para>
</listitem>
<listitem>
<para>
About the Fedora Project
(<ulink url='http://fedora.redhat.com/About/'>http://fedora.redhat.com/About/</ulink>)
</para>
</listitem>
</itemizedlist>
</section>
</article>
--- NEW FILE Xorg.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section id="sn-Xorg">
<title>X Window System (Graphics)</title>
<para>
This section contains information related to the X Window System
implementation provided with Fedora.
</para>
<section>
<title>xorg-x11</title>
<para>
X.org X11 is an open source implementation of the X Window System. It
provides the basic low-level functionality upon which full-fledged
graphical user interfaces (GUIs) such as GNOME and KDE are designed. For
more information about X.org, refer to <ulink
url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>.
</para>
<para>
You may use <emphasis>System > Administration > Display</emphasis> or
<emphasis role='strong'>system-config-display</emphasis> to configure
the settings. The configuration file for X.org is located in
<code>/etc/X11/xorg.conf</code>.
</para>
<para>
X.org X11R7 is the first modular release of X.org, which, among several
other benefits, promotes faster updates and helps programmers rapidly
develop and release specific components. More information on the current
status of the X.org modularization effort in Fedora is available at
<ulink
url='http://fedoraproject.org/wiki/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>.
</para>
</section>
<section>
<title>X.org X11R7 End-User Notes</title>
<caution>
<title>Installing Third Party Drivers</title>
<para>
Before you install any third party drivers from any vendor, including
ATI or nVidia, please read <ulink
url='http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers'>http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers</ulink>.
</para>
</caution>
<para>
The <code>xorg-x11-server-Xorg</code> package install scripts
automatically remove the <code>RgbPath</code> line from the
<code>xorg.conf</code> file if it is present. You may need to
reconfigure your keyboard differently from what you are used to. You are
encouraged to subscribe to the upstream <ulink
url='mailto:xorg at freedesktop.org'>xorg at freedesktop.org</ulink> mailing
list if you do need assistance reconfiguring your keyboard.
</para>
</section>
<section>
<title>X.org X11R7 Developer Overview</title>
<para>
The following list includes some of the more visible changes for
developers in X11R7:
</para>
<itemizedlist>
<listitem>
<para>
The entire buildsystem has changed from <code>imake</code> to the
GNU <code>autotools</code> collection.
</para>
</listitem>
<listitem>
<para>
Libraries now install <code>pkgconfig</code> <code>*.pc</code>
files, which should now always be used by software that depends on
these libraries, instead of hard coding paths to them in
<code>/usr/X11R6/lib </code> or elsewhere.
</para>
</listitem>
<listitem>
<para>
Everything is now installed directly into <code>/usr</code> instead
of <code>/usr/X11R6</code>. All software that hard codes paths to
anything in <code>/usr/X11R6</code> must now be changed, preferably
to dynamically detect the proper location of the object. Developers
are <emphasis role='strong'>strongly</emphasis> advised against
hard-coding the new X11R7 default paths.
</para>
</listitem>
<listitem>
<para>
Every library has its own private source RPM package, which creates
a runtime binary subpackage and a <code>-devel</code> subpackage.
</para>
</listitem>
</itemizedlist>
</section>
<section>
<title>X.org X11R7 Developer Notes</title>
<para>
This section includes a summary of issues of note for developers and
packagers, and suggestions on how to fix them where possible.
</para>
<section>
<title>The /usr/X11R6/ Directory Hierarchy</title>
<para>
X11R7 files install into <code>/usr</code> directly now, and no longer
use the <code>/usr/X11R6/</code> hierarchy. Applications that rely on
files being present at fixed paths under <code>/usr/X11R6/</code>,
either at compile time or run time, must be updated. They should now
use the system <code>PATH</code>, or some other mechanism to
dynamically determine where the files reside, or alternatively to hard
code the new locations, possibly with fallbacks.
</para>
</section>
<section>
<title>Imake</title>
<para>
The <code>imake</code> xutility is no longer used to build the X
Window System, and is now officially deprecated. X11R7 includes
<code>imake</code>, <code>xmkmf</code>, and other build utilities
previously supplied by the X Window System. X.Org highly recommends,
however, that people migrate from <code>imake</code> to use GNU
<code>autotools</code> and <code>pkg-config</code>. Support for
<code>imake</code> may be removed in a future X Window System release,
so developers are <emphasis role='strong'>strongly</emphasis>
encouraged to transition away from it, and not use it for any new
software projects.
</para>
</section>
<section>
<title>The Systemwide app-defaults/ Directory</title>
<para>
The system <code>app-defaults/</code> directory for X resources is now
<code>%{_datadir}/X11/app-defaults</code>, which expands to
<code>/usr/share/X11/app-defaults/</code> on Fedora Core and for
future Red Hat Enterprise Linux systems.
</para>
</section>
<section>
<title>Correct Package Dependencies</title>
<para>
Any software package that previously used <code>Build Requires:
(XFree86-devel|xorg-x11-devel)</code> to satisfy build dependencies
must now individually list each library dependency. The preferred and
recommended method is to use <emphasis>virtual</emphasis> build
dependencies instead of hard coding the library package names of the
<code>xorg</code> implementation. This means you should use
<code>Build Requires: libXft-devel</code> instead of <code>Build
Requires: xorg-x11-Xft-devel</code>. If your software truly does
depend on the X.Org X11 implementation of a specific library, and
there is no other clean or safe way to state the dependency, then use
the <code>xorg-x11-devel</code> form. If you use the virtual
provides/requires mechanism, you will avoid inconvenience if the
libraries move to another location in the future.
</para>
</section>
<section>
<title>xft-config</title>
<para>
Modular X now uses GNU <code>autotools</code> and
<code>pkg-config</code> for its buildsystem configuration and
execution. The <code>xft-config</code> utility has been deprecated for
some time, and <code>pkgconfig</code> <code>*.pc</code> files have
been provided for most of this time. Applications that previously used
<code>xft-config</code> to obtain the <code>Cflags</code> or
<code>libs</code> build options must now be updated to use
<code>pkg-config</code>.
</para>
</section>
</section>
</section>
</article>
- Previous message (by thread): release-notes/devel/css content.css, NONE, 1.1 docbook.css, NONE, 1.1 layout.css, NONE, 1.1 print.css, NONE, 1.1
- Next message (by thread): release-notes/devel/figs Fedora_Desktop.eps, NONE, 1.1 Fedora_Desktop.png, NONE, 1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list