release-notes/en ArchSpecific-en.xml, NONE, 1.1 ArchSpecificPPC-en.xml, NONE, 1.1 ArchSpecificx86-en.xml, NONE, 1.1 ArchSpecificx86_64-en.xml, NONE, 1.1 BackwardsCompatibility-en.xml, NONE, 1.1 Colophon-en.xml, NONE, 1.1 DatabaseServers-en.xml, NONE, 1.1 Desktop-en.xml, NONE, 1.1 DevelTools-en.xml, NONE, 1.1 DevelToolsGCC-en.xml, NONE, 1.1 Entertainment-en.xml, NONE, 1.1 Feedback-en.xml, NONE, 1.1 FileServers-en.xml, NONE, 1.1 FileSystems-en.xml, NONE, 1.1 I18n-en.xml, NONE, 1.1 Installer-en.xml, NONE, 1.1 Java-en.xml, NONE, 1.1 Kernel-en.xml, NONE, 1.1 Legacy-en.xml, NONE, 1.1 Multimedia-en.xml, NONE, 1.1 Networking-en.xml, NONE, 1.1 OverView-en.xml, NONE, 1.1 PackageChanges-en.xml, NONE, 1.1 PackageNotes-en.xml, NONE, 1.1 PackageNotesJava-en.xml, NONE, 1.1 Printing-en.xml, NONE, 1.1 ProjectOverview-en.xml, NONE, 1.1 RELEASE-NOTES-en.xml, NONE, 1.1 Samba-en.xml, NONE, 1.1 Security-en.xml, NONE, 1.1 SecuritySELinux-en.xml, NONE, 1.1 ServerTools-en.xml, NONE, 1.1 SystemDaemons-en.xml, NONE, 1.1 WebServers-en.xml, NONE, 1.1 Welcome-en! .xml,NONE,1.1 Xorg-en.xml,NONE,1.1 fdp-info-en.xml,NONE,1.1
Karsten Wade (kwade)
fedora-docs-commits at redhat.com
Mon Feb 6 20:35:17 UTC 2006
- Previous message (by thread): release-notes ArchSpecific-en.xml, 1.2, 1.3 ArchSpecificPPC-en.xml, 1.3, 1.4 ArchSpecificx86-en.xml, 1.2, 1.3 ArchSpecificx86_64-en.xml, 1.2, 1.3 BackwardsCompatibility-en.xml, 1.1, 1.2 Colophon-en.xml, 1.2, 1.3 DatabaseServers-en.xml, 1.1, 1.2 Desktop-en.xml, 1.3, 1.4 Entertainment-en.xml, 1.1, 1.2 Feedback-en.xml, 1.1, 1.2 FileServers-en.xml, 1.2, 1.3 FileSystems-en.xml, 1.1, 1.2 I18n-en.xml, 1.2, 1.3 Installer-en.xml, 1.2, 1.3 Kernel-en.xml, 1.3, 1.4 Legacy-en.xml, 1.3, 1.4 Makefile, 1.17, 1.18 Multimedia-en.xml, 1.2, 1.3 Networking-en.xml, 1.1, 1.2 OverView-en.xml, 1.6, 1.7 PackageChanges-en.xml, 1.3, 1.4 PackageNotes-en.xml, 1.2, 1.3 PackageNotesJava-en.xml, 1.1, 1.2 Printing-en.xml, 1.1, 1.2 ProjectOverview-en.xml, 1.2, 1.3 RELEASE-NOTES-en.xml, 1.20, 1.21 Samba-en.xml, 1.2, 1.3 Security-en.xml, 1.2, 1.3 SecuritySELinux-en.xml, 1.2, 1.3 ServerTools-en.xml, 1.2, 1.3 SystemDaemons-en.xml, 1.2, 1.3 WebServers-en.xml, 1.2, 1.3 Welcome-en.xml, 1.5, 1.6 Xorg-en.xml, 1.2, 1.3
- Next message (by thread): release-notes/it fdp-info-it.xml,NONE,1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: kwade
Update of /cvs/docs/release-notes/en
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv27624/en
Added Files:
ArchSpecific-en.xml ArchSpecificPPC-en.xml
ArchSpecificx86-en.xml ArchSpecificx86_64-en.xml
BackwardsCompatibility-en.xml Colophon-en.xml
DatabaseServers-en.xml Desktop-en.xml DevelTools-en.xml
DevelToolsGCC-en.xml Entertainment-en.xml Feedback-en.xml
FileServers-en.xml FileSystems-en.xml I18n-en.xml
Installer-en.xml Java-en.xml Kernel-en.xml Legacy-en.xml
Multimedia-en.xml Networking-en.xml OverView-en.xml
PackageChanges-en.xml PackageNotes-en.xml
PackageNotesJava-en.xml Printing-en.xml ProjectOverview-en.xml
RELEASE-NOTES-en.xml Samba-en.xml Security-en.xml
SecuritySELinux-en.xml ServerTools-en.xml SystemDaemons-en.xml
WebServers-en.xml Welcome-en.xml Xorg-en.xml fdp-info-en.xml
Log Message:
Moving content into by-language sub-directories.
--- NEW FILE ArchSpecific-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/ArchSpecific</title>
<para>This section provides notes that are specific to the supported hardware architectures of Fedora Core. </para>
<para>
</para>
<para>
</para>
<para>
</para>
</section>
</article>
--- NEW FILE ArchSpecificPPC-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>PPC Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the PPC hardware platform. </para>
<section>
<title>PPC Hardware Requirements</title>
<para>This section lists the minimum PowerPC (PPC) hardware needed to install Fedora Core 4. </para>
<itemizedlist>
<listitem>
<para> Minimum: PowerPC G3 / POWER4 </para>
</listitem>
<listitem>
<para> Fedora Core 5 supports only the “New World†generation of Apple Power Macintosh, shipped circa 1999 onwards. </para>
</listitem>
<listitem>
<para> Fedora Core also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines. </para>
</listitem>
<listitem>
<para> Recommended for text-mode: 233 MHz G3 or better, 64MiB RAM. </para>
</listitem>
<listitem>
<para> Recommended for graphical: 400 MHz G3 or better, 128MiB RAM. </para>
</listitem>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
<para>This section lists the disk space required to install Fedora Core . </para>
<para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
<para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
<para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
</section>
<section>
<title>PPC Installation Notes</title>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject> Currently FC5 Test Release CD 1 and Rescue ISOs do not boot on Mac hardware. See below on booting using boot.iso. </para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The DVD or first CD of the installation set of Fedora Core is set to be bootable on supported hardware. In addition, a bootable CD images can be found in the images/ directory of the DVD or first CD. These will behave differently according to the hardware: </para>
</listitem>
<listitem>
<para> Apple Macintosh </para>
<itemizedlist>
<listitem>
<para>The bootloader should automatically boot the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the apmud package, which is in Fedora Extras. Fedora Extras for Fedora Core is configured by default for yum. Following installation, apmud can be installed by running yum install apmud. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> 64-bit IBM eServer pSeries (POWER4/POWER5) </para>
<itemizedlist>
<listitem>
<para>After using Open<emphasis role='strong'/>Firmware to boot the CD, the bootloader (yaboot) should automatically boot the 64-bit installer. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> 32-bit CHRP (IBM RS/6000 and others) </para>
<itemizedlist>
<listitem>
<para>After using Open<emphasis role='strong'/>Firmware to boot the CD, select the 'linux32' boot image at the 'boot:' prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Genesi Pegasos II </para>
<itemizedlist>
<listitem>
<para>At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the Open<emphasis role='strong'/>Firmware prompt, enter the command: </para>
<itemizedlist>
<listitem>
<screen>boot cd: /images/netboot/ppc32.img </screen>
</listitem>
</itemizedlist>
<para>You also need to configure Open<emphasis role='strong'/>Firmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, you need to set the boot-device and boot-file environment variables appropriately. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Network booting </para>
<itemizedlist>
<listitem>
<para>There are combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the install tree. These are intended for network booting with TFTP, but can be used in many ways. </para>
<para>yaboot supports tftp booting for IBM eServer pSeries and Apple Macintosh, the use of yaboot is encouraged over the netboot images. </para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE ArchSpecificx86-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>x86 Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the x86 hardware platform. </para>
<section>
<title>x86 Hardware Requirements</title>
<para>The following information represents the minimum hardware requirements necessary to successfully install Fedora Core . </para>
<para>The compatibility/availability of other hardware components (such as video and network cards) may be required for specific installation modes and/or post-installation usage. </para>
<section>
<title>CPU Requirements</title>
<para>This section lists the CPU specifications required by Fedora Core . </para>
<para>The following CPU specifications are stated in terms of Intel processors. Other processors (notably, offerings from AMD, Cyrix, and VIA) that are compatible with and equivalent to the following Intel processors may also be used with Fedora Core. </para>
<itemizedlist>
<listitem>
<para> Minimum: Pentium-class — Fedora Core is optimized for Pentium 4 CPUs, but also supports earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III, and including AMD and VIA variants). This approach has been taken because Pentium-class optimizations actually result in reduced performance for non-Pentium-class processors, and Pentium 4 scheduling is sufficiently different (while making up the bulk of today's processors) to warrant this change. </para>
</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>
</itemizedlist>
<section>
<title>Hard Disk Space Requirements</title>
<para>This section lists the disk space required to install Fedora Core . </para>
<para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
<para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
<para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
</section>
<section>
<title>Memory Requirements</title>
<para>This section lists the memory required to install Fedora Core . </para>
<para>This list is for 32-bit x86 systems: </para>
<itemizedlist>
<listitem>
<para> Minimum for text-mode: 64MB </para>
</listitem>
<listitem>
<para> Minimum for graphical: 192MB </para>
</listitem>
<listitem>
<para> Recommended for graphical: 256MB </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>x86 Installation Notes</title>
<para>Installer package screen selection interface is being redesigned in the Fedora development version. Fedora Core does not provide an option to select the installation type such as Personal Desktop, Workstation, Server and custom. </para>
</section>
</section>
</section>
</article>
--- NEW FILE ArchSpecificx86_64-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>x86_64 Specifics for Fedora</title>
<para>This section covers any specific information you may need to know about Fedora Core and the x86_64 hardware platform. </para>
<section>
<title>x86_64 Hardware Requirements</title>
<para>The following information represents the minimum hardware requirements necessary to successfully install Fedora Core . </para>
<para>The compatibility/availability of other hardware components (such as video and network cards) may be required for specific installation modes and/or post-installation usage. </para>
<section>
<title>Hard Disk Space Requirements</title>
<para>This section lists the disk space required to install Fedora Core . </para>
<para>The disk space requirements listed below represent the disk space taken up by Fedora Core after the installation is complete. However, additional disk space is required during the installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed system. </para>
<para>In practical terms, this means that as little as an additional 90MB can be required for a minimal installation, while as much as an additional 175MB can be required for an "everything" installation. The complete packages can occupy over 7 GB of disk space. </para>
<para>Also, keep in mind that additional space is required for any user data, and at least 5% free space should be maintained for proper system operation. </para>
<section>
<title>Memory Requirements</title>
<para>This section lists the memory required to install Fedora Core . </para>
<para>This list is for 64-bit x86_64 systems: </para>
<itemizedlist>
<listitem>
<para> Minimum for text-mode: 128MB </para>
</listitem>
<listitem>
<para> Minimum for graphical: 256MB </para>
</listitem>
<listitem>
<para> Recommended for graphical: 512MB </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>x86_64 Installation Notes</title>
<para>No differences installing for x86_64. </para>
</section>
</section>
</section>
</article>
--- NEW FILE BackwardsCompatibility-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/BackwardsCompatibility</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
<section>
<title>Backwards Compatibility</title>
<para>Fedora includes several system libraries and software for compatibility with older software. These software are part of the "Legacy Software Development" group which are not installed by default. Users who require this functionality can select this group during installation or run the following the command post-installation. </para>
<screen>yum groupinstall "Legacy Software Development"</screen>
</section>
</section>
</article>
--- NEW FILE Colophon-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Colophon</title>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject> This is a draft, so it is incomplete and imperfect. </para>
</listitem>
</itemizedlist>
<section>
<title>About the Colophon</title>
<para>As we use the term, colophon means: </para>
<itemizedlist>
<listitem>
<para> A way to recognize contributors, while providing accountability. </para>
</listitem>
<listitem>
<para> Explain tools and production methods. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Contributors</title>
<itemizedlist>
<listitem>
<para>
<ulink url='/AndrewMartynov'>AndrewMartynov</ulink> (translator, Russian) </para>
</listitem>
<listitem>
<para>
<ulink url='/AnthonyGreen'>AnthonyGreen</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/BobJensen'>BobJensen</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/DaveMalcolm'>DaveMalcolm</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/DavidWoodhouse'>DavidWoodhouse</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/FrancescoTombolini'>FrancescoTombolini</ulink> (translator, Italian) </para>
</listitem>
<listitem>
<para>
<ulink url='/GavinHenry'>GavinHenry</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/JensPetersen'>JensPetersen</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/JoeOrton'>JoeOrton</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/JoshBressers'>JoshBressers</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/KarstenWade'>KarstenWade</ulink> (beat writer, editor, publisher) </para>
</listitem>
<listitem>
<para>
<ulink url='/LuyaTshimbalanga'>LuyaTshimbalanga</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/PatrickBarnes'>PatrickBarnes</ulink> (beat writer, editor) </para>
</listitem>
<listitem>
<para>
<ulink url='/RahulSundaram'>RahulSundaram</ulink> (beat writer, editor) </para>
</listitem>
<listitem>
<para>
<ulink url='/SekineTatsuo'>SekineTatsuo</ulink> (translator, Japanese) </para>
</listitem>
<listitem>
<para>
<ulink url='/SteveDickson'>SteveDickson</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/StuartElliss'>StuartElliss</ulink> (editor) </para>
</listitem>
<listitem>
<para>
<ulink url='/ThomasGraf'>ThomasGraf</ulink> (beat writer) </para>
</listitem>
<listitem>
<para>
<ulink url='/TommyReynolds'>TommyReynolds</ulink> (tools) </para>
</listitem>
<listitem>
<para>
<ulink url='/YoshinariTakaoka'>YoshinariTakaoka</ulink> (translator, tools) </para>
</listitem>
<listitem>
<para>
<ulink url='/YuanYijun'>YuanYijun</ulink> (translator, Simplified Chinese) </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Production Methods</title>
</section>
</section>
</article>
--- NEW FILE DatabaseServers-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/DatabaseServers</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
</section>
</article>
--- NEW FILE Desktop-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Desktop</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
<section>
<title>Fedora Desktop</title>
<para>GNOME 2.13.2 and KDE 3.5 Release Candidate 2 has been included in Fedora Core 5 test 2. GNOME 2.14 (or a release candidate) is scheduled to be available as part of Fedora Core 5. </para>
<para>The current test release has GNOME 2.12.1, together with some previews of technology from the forthcoming GNOME 2.14. Feedback on these packages is especially appreciated. </para>
<itemizedlist>
<listitem>
<para> gnome-power-manager: GNOME Power Manager is a session daemon for the GNOME desktop environment that makes it easy to manage your laptop or desktop system. It takes advantage of HAL (which provides a hardware abstraction layer) and DBUS ( Inter Process Communication software) written and maintained by Fedora Core developers. </para>
</listitem>
<listitem>
<para> gnome-screensaver: Provides a integrated user interface to screensavers and the lock screen dialog. </para>
</listitem>
<listitem>
<para> memory optimizations in the fontconfig and shared-mime-info packages. These now use shared memory-mapped caches for this data. </para>
</listitem>
</itemizedlist>
<para>GNOME 2.12 has removed the terminal option from the desktop context menu. nautilus-open-terminal in Fedora Extras repository provides a enhanced replacement for those who require it. You can install it using the following command. </para>
<screen>yum install nautilus-open-terminal</screen>
<para>Screensavers except the one providing a blank screen are not installed by default from Fedora Core 4 onwards. Many of the screensavers are found to be offensive or known to abruptly terminate the graphical interface, in particular some of the OpenGL animated ones provided within xscreensaver-gl-extras package. Some of them also provide a unexpected suprise to users. Users who need it can install it using the following command. </para>
<screen>yum install xscreensaver-extras xscreensaver-gl-extras</screen>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject> system-config-mouse configuration utility has been dropped from this release since synaptic and 3 button mouse configuration is being done automatically during installation and serial mice are not formally supported in Fedora Core anymore. </para>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE DevelTools-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Developer Tools</title>
<para>This section covers various developer tools. </para>
<para>
</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 has been 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-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>GCC Compiler Collection</title>
<para>This release of Fedora has been built using GCC 4.1, which is included with the distribution. </para>
<section>
<title>Caveats</title>
<itemizedlist>
<listitem>
<para> GDB 6.1 or newer is needed to debug binaries unless compiled using the <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> A sentinel attribute has been added so that the compiler will now 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 have been brought 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. The <code>-fno-threadsafe-statics</code> can be used by embedded developers to turn off this feature, but ordinary users should never do this. </para>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE Entertainment-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>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>). For a list of other games that are available for installation through <code>yum</code>, open a terminal and enter the following command: </para>
<itemizedlist>
<listitem>
<screen>yum groupinfo "Games and Entertainment"</screen>
</listitem>
</itemizedlist>
<para>For help using <code>yum</code> to install the assorted game packages, refer to the guide available at: </para>
<para>
<ulink url='http://fedora.redhat.com/docs/yum/'>http://fedora.redhat.com/docs/yum/</ulink>
</para>
</section>
</article>
--- NEW FILE Feedback-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Feedback</title>
<para>Thanks for your interest in helping us with the release notes by providing feedback. This section explains how you can give that feedback. </para>
<section>
<title>Release Notes Feedback Procedure</title>
<para>If you feel that these release notes could be improved in some way, you can provide feedback directly to the beat writers. Here are several ways, in order of preference: </para>
<itemizedlist>
<listitem>
<para> Edit content directly at <ulink url='/Docs/Beats'>Docs/Beats</ulink>
</para>
</listitem>
<listitem>
<para> Email <ulink url='mailto:relnotes at fedoraproject.org'>relnotes at fedoraproject.org</ulink>
</para>
</listitem>
<listitem>
<para> Fill out this <ulink url='http://tinyurl.com/8lryk'>pre-filled bug request template</ulink>
</para>
</listitem>
</itemizedlist>
<para>A <ulink url='/DocsProject/ReleaseNotes/Beats'>release note beat</ulink> is an area of the release notes that is the responsibility of one or more content contributors to oversee. </para>
<para>Thank you (in advance) for your feedback! </para>
</section>
</section>
</article>
--- NEW FILE FileServers-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/FileServers</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
<para>
</para>
</section>
<section>
<title>File Servers</title>
<para>This section refers to file transfer and sharing servers. Please refer to the Web Servers and Samba sections for information on HTTP (Web) file transfer and Samba (Windows) file sharing. </para>
<section>
<title>Netatalk (Macintosh Compatibility)</title>
<para>This section contains information related to Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the <ulink url='/AppleTalk'>AppleTalk</ulink> network protocols. </para>
<section>
<title>netatalk</title>
<para>Fedora includes version 2 of Netatalk. </para>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject> Upgrading from Netatalk version 1 to version 2 may result in data loss. </para>
</listitem>
</itemizedlist>
<para>Version 2 of Netatalk uses a different method to store file resource forks from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. </para>
<para>Upgrade information is available directly from the Netatalk site: </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>
</para>
</listitem>
</itemizedlist>
<para>The documentation is also included in the netatalk 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>
</section>
</article>
--- NEW FILE FileSystems-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/FileSystems</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
</section>
</article>
--- NEW FILE I18n-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Internationalization (i18n)</title>
<para>This section includes information related to the support of various languages under Fedora Core. </para>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject> SCIM has replaced IIIMF as the language input framework in Fedora Core in this release. </para>
</listitem>
</itemizedlist>
</section>
</article>
--- NEW FILE Installer-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Installation-Related Notes</title>
<para>This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core in general. </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> If you intend to download the Fedora Core 5 Test 2 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. For example, wget before version 1.9.1-16 in Fedora will exit with a File size limit exceeded error. </para>
</td>
</tr>
<tr>
<td>
<para> Wget 1.9.1-16 and above, curl and ncftpget file downloading tools do not have this limitation, and can successfully download files larger than 2GB. </para>
</td>
</tr>
<tr>
<td>
<para>Bittorrent is another method for downloading large files. For information about obtaining and using the torrent file refer to this website: </para>
</td>
</tr>
<tr>
<td>
<para>
<ulink url='http://torrent.fedoraproject.org/'>http://torrent.fedoraproject.org/</ulink>
</para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</section>
<section>
<title>Installer Notes</title>
<itemizedlist>
<listitem>
<para> The Fedora Core installation program has the ability to test the integrity of the installation media. It works with the CD, DVD, hard drive ISO, and NFS ISO installation methods. Fedora Project recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned CDs). To use this test, type linux mediacheck at the boot: prompt. </para>
<para>The mediacheck function is highly sensitive, and may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files. For best results with the mediacheck, boot with the option: </para>
<itemizedlist>
<listitem>
<screen>linux ide=nodma </screen>
</listitem>
</itemizedlist>
<para>Use the sha1sum utility to verify discs before carrying out an installation. This test accurately identifies discs that are not valid or identical to the ISO image files. </para>
</listitem>
<listitem>
<para> Memory testing may be performed prior to installing Fedora Core by entering memtest86 at the boot: prompt. This causes the Memtest86 standalone memory testing software to run. Memtest86 memory testing continues until the Esc key is pressed. </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use this feature.</para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Fedora Core supports graphical FTP and HTTP installations. However, due to the necessity of containing the installer image in RAM, only systems with more than 128MB of RAM (or systems booted from CD-ROM 1, which contains the installer image) can use the graphical installer. Systems with 128MB or less will continue to use the text-based installer. </para>
</listitem>
</itemizedlist>
<section>
<title>Changes In The Installer</title>
<itemizedlist>
<listitem>
<para> Support of yum for dependancy solver backend has been added and additional repositories are expected to be supported during installation in a future release. </para>
</listitem>
<listitem>
<para> The installer checks the hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropriate in this release. Previous releases installed both the variants and used the appropriate one as default. </para>
</listitem>
<listitem>
<para> Partition setting has been reworked to be more user friendly </para>
</listitem>
<listitem>
<para> Remote logging via syslog is supported in this release. pass syslog=host:port (port is optional) at the boot prompt. </para>
</listitem>
<listitem>
<para> Firewall/SELinux configuration has been moved to the final installation phase called 'firstboot'. </para>
</listitem>
<listitem>
<para> Rendering of html pages is now done using the gtkhtml widget for better capability. </para>
</listitem>
<listitem>
<para> Kickstart has been refactored into its own package - pykickstart - containing parser and writers. As a result of this change validation and extending kickstart is now much easier. </para>
</listitem>
<listitem>
<para> Serial mice is not formally supported in the installer and in Fedora Core anymore. </para>
</listitem>
<listitem>
<para> Full support of dmraid (disabled by default). To enable that feature, add this option to the boot command line: </para>
<itemizedlist>
<listitem>
<screen>dmraid </screen>
</listitem>
</itemizedlist>
<para>For more information, check the <ulink url='/DmraidStatus'>DmraidStatus</ulink> page. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Installation Related Issues</title>
<itemizedlist>
<listitem>
<para> Certain hardware configurations (particularly those with LCD displays) may experience problems while starting the Fedora Core installation program. In these instances, restart the installation, and add the "nofb" option to the boot command line. </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Chinese, Japanese, and Korean graphical installations started using the "nofb" option will start in English, and then switch to the appropriate language once the graphical phase of the installation process begins. </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Some Sony VAIO notebook systems may experience problems installing Fedora Core from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line: </para>
<itemizedlist>
<listitem>
<screen>pci=off ide1=0x180,0x386 </screen>
</listitem>
</itemizedlist>
<para>This option allows the installation to proceed normally; any devices not detected due to the use of this option are configured the first time Fedora Core is booted. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Upgrading Related Issues</title>
<para>Refer to <ulink url='http://fedoraproject.org/wiki/DistributionUpgrades'>http://fedoraproject.org/wiki/DistributionUpgrades</ulink> page for detailedrecommended procedures for upgradation of Fedora. </para>
<para>In general, fresh installations are to be recommended over upgrades, particularly for systems with software from add-on repositories installed. If third party packages are installed on the system, they might not work as expected. If an upgrade is attempted, the following may be helpful. </para>
<itemizedlist>
<listitem>
<para> Before upgrading (or installing), back up the system completely. In particular, preserve <emphasis>/etc</emphasis>, <emphasis>/home</emphasis>, and possibly <emphasis>/opt</emphasis> and <emphasis>/usr/local</emphasis> if customized packages are installed there. Using a multi-boot approach with a "clone" of the old installation on alternate partition[s] as a fall-back might be considered. Creating alternate boot media, such as GRUB floppy would be advisable. </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Note</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Backups of configurations in <emphasis>/etc</emphasis> are also very useful in reconstructing system settings after a fresh install.</para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> After completing the upgrade, run the command: </para>
<itemizedlist>
<listitem>
<screen>rpm -qa --last > RPMS_by_Install_Time.txt </screen>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Inspect the end of the output for packages that pre-date the upgrade and remove/upgrade those from 3rd party repos, or otherwise deal with them as necessary. </para>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE Java-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Java</title>
<para>A Free and open source Java environment is available within this Fedora Core release. </para>
<para>It has three components: GNU Java runtime ("libgcj"), the Eclipse Java compiler ("ecj"), and a set of wrappers and links ("java-gcj-compat") that present the runtime and compiler to the user in the same way as other Java environments are presented. </para>
<para>Several major software such as Openoffice.org Base, Eclipse, Apache Tomcat and several other Java software included in this release is compatible with it </para>
<para>For more information see the FAQ </para>
<para>
<ulink url='http://www.fedoraproject.org/wiki/JavaFAQ'>http://www.fedoraproject.org/wiki/JavaFAQ</ulink>
</para>
<para>Refer to the <ulink url='/Docs/Beats/PackageNotes/Java'>Docs/Beats/PackageNotes/Java</ulink> page for information about Java packages. </para>
</section>
</article>
--- NEW FILE Kernel-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Linux Kernel</title>
<para>This section is for content related to the kernel. If you have a contribution for this release notes beat for Fedora Core, add it to this page or create a sub-page. If you have any questions about what content might be appropriate for this page or if a sub-page is needed, please contact <ulink url='/SamFolkWilliams'>SamFolkWilliams</ulink> or email the Fedora Documentation Project at <code>fedora-docs-list at redhat.com</code>. </para>
<section>
<title>Version</title>
<para>This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include additional patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the so-called <emphasis>vanilla kernel</emphasis> from the kernel.org web site: </para>
<para>
<ulink url='http://www.kernel.org/'>http://www.kernel.org/</ulink>
</para>
<para>You may obtain a list of any such patches by using the command on the Fedora Core package: </para>
<itemizedlist>
<listitem>
<screen>rpm -qpl kernel-<version>.src.rpm</screen>
</listitem>
</itemizedlist>
</section>
<section>
<title>Changelog</title>
<para>The package changelog can be retrieved using the following command </para>
<itemizedlist>
<listitem>
<screen>rpm -q --changelog <kernel-version></screen>
</listitem>
</itemizedlist>
<para>If you need a user friendly version of the changelog, refer to <ulink url='http://wiki.kernelnewbies.org/LinuxChanges'>http://wiki.kernelnewbies.org/LinuxChanges</ulink>. A short and full diff of the kernel is available from <ulink url='http://kernel.org/git'>http://kernel.org/git</ulink>. The Fedora version is based on the Linus tree. </para>
<para>Customisations made for the Fedora version are available from <ulink url='http://cvs.fedora.redhat.com'>http://cvs.fedora.redhat.com</ulink> . </para>
</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 CPU's or processors. Configured sources are available in the <code>kernel-[smp-]devel-<version>.<arch>.rpm</code> package. </para>
</listitem>
<listitem>
<para> Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-hypervisor-devel-<version>.<arch>.rpm</code> package. </para>
</listitem>
<listitem>
<para> Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the <code>kernel-xen-guest-devel-<version>.<arch>.rpm</code> package. </para>
</listitem>
<listitem>
<para> 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>Sources for all kernel flavors may be installed at the same time. The files will be installed into the <code>/usr/src/kernels/<version>[-xen-hypervisor/xen-guest/kdump]-<arch>/</code> tree. Use the command: </para>
<itemizedlist>
<listitem>
<screen>rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-<version>.<arch>.rpm</screen>
</listitem>
</itemizedlist>
<para>as appropriate. </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'>The default kernels in x86_64 architecture provide the SMP capability</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> There is no separate SMP kernel available for this architecture in Fedora Core . </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</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: </para>
<itemizedlist>
<listitem>
<screen>ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux</screen>
</listitem>
</itemizedlist>
</section>
<section>
<title>Preparing for Kernel Development</title>
<para>Fedora Core does not include the kernel-source package provided by older versions. Instead, configured sources are available, as described in this kernel flavors section. </para>
<para>Users that require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. </para>
<para>To create an exploded source tree from this file, perform the following steps: </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>These Instructions Refer to the Currently-running Kernel</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, you must understand that the phrase <version> refers to the kernel version shown by the command: <code>uname -r</code>. </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
<para>1. Obtain the kernel-<version>.src.rpm file from one of the following sources: </para>
<itemizedlist>
<listitem>
<para> The SRPMS directory on the appropriate SRPMS CD iso image. </para>
</listitem>
<listitem>
<para> The FTP site where you got the kernel package. </para>
</listitem>
<listitem>
<para> By running the following command: </para>
<screen>yum install yum-utilsyumdownloader --source kernel</screen>
</listitem>
</itemizedlist>
<para>2. Install <code>kernel-<version>.src.rpm</code> using the command: </para>
<itemizedlist>
<listitem>
<screen>rpm -Uvh kernel-<version>.src.rpm`</screen>
</listitem>
</itemizedlist>
<para>This writes the RPM contents into <code>/usr/src/redhat/SOURCES</code> and <code>/usr/src/redhat/SPECS</code>. </para>
<para>3. Prepare the kernel sources using the commands: </para>
<itemizedlist>
<listitem>
<screen>cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) kernel-2.6.spec</screen>
</listitem>
</itemizedlist>
<para>The kernel source tree is then located in the <code>/usr/src/redhat/BUILD/kernel-<version>/</code> directory. It is common practice to move the resulting linux-<version> directory to the <code>/usr/src/</code> tree; while not strictly necessary, do this to match the generally-available documentation. </para>
<itemizedlist>
<listitem>
<screen>cd /usr/src/redhat/BUILD/kernel-<version>mv linux-<version> /usr/src/cd /usr/srcln -s ./linux-<version> linuxcd /usr/src/linux</screen>
</listitem>
</itemizedlist>
<para>4. The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named <code>configs/kernel-<version>-i686-smp.config</code>. Issue the following command to place the desired configuration file in the proper place for building: </para>
<itemizedlist>
<listitem>
<screen>cp configs/<desired-config-file> .config</screen>
</listitem>
</itemizedlist>
<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>
<para>5. 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 Makefile. To protect the innocent, the Makefile has been changed to generate a kernel with a different name from that of the running kernel. Before a module can be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. To do this, you must edit the kernel Makefile. </para>
<para>For example, if the <code>uname -r</code> returns the string <code>2.6.11-1.234_FC4</code>, change the <code>EXTRAVERSION</code> definition from this: </para>
<itemizedlist>
<listitem>
<screen>EXTRAVERSION = -prep</screen>
</listitem>
</itemizedlist>
<para>to this: </para>
<itemizedlist>
<listitem>
<screen>EXTRAVERSION = -1.234_FC4</screen>
</listitem>
</itemizedlist>
<para>that is, substitute everything from the final dash onward. </para>
<para>6. Issue the following command: </para>
<itemizedlist>
<listitem>
<screen>make oldconfig</screen>
</listitem>
</itemizedlist>
<para>You can then proceed as usual. </para>
</section>
<section>
<title>Building Only Kernel Modules</title>
<para>An exploded source tree is not required to build a kernel module, such as your own device driver, against the currently in-use kernel. For example, to build the <code>foo.ko</code> module, create the following Makefile in the directory containing the <code>foo.c</code> file: </para>
<itemizedlist>
<listitem>
<screen>obj-m := foo.oKDIR := /lib/modules/$(shell uname -r)/buildPWD := $(shell pwd)default:$(MAKE) -C $(KDIR) M=$(PWD) modules</screen>
</listitem>
</itemizedlist>
<para>Issue the <code>make</code> command to build the <code>foo.ko</code> module. </para>
</section>
<section>
<title>User Space Dependencies on the Kernel</title>
<para>Fedora Core release has support for clustered storage through the Global File System (GFS). This requires a special kernel that works in conjunction with some user-space utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you cannot simply use the <code>rpm -e kernel-<version></code> command as in earlier distributions because these user space packages depend on the kernel package. You may either list both the kernel package and all of its user space dependent packages on the <code>rpm -e</code> command, or you can use the <code>yum remove kernel-<version></code> command instead. The <code>yum</code> command automatically removes dependent packages, if necessary. </para>
</section>
</section>
</article>
--- NEW FILE Legacy-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Legacy Information</title>
<section>
<title>Systemwide Search Changes</title>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>
<code>Slocate</code> has been replaced with <code>mlocate</code> in this release</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> The <code>/usr/bin/{locate,updatedb}</code> implementation <code>slocate</code> was replaced by <code>mlocate</code>. </para>
</td>
</tr>
</table>
</listitem>
<listitem>
<para> The <code>locate</code> command should be completely compatible </para>
</listitem>
<listitem>
<para>
<code>/etc/updatedb.conf</code> is compatible for correct configuration files </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 not compatible, custom scripts using <code>updatedb</code> might have to be changed. </para>
</listitem>
</itemizedlist>
<section>
<title>LinuxThreads No Longer Available</title>
<para>The <code>LinuxThreads</code> library, which was deprecated in Fedora Core 4, is no longer available in this release. <code>NPTL</code> has been the default threading library since Red Hat Linux 9. </para>
</section>
<section>
<title>Legacy Compatability Libraries</title>
<para>Fedora Core includes legacy system libraries for compatibility with older software. This software is part of the <emphasis role='strong'>Legacy Software Development</emphasis> group that is not installed by default. Users who require this functionality can select this group during installation or run the following command post-installation. </para>
<itemizedlist>
<listitem>
<screen>yum groupinstall "Legacy Software Development"</screen>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE Multimedia-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Multimedia</title>
<para>Fedora Core includes applications for assorted multimedia functions, including playback, recording and editing. Additional packages are available through the Fedora Extras repository. </para>
<section>
<title>Multimedia Players</title>
<para>By default, Fedora Core installs with <emphasis role='strong'>Rhythm Box</emphasis>, <emphasis role='strong'>Totem</emphasis>, and <emphasis role='strong'>Helix Player</emphasis> for media playback. In addition, many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular <emphasis role='strong'>XMMS</emphasis> package. Both GNOME and KDE also have specific sets of programs that can be used with a variety of formats. Other popular programs, such as Adobe/Macromedia's <emphasis role='strong'>Flash Player</emphasis>, <emphasis role='strong'>Real Player</emphasis>, <emphasis role='strong'>VLC</emphasis>, <emphasis role='strong'>MPlayer</emphasis>, and <emphasis role='strong'>Xine</emphasis>, can also be installed, but are excluded from the Fedora repositories since they are not compatible with Fedora's licensing or are usually distributed with support for restricted formats. For more on this, refer to: the <ulink url!
='/http'>//fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software:Excluded Multimedia Software</ulink> section. </para>
<para>Fedora Core is also equipped to take full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. This means that many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, the old limitation disappears. For more information about ALSA, visit the project website: </para>
<para>
<ulink url='http://www.alsa-project.org/'>http://www.alsa-project.org/</ulink>
</para>
</section>
<section>
<title>Ogg and Xiph.Org Foundation Formats</title>
<para>Fedora includes complete support for the Ogg media container format, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. More information on these formats and how to use them can be found at the Xiph.Org Foundation's web site: </para>
<para>
<ulink url='http://www.xiph.org/'>http://www.xiph.org/</ulink>
</para>
</section>
<section>
<title>MP3 & DVD Support</title>
<para>Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. For more information, refer to: </para>
<para>
<ulink url='http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software'>http://fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multimedia_Software</ulink>
</para>
</section>
<section>
<title>Excluded Multimedia Software</title>
<anchor id='Excluded_Multimedia_Software'/>
<para>
</para>
<para>Several programs are excluded from Fedora Core and Fedora Extras due to patent or license restrictions. These include programs which provide MP3 and DVD support, Flash Player, and Real Player. For more on this subject, please see: </para>
<para>
<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>Tools are included in Fedora Core and Fedora Extras for easily mastering and burning CDs and DVDs. Tools that can be used from the console include <code>cdrecord</code>, <code>readcd</code>, <code>mkisofs</code>, and other typical Linux applications. For GNOME users, the <code>xcdroast</code> package from Fedora Core and the <code>graveman</code> package from Fedora Extras allows for easy preparation of audio and data discs. For KDE users, the <code>k3b</code> package provides a very robust tool for these tasks. </para>
</section>
</section>
</article>
--- NEW FILE Networking-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Networking</title>
<section>
<title>Major Kernel Changes 2.6.11 - 2.6.14</title>
<section>
<title>IPv4 Address Promotion</title>
<para>Starting with version 2.6.12 of the kernel a new feature has been added called <emphasis>named address promotion</emphasis>. It allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. By enabling the new sysctl <code>net.ipv4.conf.all.promote_secondaries</code> (or one of the interface specific variants) this behaviour can be changed to promote one of the secondary addresses to be the new primary address. </para>
</section>
<section>
<title>Configurable Source Address for ICMP Errors</title>
<para>The current behaviour when selecting the source address for ICMP error messages is to use the address of the interface the ICMP error is going to be sent out. Kernel version 2.6.12 introduces a new sysctl <code>net.ipv4.icmp_errors_use_inbound_ifaddr</code> that allows changing this behaviour to use the address of the interface that received the original error-causing packet. </para>
<para>For example, the kernel receives an ICMP echo request on eth0. Because the new sysctl option is enabled, this causes the ICMP echo reply to be sent out via eth1. The address of eth0 is used when the default behaviour would use the address of eth. </para>
<para>This may ease network debugging in asynchronous routing setups. </para>
</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 stays 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>
<itemizedlist>
<listitem>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject> Affecting the Congestion Control Algorithm </para>
<para>An interesting addition for developers is that the congestion control algorithm is socket specific and can be changed via the socket option <code>TCP_CONGESTION</code>. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>Queue Avoidance upon Carrier Loss</title>
<para>When a network driver notices a carrier loss, for example, when the cable is pulled out, the driver stops the queue in front of the driver. This has been causing the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now ceases to accept any packets for queueing for any device that is operationally down, that is, has its queue disabled. </para>
</section>
<section>
<title>DCCP Protocol Support</title>
<para>Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental but known to work. Work has begun to make userspace applications aware of this new protocol. </para>
</section>
<section>
<title>Wireless</title>
<para>A new driver named HostAP has been added to 2.6.14-rc1 allowing the emulation of a wireless access point in software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added. </para>
</section>
<section>
<title>Miscellaneous</title>
<itemizedlist>
<listitem>
<para> A lot of TCP Segmentation Offloading (TSO) related fixes have been included. </para>
</listitem>
<listitem>
<para> A new textsearch infrastructure has been added useable with the corresponding iptables and extended match. </para>
</listitem>
<listitem>
<para> Both the IPv4 and IPv6 multicast joining interface visible by userspace have been reworked and brought up to the latest standards. </para>
</listitem>
<listitem>
<para> The SNMPv2 MIB counter ipInAddrErrors is finally supported for IPv4. </para>
</listitem>
<listitem>
<para> Various new socket options proposed in Advanced API (RFC3542) have been added. </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Userspace Tools</title>
<para>The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the iproute2 tool now issues a warning if no prefix length is provided to warn about possible unintended deletions: </para>
<itemizedlist>
<listitem>
<screen>ip addr list dev eth0 4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000inet 10.0.0.3/24 scope global eth0su -c 'ip addr del 10.0.0.3 dev eth0'Warning: Executing wildcard deletion to stay compatible with oldscripts. Explicitly specify the prefix length (10.0.0.3/32) toavoid this warning. This special behaviour is likely to disappearin further releases, fix your scripts!</screen>
</listitem>
</itemizedlist>
<para>The correct method of deleting the address and thus avoiding the warning is: </para>
<itemizedlist>
<listitem>
<screen>su -c 'ip addr del 10.0.0.3/24 dev eth0'</screen>
</listitem>
</itemizedlist>
<para>Previously, it has not been possible to tell if an interface is down administratively or because no carrier can be found (cable unplugged). The flag <code>NO-CARRIER</code> has been introduced that shows up as a link flag if the link is administratively up but no carrier can be found. </para>
<para>The ip command now supports a batch mode via the argument <code>-batch</code> that works similar to the tc command to speed up batches of tasks. </para>
</section>
</section>
</article>
--- NEW FILE OverView-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Fedora Core 5 Tour</title>
<para>Welcome to Fedora. In this new exciting new release, we present you a sneak preview of Fedora Core 5 filled with pictures and videos available at <ulink url='http://fedoraproject.org/wiki/Tours/FedoraCore5'>http://fedoraproject.org/wiki/Tours/FedoraCore5</ulink>. </para>
<section>
<title>What Has Changed Since Fedora Core 4</title>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
</imageobject>
<textobject>
<phrase>(!)</phrase>
</textobject>
</inlinemediaobject> We request active participation from the community to test the following major changes with special care and provide feedback to the developers for a robust and cutting edge release of Fedora Core 5. You can provide feedback and discuss changes in the fedora-test (<ulink url='http://redhat.com/mailman/listinfo/fedora-test-list/'>http://redhat.com/mailman/listinfo/fedora-test-list/</ulink>) mailing list. Thank you for your interest and participation in the development of Fedora. </para>
<section>
<title>Desktop</title>
<itemizedlist>
<listitem>
<para> A completely revamped look and feel including a bubbly new theme, wallpaper, screensaver and logo has been provided that is visually appealing and demonstrates the exciting and user friendly nature of Fedora. </para>
</listitem>
<listitem>
<para> GNOME 2.13.4 (<ulink url='http://live.gnome.org/TwoPointThirteen'>http://live.gnome.org/TwoPointThirteen</ulink>) development release and KDE 3.5 (<ulink url='http://kde.org/announcements/announce-3.5.php'>http://kde.org/announcements/announce-3.5.php</ulink>) general release of popular desktop environments is available. </para>
</listitem>
<listitem>
<para> GNOME Power Manager and GNOME Screensaver are available as a technology preview within this release. </para>
</listitem>
<listitem>
<para> Open<emphasis role='strong'/>Office.org 2.0 (<ulink url='http://www.openoffice.org/product/index.html/'>http://www.openoffice.org/product/index.html/</ulink>) release is included. Open<emphasis role='strong'/>Office.org now uses system versions for many of the libraries leading to increased performance and efficiency. </para>
</listitem>
<listitem>
<para> Firefox 1.5(<ulink url='http://www.mozilla.com/firefox/releases/1.5.html'>http://www.mozilla.com/firefox/releases/1.5.html</ulink>) web browser with many new features is included in this release </para>
</listitem>
<listitem>
<para> Pup, the package updater has been joined by Pirut, which is the replacement for system-config-packages providing comprehensive software package management using yum as a backend. </para>
</listitem>
<listitem>
<para> Beagle which provides a index based search interface, f-spot for photo management and tomboy, a note taking application has been added to this release. </para>
</listitem>
<listitem>
<para> Support for Broadcom 43xx wireless chipsets (<ulink url='http://bcm43xx.berlios.de/'>http://bcm43xx.berlios.de/</ulink>) has been included in the kernel. </para>
</listitem>
<listitem>
<para> I18N support has drastically improved through the use of SCIM language input framework which has replaced IIMF in this release </para>
</listitem>
<listitem>
<para> Gstreamer media framework 0.10 which brings major improvements in robustness and features has been included in this release. Totem uses this new version of Gstreamer now. Other media applications that use gstreamer is expected to be updated within the subsequent releases. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Administration</title>
<itemizedlist>
<listitem>
<para> Xen Virtualisation software and yum package manager are now well integrated within the Fedora installer. The installer interface is more streamlined. Remote logging and improved support for tracebacks is included. </para>
</listitem>
<listitem>
<para> System Tap (<ulink url='http://sourceware.org/systemtap/'>http://sourceware.org/systemtap/</ulink>) a instrumentation system for debugging and analysing performance bottle necks and Frysk (<ulink url='http://sourceware.org/frysk/'>http://sourceware.org/frysk/</ulink>), an execution analysis technology for monitoring running processes or threads is included within this release. </para>
</listitem>
</itemizedlist>
</section>
<section>
<title>System Level Changes</title>
<itemizedlist>
<listitem>
<para> Xorg X11<emphasis role='strong'/>R7.0 has been included in this release. This is the first modular version, which helps in providing additional features and bug fixes at a faster pace. </para>
</listitem>
<listitem>
<para> gcc 4.1 compiler is included and the entire set of Fedora packages is now build using this new compiler version which brings in new security and performance enhancements. </para>
</listitem>
<listitem>
<para> PCMCIA framework used by laptop and mobile devices had changed as with kernel version 2.6.13-rc1 onwards. The older pcmcia-cs package using the cardmgr/pcmcia service has been replaced with a new pcmciautils package where the PCMCIA devices are handled directly with the hotplug system using udev dynamically in this Fedora release. This increases both efficiency and performance of the system. More information about this changes are available from <ulink url='http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html'>http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html</ulink>. </para>
</listitem>
<listitem>
<para> SELinux implementation has undergone a major change with a switchover to <ulink url='http://serefpolicy.sourceforge.net/'>reference policy</ulink>. SELinux reference policy can support binary policy modules. It is possible now to move SELinux policies into individual packages and make it easier for users to ship site-specific policy customizations when required. This version also adds support for MCS (Multi Category System) enabled by default and MLS (Multi Level System) in addition to the the previous versions which have TE (Type Enforcement) which is enabled by default and RBAC (Role Based Access Contro) security sub systems within the SELinux framework. </para>
</listitem>
</itemizedlist>
</section>
</section>
<section>
<title>Road Map</title>
<para>The proposed plans for Fedora in this version are available from <ulink url='http://fedoraproject.org/wiki/RoadMap'>http://fedoraproject.org/wiki/RoadMap</ulink>. </para>
</section>
</section>
</article>
--- NEW FILE PackageChanges-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Package Changes</title>
<para>Beat Writer: <ulink url='/RahulSundaram'>RahulSundaram</ulink>
</para>
<para>Note: treediff.py dist-fc4 dist-rawhide > /tmp/diff sed -e 's,^,* ,g' -e 's,$,\n,g' /tmp/diff > diffwiki </para>
<para>Note: Should add a note on third party repos and yum plugin to protect base repos </para>
<section>
<title>Package Change Details</title>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>
<code>LinuxThreads</code> library is no longer available</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para>
<code>LinuxThreads</code> was been deprecated in Fedora Core 4 and is no longer available in this release. NPTL, which has been the default threading library since Red Hat Linux 9, has replaced this completely. </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE PackageNotes-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Package Notes</title>
<para>The following sections contain information regarding packages that have undergone significant changes for Fedora Core . For easier access, they are generally organized using the same groups used in Anaconda. </para>
<section>
<title>Basic Components</title>
<para>This section contains information related to basic system components. </para>
<section>
<title>Mouse Configuration Utility Removed</title>
<para>The <emphasis role='strong'>system-config-mouse</emphasis> configuration utility has been dropped in this release because synaptic and 3 button mouse configuration is being done automatically. Serial mice are no longer supported. </para>
</section>
<section>
<title>Screensavers Not Installed by Default</title>
<para>Screensavers not installed by default anymore? Explain why and provide commands to install them. </para>
</section>
<section>
<title>NetworkManager</title>
<para>Because it is not possible to test <ulink url='/NetworkManager'>NetworkManager</ulink> in all configurations, it is not enabled by default in Fedora Core . </para>
<para>Refer to this page for information about enabling this application: </para>
<para>
<ulink url='http://fedoraproject.org/wiki/Tools/NetworkManager'>http://fedoraproject.org/wiki/Tools/NetworkManager</ulink>
</para>
</section>
<section>
<title>Dovecot</title>
<para>This release of Fedora Core has a new version of the Dovecot IMAP server software which has has many changes in its configuration file. These changes are of importance especially to users upgrading from a previous release. Refer to <ulink url='http://wiki.dovecot.org/UpgradingDovecot'>http://wiki.dovecot.org/UpgradingDovecot</ulink> for more information on the changes. </para>
<para>
</para>
</section>
</section>
</section>
</article>
--- NEW FILE PackageNotesJava-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Handling Java and Java-like Packages</title>
<para>Fedore Core includes a tool suite and execution environment based on free software technologies that is capable of building and running many useful programs written in the Java programming language, including the Eclipse IDE, Tomcat, and Open<emphasis role='strong'/>Office.org. </para>
<para>In addition to the free software stack, Fedora Core is designed to let you install multiple Java implementations and switch between them using the <code>alternatives</code> command line tool. However, every Java system you install must be packaged using the <ulink url='http://www.jpackage.org'>JPackage Project's</ulink> packaging guidelines to take advantage of <code>alternatives</code>. </para>
<para>Once installed properly, the root user should be able to switch between <code>java</code> and <code>javac</code> implementations using the <code>alternatives</code> command: </para>
<itemizedlist>
<listitem>
<screen>alternatives --config java alternatives --config javac</screen>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Fedora Core does not include the proprietary Sun Microsystems Java implementation</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Java is a trademark of Sun Microsystems. This entirely free software stack is <emphasis role='strong'>not</emphasis> Java but can run many programs written in Java. For more information, refer to the Java FAQ at <ulink url='http://fedoraproject.org/wiki/JavaFAQ'>http://fedoraproject.org/wiki/JavaFAQ</ulink>. </para>
</td>
</tr>
</table>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
</imageobject>
<textobject>
<phrase>(!)</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>When to use the JPackage Project RPM repository</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Fedora Core includes many packages derived from the excellent JPackage Project, which provides a Java software repository. Refer to <ulink url='http://jpackage.org'>http://jpackage.org</ulink> for more information on the Jpackage Project.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>
</td>
</tr>
</table>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/alert.png' depth='15'/>
</imageobject>
<textobject>
<phrase>/!\</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Do not simply add the JPackage repo to your <code>yum</code> configuration</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> Understand better what you are doing if you plan on mixing packages from the Fedora and JPackage repos. Doing so may leave your system in a state that cannot be easily fixed. Be careful, and do research before you proceed. </para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
</section>
</article>
--- NEW FILE Printing-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Printing</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
</section>
</article>
--- NEW FILE ProjectOverview-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>An Overview of the Fedora Project</title>
<para>The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community. </para>
<para>For more information, refer to the Fedora Project website: </para>
<para>
<ulink url='http://fedora.redhat.com/'>http://fedora.redhat.com/</ulink>
</para>
<para>Your participation is welcome. See <ulink url='http://fedoraproject.org/wiki/HelpWanted'>http://fedoraproject.org/wiki/HelpWanted</ulink> for details. </para>
<para>For communication in the Fedora Project look at <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
<para>In addition to the website, the following mailing lists are available: </para>
<itemizedlist>
<listitem>
<para>
</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>
</itemizedlist>
</listitem>
<listitem>
<para>
</para>
<itemizedlist>
<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>
</itemizedlist>
</listitem>
<listitem>
<para>
</para>
<itemizedlist>
<listitem>
<para>
<ulink url='mailto:fedora-devel-list at redhat.com'>fedora-devel-list at redhat.com</ulink> — For developers, developers, developers </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para>
</para>
<itemizedlist>
<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>
</listitem>
</itemizedlist>
<para>To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <listname>-request (where <listname> is one of the above list names.) </para>
<para>Alternately, you can subscribe through the Web interface: </para>
<para>
<ulink url='http://www.redhat.com/mailman/listinfo/'>http://www.redhat.com/mailman/listinfo/</ulink>
</para>
<para>The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC is a real-time, text-based form of communication. With it, you can have conversations with multiple people in an open channel or chat with someone privately one-on-one. </para>
<itemizedlist>
<listitem>
<para>To talk with other Fedora Project participants via IRC, access freenode IRC network. Refer to the freenode website (<ulink url='http://www.freenode.net/'>http://www.freenode.net/</ulink>) for more information. Fedora Project participants frequent the #fedora channel, while Fedora Project developers can often be found on the #fedora-devel channel. Some of the larger projects may have their own channels as well; this information can be found on the project pages and at <ulink url='http://fedoraproject.org/wiki/Communicate'>http://fedoraproject.org/wiki/Communicate</ulink>. </para>
</listitem>
</itemizedlist>
<para>In order to talk on the #fedora channel, you will need to register your nickname (nick). Instructions are given when you /join the channel. </para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='16' fileref='/wiki/ntheme/img/icon-info.png' depth='16'/>
</imageobject>
<textobject>
<phrase>{i}</phrase>
</textobject>
</inlinemediaobject> Red Hat has no control over the Fedora Project IRC channels or their content. </para>
</section>
</article>
***** Error reading new file: [Errno 2] No such file or directory: 'RELEASE-NOTES-en.xml'
--- NEW FILE Samba-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Samba</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
<para>
</para>
</section>
<section>
<title>Samba (Windows Compatibility)</title>
<para>This section contains information related to Samba, the suite of software that enables Linux to interact with Microsoft Windows systems. </para>
<section>
<title>SMB Browsing</title>
<para>Browsing of Windows shares (also known as SMB browsing) is now possible. In releases prior to Fedora Core 5, the firewall prevented the proper function of SMB browsing. With the addition of <code>ip_conntrack_netbios_ns</code> kernel module to the 2.6.14 kernel and corresponding enhancements to <code>system-config-securitylevel</code>, the firewall now properly tracks SMB browse broadcasts. </para>
<section>
<title>Samba Configuration using SWAT</title>
<para>Samba-SWAT, is still required for ease of use of Samba. Once installed you can access it by opening a web-browser and navigating to <emphasis><ulink url='http://localhost:901'>http://localhost:901</ulink>
</emphasis> replacing <emphasis>localhost</emphasis> with the name of the computer on which <emphasis>Samba</emphasis> is installed. </para>
<para>For more information about SWAT navigate here, <ulink url='http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html'>http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/SWAT.html</ulink>
</para>
<para>More Information such as a detailed How-To Install, Configure etc will follow soon. </para>
<para>
<ulink url='/CategoryDocumentation'>CategoryDocumentation</ulink>
</para>
</section>
</section>
</section>
</article>
--- NEW FILE Security-en.xml ---
||<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Security</title>
<para>This section highlights various security items from Fedora Core. </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'>Comment for beat writer <ulink url='/JoshBressers'>JoshBressers</ulink>
</emphasis>
</para>
</td>
</tr>
<tr>
<td>
<para> fstack-protecter information was provided by Arjan. I will add more information on fortify source after reading up the relevant material. Should also add introductory information on SELinux, link to SELinux FAQ. Write about the various security features like /dev/mem restriction, Exec Shield, PIE, ELF hardening in <ulink url='/Security/Features'> Security Features</ulink> page and link from this section to provide a comprehensive overview of the security features available in addition to others like firewall or network services like sendmail only listening to localhost - <ulink url='/RahulSundaram'>RahulSundaram</ulink>
</para>
</td>
</tr>
</table>
</listitem>
</itemizedlist>
<section>
<title>General Information</title>
<para>General introduction to the many proactive security features in Fedora, current status and policies is available from this page: </para>
<para>
<ulink url='http://fedoraproject.org/wiki/Security'>http://fedoraproject.org/wiki/Security</ulink>
</para>
</section>
<section>
<title>What's New</title>
<section>
<title>PAM module Deprecation</title>
<para>
<code>Pam_stack</code> is deprecated in this release. </para>
<para>Linux-PAM 0.78 and later contains the include directive which obsoletes the <code>pam_stack</code> module. <code>pam_stack</code> module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it. </para>
<itemizedlist>
<listitem>
<table>
<caption/>
<tr>
<td>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
</imageobject>
<textobject>
<phrase>(!)</phrase>
</textobject>
</inlinemediaobject>
<emphasis role='strong'>Upgraded installations using older PAM stacks need manual intervention</emphasis>
</para>
</td>
</tr>
</table>
<para> When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration fiels are created as <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>
</listitem>
</itemizedlist>
<para>Example /etc/pam.d/login: </para>
<itemizedlist>
<listitem>
<screen>#%PAM-1.0auth required pam_securetty.soauth required pam_stack.so service=system-authauth required pam_nologin.soaccount required pam_stack.so service=system-authpassword required pam_stack.so service=system-auth# pam_selinux.so close should be the first session rulesession required pam_selinux.so closesession required pam_stack.so service=system-authsession required pam_loginuid.sosession optional pam_console.so# pam_selinux.so open should be the last session rulesession required pam_selinux.so open#%PAM-1.0auth required pam_securetty.soauth include system-auth# no module should remain after 'include' if 'sufficient' might# be used in the included configuration file# pam_nologin moved to account phase - it's more appropriate there# other modules might be moved before the system-auth 'include'account required pam_nologin.soaccount include syst!
em-authpassword include system-auth# pam_selinux.so close should be the first session rulesession required pam_selinux.so closesession include system-auth# the system-auth config doesn't contain sufficient modules# in the session phasesession required pam_loginuid.sosession optional pam_console.so# pam_selinux.so open should be the last session rulesession required pam_selinux.so open</screen>
</listitem>
</itemizedlist>
</section>
<section>
<title>Buffer Overflow detection and variable reordering</title>
<para>All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called <code>fstack-protecter</code>. <code>fstack-protector</code> puts a canary value on the stack of <emphasis>key</emphasis> functions, just before the return address and just before returning from that value. Then the canary value is verified, and if there was a buffer overflow, the canary will no longer match and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature written by Red Hat developers as a rewritten implementation of the IBM <ulink url='http://www.research.ibm.com/trl/projects/security/ssp/'>ProPolice/SSP</ulink> feature and available as part of GCC 4.1 compiler used in Fedora Core . </para>
<para>This is in addition to using <code>FORTIFY_SOURCE</code> from Fedora Core 4 onwards. </para>
<para>
</para>
<para>
</para>
</section>
</section>
</section>
</article>
--- NEW FILE SecuritySELinux-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>SELinux</title>
<para>The new SELinux project pages have troubleshooting tips, explanations, and pointers to documentation and references: </para>
<itemizedlist>
<listitem>
<para> New SELinux project pages: </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SELinux'>http://fedoraproject.org/wiki/SELinux</ulink>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> If you are having trouble: </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SELinux/Troubleshooting'>http://fedoraproject.org/wiki/SELinux/Troubleshooting</ulink>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Questions? </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedora.redhat.com/docs/selinux-faq/'>http://fedora.redhat.com/docs/selinux-faq/</ulink>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Looking for a list of SELinux commands? </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SELinux/Commands'>http://fedoraproject.org/wiki/SELinux/Commands</ulink>
</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para> Want to know which domains are confined? </para>
<itemizedlist>
<listitem>
<para>
<ulink url='http://fedoraproject.org/wiki/SELinux/Domains'>http://fedoraproject.org/wiki/SELinux/Domains</ulink>
</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<section>
<title>Multi Category Security (MCS)</title>
<para>General use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with <emphasis>categories</emphasis>. For example, <code>Company_Confidential</code>, <code>CEO_EYES_ONLY</code>, or <code>Sysadmin_Passwords</code>. </para>
<para>For more information, you can read this article from the creator of MCS: </para>
<para>
<ulink url='http://james-morris.livejournal.com/5583.html'>http://james-morris.livejournal.com/5583.html</ulink>
</para>
<section>
<title>Multilevel Security (MLS)</title>
<para>A specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object (a document file) can have the security level of <code>{ Secret, ProjectMeta }</code>, where <code>Secret</code> is the sensitivity level, and the <code>ProjectMeta</code> is the category. </para>
<para>Refer to this technical article for more information: </para>
<para>
<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-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/ServerTools</title>
<para>This section highlights changes and additions to the various GUI server and system configuration tools in Fedora Core. </para>
<section>
<title>system-config-printer</title>
<section>
<title>SMB Browsing Outside Local Network</title>
<para>Browsing for Samba print shares across subnets is now possible. In addition, if at least one WINS server has been specified in <emphasis>/etc/samba/smb.conf</emphasis>, the first address specified is used when browsing. </para>
</section>
<section>
<title>Kerberos Support for SMB Printers</title>
<para>The system-config-printer application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and <emphasis>/usr/sbin/printconf-gui</emphasis> must be launched via sudo. No username and password is stored in <emphasis>/etc/cups/printers.conf</emphasis>. Printing is still possible if the SMB print queue permits anonymous printing. </para>
</section>
</section>
<section>
<title>system-config-securitylevel</title>
<section>
<title>Trusted Service Additions</title>
<para>Samba is now listed in the "Trusted services" list and can thus be enabled to permit the firewall to pass SMB traffic. </para>
</section>
<section>
<title>Port Ranges</title>
<para>When defining "Other Ports" in the <code>system-config-securitylevel</code> tool, port ranges can now be specified. For example, specifying "6881-6999:tcp" results in the addition of the following line to <code>/etc/sysconfig/iptables</code>: </para>
<itemizedlist>
<listitem>
<screen>A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 -j ACCEPT </screen>
</listitem>
</itemizedlist>
</section>
</section>
</section>
</article>
--- NEW FILE SystemDaemons-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/SystemDaemons</title>
<para>This page is a stub for content. If you have a contribution for this release notes beat for the test release of Fedora Core, add it to this page or create a sub-page. </para>
<para>Beat writers: this is where you want to fill in with instructions about how to post relevant information. Any questions that come up can be taken to a bugzilla report for discussion to resolution, or to fedora-docs-list for wider discussions. </para>
<para>
</para>
</section>
<section>
<title>System Services</title>
</section>
</article>
--- NEW FILE WebServers-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Web Servers</title>
<para>This section contains information on Web-related applications. </para>
<section>
<title>httpd</title>
<para>Version 2.2 of the Apache HTTP Server is now included in Fedora Core. This release brings a number of improvements since the 2.0 series, including: </para>
<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> refactored authentication and authorization support </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 >2Gb request bodies) </para>
</listitem>
<listitem>
<para> new modules <code>mod_dbd</code> and <code>mod_filter</code> bring SQL database support and enhanced filtering </para>
</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>
</listitem>
</itemizedlist>
<para>Any third-party modules compiled for <code>httpd</code> 2.0 must be rebuilt for <code>httpd</code> 2.2. </para>
<para>Any existing configuration files might need adapting for 2.2, refer to this page for more information: </para>
<para>
<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 php 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-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Welcome</title>
<section>
<title>Welcome to Fedora Core</title>
<itemizedlist>
<listitem>
<para>
</para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/attention.png' depth='15'/>
</imageobject>
<textobject>
<phrase><!></phrase>
</textobject>
</inlinemediaobject> This is a test release and is provided for developers and testers to participate and provide feedback. It is not meant for end users. </para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
</imageobject>
<textobject>
<phrase>(!)</phrase>
</textobject>
</inlinemediaobject> Subscribe to the fedora-test and fedora-devel mailings lists to keep track of important changes in the current development versions and provide feedback to the developers. Fedora Project requests you to file bug reports and enhancements to provide a improved final release to end users. See the following document for more information. </para>
<para>
<ulink url='http://fedoraproject.org/wiki/BugsAndFeatureRequests'>http://fedoraproject.org/wiki/BugsAndFeatureRequests</ulink>. Thank you for your participation. </para>
<para>
<inlinemediaobject>
<imageobject>
<imagedata width='15' fileref='/wiki/ntheme/img/idea.png' depth='15'/>
</imageobject>
<textobject>
<phrase>(!)</phrase>
</textobject>
</inlinemediaobject> Latest Release Notes on the Web </para>
<para>These release notes may be updated. Visit <ulink url='http://fedora.redhat.com/docs/release-notes/'>http://fedora.redhat.com/docs/release-notes/</ulink> to view the latest release notes for Fedora Core . </para>
</listitem>
</itemizedlist>
<para>Refer to these webpages to find out more information about Fedora: </para>
<itemizedlist>
<listitem>
<para>
<ulink url='/Docs/Beats/OverView'>Docs/Beats/OverView</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url='/Docs/Beats/Introduction'>Docs/Beats/Introduction</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>
</section>
</article>
--- NEW FILE Xorg-en.xml ---
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docbook.org/xml/4.4/docbookx.dtd">
<article>
<articleinfo>
<title>Temp</title>
</articleinfo>
<section>
<title>Docs/Beats/Xorg</title>
<para/>
</section>
<section>
<title>X Window System (Graphics)</title>
<para>This section contains information related to the X Window System implementation provided with Fedora. </para>
<section>
<title>xorg-x11</title>
<para>X.org X11 is an open source implementation of the X Window System. It provides the basic low level functionality which full fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed upon. </para>
<para>For more information about Xorg refer to <ulink url='http://xorg.freedesktop.org/wiki/'>http://xorg.freedesktop.org/wiki/</ulink>
</para>
<para>You can use Applications=> System Settings=> Display or system-config-display to configure the settings. The configuration file for Xorg is located in /etc/X11/xorg.conf </para>
<para>Modular X.Org X11<emphasis role='strong'/>R7 RC2 was released into Fedora development (rawhide) on November 16, 2005. This is the first modular release of Xorg which among several other benefits, enable users to receive updates in a faster pace and helps developers to develop and release specific components in a rapid fashion. </para>
<para>More information on the current status of the Xorg modularization effort in Fedora is available from <ulink url='/Xorg/Modularization'>http://fedoraproject.org/wiki/Xorg/Modularization</ulink>
</para>
</section>
<section>
<title>Xorg X11R7.0 Developer Notes</title>
<para>X11<emphasis role='strong'/>R7.0 is included in this release and there are a number of things that software developers, and packagers in Fedora repositories need to be aware of in order to ensure that their software or software packages properly compile and work with X11<emphasis role='strong'/>R7. Some are simple changes, while others may be more involved. Here is a summary of issues that may arise and where possible, suggestions on how to fix them. </para>
<section>
<title>The /usr/X11R6 directory hierarchy</title>
<para>X11<emphasis role='strong'/>R7 install into /usr directly now, and no longer uses the /usr/X11<emphasis role='strong'/>R6 hierarchy. Applications which rely on files being present at fixed paths under /usr/X11<emphasis role='strong'/>R6 at compile time or at run time, must be updated to use the system PATH, or some other mechanism to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks. </para>
</section>
<section>
<title>Imake</title>
<para>Imake is no longer used to build the X Window System, and as such is now officially deprecated. Imake, xmkmf and other utilities previously supplied by the X Window System, are still supplied in X11<emphasis role='strong'/>R7, however X.Org highly recommends that people migrate from Imake to using GNU autotools and pkg-config. imake support may vanish in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects. </para>
</section>
<section>
<title>The systemwide app-defaults directory</title>
<para>The system app-defaults directory for X resources, is now "%{_datadir}/X11/app-defaults", which expands to /usr/share/X11/app-defaults on Fedora Core 5 and for future Red Hat Enterprise Linux systems. </para>
</section>
<section>
<title>xft-config can't be found</title>
<para>Modular X now uses GNU autotools, and pkg-config for its buildsystem configuration, etc. xft-config has been deprecated for 2-3 years now, and pkgconfig *.pc files have been provided for most of this time. Applications which previously used xft-config to obtain the Cflags or libs options for building with, must now be updated to use pkg-config. </para>
</section>
</section>
<section>
<title>Xorg X11R7 Developer Overview</title>
<para>Here is a short list of some of the more developer/package visible changes that are present in X11<emphasis role='strong'/>R7: </para>
<itemizedlist>
<listitem>
<para> The entire buildsystem has changed from "Imake" to the GNU autotools collection. </para>
</listitem>
<listitem>
<para> All of the libraries now install pkgconfig *.pc files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in /usr/X11<emphasis role='strong'/>R6/lib or elsewhere. </para>
</listitem>
<listitem>
<para> Everything is now installed directly into /usr instead of /usr/X11<emphasis role='strong'/>R6. All software which hard codes paths to anything in /usr/X11<emphasis role='strong'/>R6, must now be changed preferably to dynamically detect the proper location of the object, or to hard code the new paths that X11<emphasis role='strong'/>R7 uses by default. It is strongly advised to use autodetection methods than to hard code paths. </para>
</listitem>
<listitem>
<para> Every library is in its own private source RPM now, which creates a runtime binary subpackage, and a -devel subpackage. Any software package that previously picked up the development headers, etc. for X libraries by using "Build<emphasis role='strong'/>Requires: (XFree86-devel|xorg-x11-devel)", must now individually list each library dependency individually. When doing this, it is greatly preferred and strongly recommended to use "virtual" build dependencies instead of hard coding the library rpm package names of the xorg implementation. This means you should use: "Build<emphasis role='strong'/>Requires: libXft-devel" instead of using: "Build<emphasis role='strong'/>Requires: xorg-x11-Xft-devel". If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean/safe way to state the dependency, then go ahead and use the "xorg-x11--devel" form. By sticking to the virtual provides/requires mechanism, this mak!
es it painless if and when the libraries move to another location in the future. </para>
</listitem>
</itemizedlist>
</section>
</section>
</article>
--- NEW FILE fdp-info-en.xml ---
<!--
Warning! Warning! Danger, Will Robinson!
This is a generated file, produced from information in
the "rpm-info.xml" file.
DO NOT EDIT THIS FILE DIRECTLY!
Edit "rpm-info.xml" to change this information.
-->
<articleinfo>
<title>Fedora Core 5 test2 Release Notes</title>
<copyright>
<year>2006</year>
<holder>Red Hat, Inc.</holder>
</copyright>
<authorgroup>
<author>
<surname>Wade</surname>
<firstname>Karsten</firstname>
</author>
</authorgroup>
<revhistory>
<revision>
<revnumber>0.0.0</revnumber>
<date>Tue Jan 24 2006</date>
<authorinitials></authorinitials>
<revdescription>
<para>
Dummy entry to make rpm building work; please remove
</para>
</revdescription>
</revision>
</revhistory>
&LEGALNOTICE;
</articleinfo>
- Previous message (by thread): release-notes ArchSpecific-en.xml, 1.2, 1.3 ArchSpecificPPC-en.xml, 1.3, 1.4 ArchSpecificx86-en.xml, 1.2, 1.3 ArchSpecificx86_64-en.xml, 1.2, 1.3 BackwardsCompatibility-en.xml, 1.1, 1.2 Colophon-en.xml, 1.2, 1.3 DatabaseServers-en.xml, 1.1, 1.2 Desktop-en.xml, 1.3, 1.4 Entertainment-en.xml, 1.1, 1.2 Feedback-en.xml, 1.1, 1.2 FileServers-en.xml, 1.2, 1.3 FileSystems-en.xml, 1.1, 1.2 I18n-en.xml, 1.2, 1.3 Installer-en.xml, 1.2, 1.3 Kernel-en.xml, 1.3, 1.4 Legacy-en.xml, 1.3, 1.4 Makefile, 1.17, 1.18 Multimedia-en.xml, 1.2, 1.3 Networking-en.xml, 1.1, 1.2 OverView-en.xml, 1.6, 1.7 PackageChanges-en.xml, 1.3, 1.4 PackageNotes-en.xml, 1.2, 1.3 PackageNotesJava-en.xml, 1.1, 1.2 Printing-en.xml, 1.1, 1.2 ProjectOverview-en.xml, 1.2, 1.3 RELEASE-NOTES-en.xml, 1.20, 1.21 Samba-en.xml, 1.2, 1.3 Security-en.xml, 1.2, 1.3 SecuritySELinux-en.xml, 1.2, 1.3 ServerTools-en.xml, 1.2, 1.3 SystemDaemons-en.xml, 1.2, 1.3 WebServers-en.xml, 1.2, 1.3 Welcome-en.xml, 1.5, 1.6 Xorg-en.xml, 1.2, 1.3
- Next message (by thread): release-notes/it fdp-info-it.xml,NONE,1.1
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the Fedora-docs-commits
mailing list