From fedora-docs-commits at redhat.com Wed Jun 10 15:30:41 2015 Content-Type: multipart/mixed; boundary="===============7842936827611291603==" MIME-Version: 1.0 From: fedora-docs-commits at redhat.com To: docs-commits at lists.fedoraproject.org Subject: release-notes/en Virtualization.xml, NONE, 1.1 ArchSpecific.xml, 1.1, 1.2 ArchSpecificPPC.xml, 1.1, 1.2 ArchSpecificx86.xml, 1.1, 1.2 ArchSpecificx86_64.xml, 1.1, 1.2 BackwardsCompatibility.xml, 1.1, 1.2 Colophon.xml, 1.1, 1.2 DatabaseServers.xml, 1.1, 1.2 Desktop.xml, 1.1, 1.2 DevelTools.xml, 1.2, 1.3 DevelToolsGCC.xml, 1.1, 1.2 Entertainment.xml, 1.1, 1.2 Extras.xml, 1.1, 1.2 Feedback.xml, 1.1, 1.2 FileServers.xml, 1.1, 1.2 FileSystems.xml, 1.1, 1.2 I18n.xml, 1.1, 1.2 Installer.xml, 1.1, 1.2 Java.xml, 1.1 Date: Tue, 28 Feb 2006 12:25:33 -0500 Message-ID: <200602281725.k1SHPXCD013684@cvs-int.fedora.redhat.com> --===============7842936827611291603== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: kwade Update of /cvs/docs/release-notes/en In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13626 Modified Files: ArchSpecific.xml ArchSpecificPPC.xml ArchSpecificx86.xml = ArchSpecificx86_64.xml BackwardsCompatibility.xml Colophon.xml = DatabaseServers.xml Desktop.xml DevelTools.xml = DevelToolsGCC.xml Entertainment.xml Extras.xml Feedback.xml = FileServers.xml FileSystems.xml I18n.xml Installer.xml = Java.xml Kernel.xml Legacy.xml Multimedia.xml Networking.xml = OverView.xml PackageChanges.xml PackageNotes.xml Printing.xml = ProjectOverview.xml Samba.xml Security.xml SecuritySELinux.xml = ServerTools.xml SystemDaemons.xml WebServers.xml Welcome.xml = Xorg.xml = Added Files: Virtualization.xml = Removed Files: PackageNotesJava.xml = Log Message: This is the FC 5 GOLD content from the Wiki, fresh off the press. I'll tag= it with release-notes-FC-5-GOLD-for-ISO as well as a trans tag. --- NEW FILE Virtualization.xml ---
Temp
Virtualization Virtualization in Fedora Core is based on Xen. Xen 3.0 is integrated within Fedora Core in the instal= ler. Refer to http:/= /fedoraproject.org/wiki/Tools/Xen for more information about Xen. =
{i} No PowerPC Support
Xen is not supported on the PowerPC architecture in Fe= dora Core .
Index: ArchSpecific.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ArchSpecific.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ArchSpecific.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ArchSpecific.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,18 +1,17 @@ - +
Temp -
- Archictecture Specific +
+ Docs/Beats/ArchSpecific This section provides notes that are specific to the supported h= ardware architectures of Fedora Core. - - - + + + + + +
Index: ArchSpecificPPC.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ArchSpecificPPC.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ArchSpecificPPC.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ArchSpecificPPC.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,107 +1,84 @@ - +
Temp -
+
PPC Specifics for Fedora This section covers any specific information you may need to kno= w about Fedora Core and the PPC hardware platform.
PPC Hardware Requirements - This section lists the minimum PowerPC (PPC) hardware needed t= o install Fedora Core 4. - - - Minimum: PowerPC G3 / POWER4 - - - Fedora Core 5 supports only the =EF=BF=BD=EF=BF=BD=EF=BF= =BDNew World=EF=BF=BD=EF=BF=BD=EF=BF=BD generation of Apple Power Macintosh= , shipped circa 1999 onwards. - - - Fedora Core also supports IBM eServer pSeries, IBM RS/600= 0, Genesi Pegasos II, and IBM Cell Broadband Engine machines. - - - Recommended for text-mode: 233 MHz G3 or better, 64MiB RA= M. - - - Recommended for graphical: 400 MHz G3 or better, 128MiB R= AM. - -
- Hard Disk Space Requirements - This section lists the disk space required to install Fedora= Core . - 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 i= nstallation 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 /va= r/lib/rpm on the installed system. - In practical terms, this means that as little as an addition= al 90MB can be required for a minimal installation, while as much as an add= itional 175MB can be required for an "everything" installation. The complet= e packages can occupy over 7 GB of disk space. - Also, keep in mind that additional space is required for any= user data, and at least 5% free space should be maintained for proper syst= em operation. -
-
-
- PPC Installation Notes + Processor and Memory - - - - - - - /!\ - - Currently FC5 Test Release CD 1 and Res= cue ISOs do not boot on Mac hardware. See below on booting using boot.iso.= + Minimum CPU: PowerPC G3 / POWER4 + + + Fedora Core supports only the =EF=BF=BD=EF=BF=BD=EF=BF= =BDNew World=EF=BF=BD=EF=BF=BD=EF=BF=BD generation of Apple Power Macintosh= , shipped from circa 1999 onward. - - - The DVD or first CD of the installation set of Fedora Co= re 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: + Fedora Core also supports IBM eServer pSeries, IBM RS/= 6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines. + Recommended for text-mode: 233 MHz G3 or better, 128MiB= RAM. + + + Recommended for graphical: 400 MHz G3 or better, 256MiB= RAM. + + +
+ Hard Disk Space Requirements + The disk space requirements listed below represent the dis= k space taken up by Fedora Core after installation is complete. However, a= dditional disk space is required during installation to support the install= ation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on Installtion Disc 1) plus the size of= the files in /var/lib/rpm on the installed system. + In practical terms, additional space requirements may rang= e from as little as 90 MiB for a minimal installation to as much as an addi= tional 175 MiB for an "everything" installation. The complete packages can = occupy over 9 GB of disk space. + Additional space is also required for any user data, and a= t least 5% free space should be maintained for proper system operation. +
+
+
+ The Apple keyboard + The Option key on Apple systems is equivalent t= o the Alt key on the PC. Where documentation and the installer= refer to the Alt key, use the Option key. For so= me key combinations you may need to use the Option key in conj= unction with the Fn key, such as Option-Fn<= /code>-F3 to switch to virtual terminal tty3. +
+
+ PPC Installation Notes + Fedora Core Installation Disc 1 is bootable on supported har= dware. In addition, a bootable CD image appears in the images/= directory of this disc. These images will behave differently according to = your system hardware: + + Apple Macintosh + The bootloader should automatically boot the appropriate= 32-bit or 64-bit installer. + The default gnome-power-manager package inc= ludes power management support, including sleep and backlight level managem= ent. Users with more complex requirements can use the apmud p= ackage in Fedora Extras. Following installation, you can install apm= ud with the following command: - The bootloader should automatically boot the appropr= iate 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 fo= r yum. Following installation, apmud can be installed by running yum instal= l apmud. + su -c 'yum install apmud' 64-bit IBM eServer pSeries (POWER4/POWER5) - - - After using OpenFirmware = to boot the CD, the bootloader (yaboot) should automatically boot the 64-bi= t installer. - - + After using OpenFirmware to b= oot the CD, the bootloader (yaboot) should automatically boot the 64-bit in= staller. 32-bit CHRP (IBM RS/6000 and others) - - - After using OpenFirmware = to boot the CD, select the 'linux32' boot image at the 'boot:' prompt to st= art the 32-bit installer. Otherwise, the 64-bit installer is started, which= does not work. - - + After using OpenFirmware to b= oot the CD, select the linux32 boot image at the boot: prompt to start the 32-bit installer. Otherwise, the 64-bit installer= starts, which does not work. Genesi Pegasos II + At the time of writing, firmware with full support for I= SO9660 file systems is not yet released for the Pegasos. However, you can u= se the network boot image. At the OpenFirmware p= rompt, enter the command: - At the time of writing, firmware with full support f= or ISO9660 file systems is not yet released for the Pegasos. However, the n= etwork boot image can be used. At the OpenFirmwa= re prompt, enter the command: - - - boot cd: /images/netboot/ppc32.img - - - You also need to configure OpenFirmware on the Pegasos manually to make the installed Fedora Core sy= stem bootable. To do this, you need to set the boot-device and boot-file en= vironment variables appropriately. + boot cd: /images/netboot/ppc32.img + You must also configure OpenF= irmware on the Pegasos manually to make the installed Fedora Core system bo= otable. To do this, set the boot-device and boot-file environment variables appropriately. Network booting - - - There are combined images containing the installer k= ernel and ramdisk in the images/netboot/ directory of the install tree. The= se are intended for network booting with TFTP, but can be used in many ways= . - yaboot supports tftp booting for IBM eServer pSeries= and Apple Macintosh, the use of yaboot is encouraged over the netboot imag= es. - - + You can find combined images containing the installer ke= rnel and ramdisk in the images/netboot/ directory of the insta= llation tree. These are intended for network booting with TFTP, but can be = used in many ways. + + yaboot supports TFTP booting for IBM eServer pS= eries and Apple Macintosh. The Fedora Project encourages the use of = yaboot over the netboot images.
+
Index: ArchSpecificx86.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ArchSpecificx86.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ArchSpecificx86.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ArchSpecificx86.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,23 +1,21 @@ - +
Temp -
+
x86 Specifics for Fedora This section covers any specific information you may need to kno= w about Fedora Core and the x86 hardware platform.
x86 Hardware Requirements - The following information represents the minimum hardware requ= irements necessary to successfully install Fedora Core . - The compatibility/availability of other hardware components (s= uch as video and network cards) may be required for specific installation m= odes and/or post-installation usage. + In order to use specific features of Fedora Core during or af= ter installation, you may need to know details of other hardware components= such as video and network cards.
- CPU Requirements - This section lists the CPU specifications required by Fedora= Core . - The following CPU specifications are stated in terms of Inte= l 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. + Processor and Memory Requirements + The following CPU specifications are stated in terms of Inte= l processors. Other processors, such as those from AMD, Cyrix, and VIA that= are compatible with and equivalent to the following Intel processors, may = also be used with Fedora Core. - Minimum: Pentium-class =EF=BF=BD=EF=BF=BD=EF=BF=BD Fedo= ra Core is optimized for Pentium 4 CPUs, but also supports earlier CPUs (s= uch as Pentium, Pentium Pro, Pentium II, Pentium III, and including AMD and= VIA variants). This approach has been taken because Pentium-class optimiza= tions actually result in reduced performance for non-Pentium-class processo= rs, and Pentium 4 scheduling is sufficiently different (while making up the= bulk of today's processors) to warrant this change. + Minimum: Pentium-class =EF=BF=BD=EF=BF=BD=EF=BF=BD Fedo= ra Core is optimized for Pentium 4 CPUs, but also supports earlier CPUs su= ch as Pentium, Pentium Pro, Pentium II, Pentium III, and compatible AMD and= VIA processors. Fedora takes this approach because Pentium-class optimiza= tions actually result in reduced performance for non-Pentium class processo= rs. In addition, scheduling for Pentium 4 processors, which make up the bu= lk of today's processors, is sufficiently different to warrant this change.= Recommended for text-mode: 200 MHz Pentium-class or bet= ter @@ -31,35 +29,23 @@ Intel processors with Intel=EF=BF=BD=EF=BF=BD Extended = Memory 64 Technology (Intel=EF=BF=BD=EF=BF=BD EM64T) + + Minimum RAM for text-mode: 128MiB + + + Minimum RAM for graphical: 192MiB + + + Recommended for graphical: 256MiB +
Hard Disk Space Requirements - This section lists the disk space required to install Fedo= ra Core . - The disk space requirements listed below represent the dis= k space taken up by Fedora Core after the installation is complete. Howeve= r, additional disk space is required during the installation to support the= installation environment. This additional disk space corresponds to the si= ze of /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in /= var/lib/rpm on the installed system. - In practical terms, this means that as little as an additi= onal 90MB can be required for a minimal installation, while as much as an a= dditional 175MB can be required for an "everything" installation. The compl= ete packages can occupy over 7 GB of disk space. - Also, keep in mind that additional space is required for a= ny user data, and at least 5% free space should be maintained for proper sy= stem operation. -
-
- Memory Requirements - This section lists the memory required to install Fedora C= ore . - This list is for 32-bit x86 systems: - - - Minimum for text-mode: 64MB - - - Minimum for graphical: 192MB - - - Recommended for graphical: 256MB - - + The disk space requirements listed below represent the dis= k space taken up by Fedora Core after the installation is complete. Howeve= r, additional disk space is required during the installation to support the= installation environment. This additional disk space corresponds to the si= ze of /Fedora/base/stage2.img on Installation Disc 1 plus the = size of the files in /var/lib/rpm on the installed system. + In practical terms, additional space requirements may rang= e from as little as 90 MiB for a minimal installation to as much as an addi= tional 175 MiB for an "everything" installation. The complete packages can= occupy over 9 GB of disk space. + Additional space is also required for any user data, and a= t least 5% free space should be maintained for proper system operation.
-
- x86 Installation Notes - Installer package screen selection interface is being redesign= ed in the Fedora development version. Fedora Core does not provide an opti= on to select the installation type such as Personal Desktop, Workstation, S= erver and custom. -
Index: ArchSpecificx86_64.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ArchSpecificx86_64.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ArchSpecificx86_64.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ArchSpecificx86_64.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,43 +1,54 @@ - +
Temp -
+
x86_64 Specifics for Fedora This section covers any specific information you may need to kno= w about Fedora Core and the x86_64 hardware platform.
x86_64 Hardware Requirements - The following information represents the minimum hardware requ= irements necessary to successfully install Fedora Core . - The compatibility/availability of other hardware components (s= uch as video and network cards) may be required for specific installation m= odes and/or post-installation usage. + In order to use specific features of Fedora Core during or af= ter installation, you may need to know details of other hardware components= such as video and network cards.
- Hard Disk Space Requirements - This section lists the disk space required to install Fedora= Core . - 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 i= nstallation 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 /va= r/lib/rpm on the installed system. - In practical terms, this means that as little as an addition= al 90MB can be required for a minimal installation, while as much as an add= itional 175MB can be required for an "everything" installation. The complet= e packages can occupy over 7 GB of disk space. - Also, keep in mind that additional space is required for any= user data, and at least 5% free space should be maintained for proper syst= em operation. + Memory Requirements + This list is for 64-bit x86_64 systems: + + + Minimum RAM for text-mode: 128MiB + + + Minimum RAM for graphical: 256MiB + + + Recommended RAM for graphical: 512MiB + +
- Memory Requirements - This section lists the memory required to install Fedora C= ore . - This list is for 64-bit x86_64 systems: - - - Minimum for text-mode: 128MB - - - Minimum for graphical: 256MB - - - Recommended for graphical: 512MB - - + Hard Disk Space Requirements + The disk space requirements listed below represent the dis= k space taken up by Fedora Core after the installation is complete. Howeve= r, additional disk space is required during the installation to support the= installation environment. This additional disk space corresponds to the si= ze of /Fedora/base/stage2.img on Installation Disc 1 plus the = size of the files in /var/lib/rpm on the installed system. + In practical terms, additional space requirements may rang= e from as little as 90 MiB for a minimal installation to as much as an addi= tional 175 MiB for an "everything" installation. The complete packages can= occupy over 9 GB of disk space. + Additional space is also required for any user data, and a= t least 5% free space should be maintained for proper system operation.
-
- x86_64 Installation Notes - No differences installing for x86_64. + RPM Multiarch Support on x86_64 + + RPM supports parallel insta= llation of multiple architectures of the same package. A default package l= isting such as rpm -qa might appear to include duplicate packa= ges, since the architecture is not displayed. Instead, use the repoq= uery command, part of the yum-utils package in Fedora E= xtras, which displays architecture by default. To install yum-utils<= /code>, run the following command: + + + su -c 'yum install yum-utils' + + + To list all packages with their architecture using rpm= , run the following command: + + + rpm -qa --queryformat "%{name}-%{version}-%{release}.%= {arch}\n" + + + +
+
Index: BackwardsCompatibility.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/BackwardsCompatibility.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- BackwardsCompatibility.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ BackwardsCompatibility.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,12 +1,20 @@ - +
- Backwards Compatibility + Temp -
+
+ Docs/Beats/BackwardsCompatibility +
Backwards Compatibility - Fedora includes several system libraries and software for comp= atibility with older software. These software are part of the "Legacy Softw= are Development" group which are not installed by default. Users who requir= e this functionality can select this group during installation or run the f= ollowing the command post-installation. - yum groupinstall "Legacy Software Development" + Fedora Core provides legacy system libraries for compatibility= with older software. This software is part of the Legacy Software Development group, which is not installed by d= efault. Users who require this functionality may select this group either d= uring installation, or after the installation process is complete. To insta= ll the package group on a Fedora system, use Applications=3D>Add/= Remove Software, Pirut or e= nter the following command in a terminal window: + + + su -c 'yum groupinstall "Legacy Software Development"' + + + Enter the password for the root account when prom= pted. +
Index: Colophon.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Colophon.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Colophon.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Colophon.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,26 +1,47 @@ - +
Temp -
- Colophon - - Draft - - This is a draft, so it is incomplete and imperfect. = - - +
+ Docs/Beats/Colophon + + + + + + + + + +
+
+ + + + + + + {i} + + + Draft + +
+ This is a draft, so it is an incomplete and imperfect= list. +
+
+
About the Colophon - As we use the term, colophon means: + As we use the term, a colophon: - A way to recognize contributors, while providing accounta= bility. + recognizes contributors and provides accountability, and = - Explain tools and production methods. + explains tools and production methods.
@@ -29,94 +50,97 @@ - An= drew Martynov (translator, Russian) + AndrewMartynov (transla= tor, Russian) - Anth= ony Green (beat writer) + AnthonyGreen (beat writer= ) - Bob Jen= sen (beat writer) + BobJensen (beat writer, edit= or, co-publisher) - Dave = Malcolm (beat writer) + DaveMalcolm (beat writer) = - Da= vid Woodhouse (beat writer) + DavidWoodhouse (beat wr= iter) - Franc= esco Tombolini (translator, Italian) + FrancescoTombolini = (translator, Italian) - Gavin = Henry (beat writer) + GavinHenry (beat writer) - Jens= Petersen (beat writer) + JensPetersen (beat writer= ) - Joe Orto= n (beat writer) + JoeOrton (beat writer) - Josh= Bressers (beat writer) + JoshBressers (beat writer= ) - Karst= en Wade (beat writer, editor, publisher) + KarstenWade (beat writer, = editor, co-publisher) - = Luya Tshimbalanga (beat writer) + LuyaTshimbalanga (bea= t writer) - Pat= rick Barnes (beat writer, editor) + PatrickBarnes (beat writ= er, editor) - - - Paul W. Fri= elds (tools, editor) - - Rah= ulSundaram (beat writer, editor) + PaulWFrields (tools, edit= or) - Seki= neTatsuo (translator, Japanese) + RahulSundaram (beat writ= er, editor) - Stev= eDickson (beat writer) + SekineTatsuo (translator,= Japanese) - Stua= rtElliss (editor) + SteveDickson (beat writer= ) - Thomas= Graf (beat writer) + StuartEllis (editor) - Tom= myReynolds (tools) + ThomasGraf (beat writer) - = YoshinariTakaoka (translator, tools) + TommyReynolds (tools) - YuanYij= un (translator, Simplified Chinese) + YoshinariTakaoka (tra= nslator, tools) + + + + YuanYijun (translator, Simpl= ified Chinese)
+
+ Production Methods + Beat writers produce the release notes directly on the Fedora = Project Wiki. They collaborate with other subject matter experts during th= e test release phase of Fedora Core to explain important changes and enhanc= ements. The editorial team ensures consistency and quality of the finished= beats, and ports the Wiki material to DocBook XML in a revision control repository. At this point, the team of trans= lators produces other language versions of the release notes, and then they= become available to the general public as part of Fedora Core. The public= ation team also makes them, and subsequent errata, available via the Web. <= /para> +
Index: DatabaseServers.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/DatabaseServers.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- DatabaseServers.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ DatabaseServers.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,16 +1,47 @@ - +
Temp -
- Database Servers - - - - - No changes of note. +
+ Docs/Beats/DatabaseServers +
+ MySQL + Fedora now provides MySQL= 5.0. For a list of the enhancements provided by this version, refer to = http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html. + For more information on upgrading databases from previous rele= ases of MySQL, refer to the MySQL web site at http://dev.mysql.com/doc/refman/5.0/en= /upgrade.html. +
+
+ PostgreSQL + This release of Fedora includes Post= greSQL 8.1. For more information on this new version, refer to <= ulink url=3D'http://www.postgresql.org/docs/whatsnew/'>http://www.postgresq= l.org/docs/whatsnew/. + + + + + + + + + +
+
+ + + + + + + {*} + + + Upgrading Databases + +
+ Fedora Core 4 provided version 8.0 of PostgreSQL. I= f you upgrade an existing Fedora system with a PostgreSQL database, you mus= t upgrade the database to access the data. +
+
+
+ To upgrade a database from a previous version of PostgreSQL, f= ollow the procedure described at http://www.postgresql.org/docs/8= .1/interactive/install-upgrading.html. +
Index: Desktop.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Desktop.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Desktop.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Desktop.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,32 +1,52 @@ - +
Temp -
- Desktop - 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. - The current test release has GNOME 2.12.1, together with some = previews of technology from the forthcoming GNOME 2.14. Feedback on these p= ackages is especially appreciated. - - - gnome-power-manager: GNOME Power Manager is a session dae= mon for the GNOME desktop environment that makes it easy to manage your lap= top or desktop system. It takes advantage of HAL (which provides a hardware= abstraction layer) and DBUS ( Inter Process Communication software) writt= en and maintained by Fedora Core developers. - - - gnome-screensaver: Provides a integrated user interface t= o screensavers and the lock screen dialog. - - - memory optimizations in the fontconfig and shared-mime-in= fo packages. These now use shared memory-mapped caches for this data. - - - GNOME 2.12 has removed the terminal option from the desktop co= ntext menu. nautilus-open-terminal in Fedora Extras repository provides a e= nhanced replacement for those who require it. You can install it using the = following command. - yum install nautilus-open-terminal - Screensavers except the one providing a blank screen are not i= nstalled by default from Fedora Core 4 onwards. Many of the screensavers ar= e found to be offensive or known to abruptly terminate the graphical interf= ace, in particular some of the OpenGL animated ones provided within xscreen= saver-gl-extras package. Some of them also provide a unexpected suprise to = users. Users who need it can install it using the following command. - yum install xscreensaver-extras xscreensaver-gl-extras - - system-config-mouse Removed - -system-config-mouse configuration utility has been dropped from this relea= se since synaptic and 3 button mouse configuration is being done automatica= lly during installation and serial mice are not formally supported in Fedor= a Core anymore. - +
+ Fedora Desktop + GNOME 2.14 (or a release candidate) and KDE 3.5.1 are included i= n Fedora Core . The following list includes notable changes to the desktop= interface in this release. + + + + gnome-power-manager + + + + The GNOME Power Manager is a session daemon for the GNOME desktop environment that makes it ea= sy to manage your laptop or desktop system. It takes advantage of HAL (whic= h provides a hardware abstraction layer) and DBUS (Inter Process Communica= tion software) written and maintained by Fedora Core developers. + + + + + + gnome-screensaver + + + + The GNOME Screensaver provides a integrated user interface to screensavers and the lock screen= dialog. + + + + + Memory optimizations in the fontconfig and shared-mime-info= packages. These now use shared memory-mapped caches for this data. + + + Starting with GNOME 2.12, the terminal option has been remo= ved from the desktop context menu. The nautilus-open-terminal = package in Fedora Extras provides a enhanced replacement for those who requ= ire it. You can install it with the following command. + + + yum install nautilus-open-terminal + + + + + In Fedora Core 5, only a small assortment of screensavers i= s installed by default. Some users find certain screensavers unpleasant, a= nd other screensavers may abruptly terminate the graphical interface. This= tends to happen more often with OpenGL animated screensavers provided with= in the xscreensaver-gl-extras package, when used with poorly-s= upported video hardware. To install these extra screensavers, run the foll= owing command: + + + yum install xscreensaver-extras xscreensaver-gl-extras= + + + +
Index: DevelTools.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/DevelTools.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- DevelTools.xml 17 Feb 2006 00:49:51 -0000 1.2 +++ DevelTools.xml 28 Feb 2006 17:25:26 -0000 1.3 @@ -1,10 +1,10 @@ - +
Temp -
+
Developer Tools This section covers various developer tools. @@ -21,14 +21,12 @@ Eclipse Development Environment - Eclipse 3.1M6 has been compiled as a native application. = + Eclipse 3.1M6 is compiled as a native application. The C Development Tool (CDT) has been included.
-
Index: DevelToolsGCC.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/DevelToolsGCC.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- DevelToolsGCC.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ DevelToolsGCC.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,26 +1,26 @@ - +
Temp -
+
GCC Compiler Collection - This release of Fedora has been built using GCC 4.1, which is in= cluded with the distribution. + This release of Fedora has been built with GCC 4.1 as the system= compiler, which is included with the distribution.
Caveats - GDB 6.1 or newer is needed to debug binaries unless compi= led using the -fno-var-tracking compilation option. + You need GDB 6.1 or newer to debug binaries, unless they = are compiled using the -fno-var-tracking compilation option. <= /para> - The -fwritable-strings option is no lo= nger accepted. + The -fwritable-strings option is no longer a= ccepted. - English-language diagnostic messages now use Unicode quot= es; if you cannot read this, set your LC_CTYPE environme= nt variable to C or change your terminal emulator. + English-language diagnostic messages now use Unicode quot= es. If you cannot read this, set your LC_CTYPE environment va= riable to C or change your terminal emulator. - The specs file is no longer installed = on most systems. Ordinary users will not notice, but developers who need to= alter the file can use the -dumpspecs option to generat= e the file for editing. + The specs file is no longer installed on mos= t systems. Ordinary users will not notice, but developers who need to alter= the file can use the -dumpspecs option to generate the file f= or editing.
@@ -38,13 +38,13 @@ Language Extensions - A sentinel attribute has been added so that the compile= r will now issue a warning if a function such as execl(char *path,= const char *arg, ...), which requires a NULL list terminator is = missing the NULL. + The new sentinel attribute causes the compiler to issue= a warning if a function such as execl(char *path, const char *arg, .= ..), which requires a NULL list terminator, is missing the NULL. - The cast-as-lvalue, conditi= onal-expression-as-lvalue, and compund-expression-as-lva= lue extensions have been removed. + The cast-as-lvalue, conditional-expr= ession-as-lvalue, and compund-expression-as-lvalue exte= nsions have been removed. - The #pragma pack() semantics have be= en brought closer to those used by other compilers. + The #pragma pack() semantics are now close= r to those used by other compilers. Taking the address of a variable declared with the regi= ster modifier now generates an error instead of a warning. @@ -53,10 +53,10 @@ Arrays of incomplete element types now generate an erro= r. This implies no forward reference to structure definitions. - The basic compiler, without any optimization (= -O0), has been measured as much as 25% faster in real-world code.= + The basic compiler, without any optimization (-O0= ), has been measured as much as 25% faster in real-world code. - Libraries may now contain function-scope static variabl= es in multi-threaded programs. The -fno-threadsafe-statics can be used by embedded developers to turn off this feature, but ordinar= y users should never do this. + Libraries may now contain function-scope static variabl= es in multi-threaded programs. Embedded developers can use the -fno-t= hreadsafe-statics to turn off this feature, but ordinary users shoul= d never do this.
Index: Entertainment.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Entertainment.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Entertainment.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Entertainment.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,16 +1,11 @@ - +
Temp -
+
Games and Entertainment - Fedora Core and Fedora Extras provide a selection of games that = cover a variety of genres. By default, Fedora Core includes a small packag= e of games for GNOME (called gnome-games). For a list o= f other games that are available for installation through yum, open a terminal and enter the following command: - yum groupinfo "Games and Entertainment" - For help using yum to install the assorted ga= me packages, refer to the guide available at: - - http://fedora.redh= at.com/docs/yum/ - + Fedora Core and Fedora Extras provide a selection of games that = cover a variety of genres. By default, Fedora Core includes a small packag= e of games for GNOME (called gnome-games). To install other g= ames available from Fedora Core and Fedora Extras, select Applica= tions>Add/Remove Software from the main des= ktop menu.
Index: Extras.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Extras.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Extras.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Extras.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,17 +1,143 @@ - +
Temp -
- Fedora Extras Repository - Fedora Extras is part of the larger Fedora Project and is a volu= nteer-based community effort to create a repository of packages that compli= ment Fedora Core. The Fedora Extras repository is enabled by default. - You can lean more about Fedora Extras from - http://fedorapro= ject.org/wiki/Extras. - - If you would like to install any software available from Fedora = extras you can use yum. - yum install <packagename> - Where <packagename> is the name of the package you want to in= stall. For example, if you wanted to install the abiword package, the comma= nd yum install abiword automatically installs the package and = all dependencies. +
+ Fedora Extras +
+ Using the Repository + Fedora Extras provides a repository of packages that complemen= t Fedora Core. This volunteer-based community effort is part of the larger = Fedora Project. + + + + + + + + + +
+
+ + + + + + + {i} + + + Fedora Extras are Available by= Default + +
+ Fedora systems automatically use both the Fedora Co= re and Fedora Extras repositories to install and update software. +
+
+
+ To install software from either the Core or Extras repositorie= s, choose Applications > Add/Remove Software. Enter th= e root password when prompted. Select the software you require= from the list, and choose Apply. + Alternatively, you may install software with the yum command-line utility. For example, this command automatically installs = the abiword package, and all of the dependencies that are requ= ired: + + + su -c 'yum install abiword' + + + Enter the root password when prompted. +
+
+ About Fedora Extras + As of the release of Fedora Core 5, there are approximately 2,= 000 packages in Fedora Extras, built from 1,350 source packages. The follow= ing list includes some popular and well-known applications that are maintai= ned by community members in Fedora Extras: + + + + abiword - elegant word-processing application + + + + balsa - lightweight e-mail reader + + + + bash-completion - advanced command-line completio= n for power users + + + + bluefish - HTML editor + + + + clamav - open source anti-virus scanner for serve= rs and desktops + + + + fuse - tool for attaching non-standard devices an= d network services as directories + + + + fwbuilder - graphical utility for building Linux = and Cisco firewall rulesets + + + + gaim-guifications - enhancements to the Gaim Inst= ant Messenger + + + + gdesklets - widgets for the GNOME desktop + + + + gnumeric - powerful spreadsheet application + + + + inkscape - illustration and vector drawing applic= ation + + + + koffice - complete office suite for the KDE deskt= op + + + + mail-notification - alerts you as new mail arrive= s + + + + mediawiki - the Wikipedia solution for collaborat= ive websites + + + + nautilus-open-terminal - extension to the GNOME f= ile manager + + + + pan - the Usenet news reader + + + + revelation - password management utility + + + + scribus - desktop publishing (DTP) application + + + + xfce - lightweight desktop environment + + + + xmms - the popular audio player + + + lots of Perl and Python tools and libraries + + + ...and much more! + + + Is your favorite open source application missing from Fedora E= xtras? Package the application as an RPM, and submit it for review to Fedo= ra Extras. After a successful review, import it to Extras and you can maint= ain it there. If you don't know how to create RPM packages, there are many = other ways to get involved in Fedora Extras and help drive it forward. + To learn more about how to use Fedora Extras or how to get inv= olved, refer to http://= fedoraproject.org/wiki/Extras. +
Index: Feedback.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Feedback.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Feedback.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Feedback.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,31 +1,54 @@ - +
Temp -
- Feedback - Thanks for your interest in helping us with the release notes by= providing feedback. This section explains how you can give that feedback.= -
- Release Notes Feedback Procedure - If you feel that these release notes could be improved in some= way, you can provide feedback directly to the beat writers. Here are seve= ral ways, in order of preference: - - - Edit content directly at Docs/= Beats - - - - Email = relnotes(a)fedoraproject.org - - - - Fill out this pre= -filled bug request template - - - - A release note = beat is an area of the release notes that is the responsibility of = one or more content contributors to oversee. - Thank you (in advance) for your feedback! -
+
+ Providing Feedback for Release Notes + + + + + + + + + +
+
+ + + + + + + (!) + + + Feedback for Release Notes Only<= /emphasis> + +
+ This section concerns feedback on the release notes t= hemselves. To provide feedback on Fedora software or other system elements= , please refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests. +
+
+
+ Thanks for your interest in giving feedback for these release no= tes. If you feel these release notes could be improved in any way, you can= provide your feedback directly to the beat writers. Here are several ways= to do so, in order of preference: + + + Edit content directly at http://fedoraproject.org/wiki/Docs/Beats + + + + Fill out a bug request using this template: http://tinyurl.com/8lryk + + + + Email re= lnotes(a)fedoraproject.org + + + + A release note beat is an area of the release notes that is the = responsibility of one or more content contributors to oversee. For more if= normation about beats, refer to http://fedoraproject.org/wiki/DocsProject/= ReleaseNotes/Beats. + Thank you (in advance) for your feedback!
Index: FileServers.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/FileServers.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- FileServers.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ FileServers.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,23 +1,44 @@ - +
Temp -
+
File Servers - 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. + This section refers to file transfer and sharing servers. Refer = to http:= //fedoraproject.org/wiki/Docs/Beats/WebServers and http://fedoraproject.org/wiki= /Docs/Beats/Samba for information on HTTP (Web) file transfer and S= amba (Windows) file sharing services.
Netatalk (Macintosh Compatibility) - This section contains information related to Netatalk, a suite= of software that enables Linux to interact with Macintosh systems using th= e AppleTalk network protocols. - - -Upgrading from Netatalk version 1 to version 2 may result in data loss. <= /title> - <para>Version 2 of Netatalk uses a different method to store file = resource forks from the previous version, and may require a different file = name encoding scheme. Please read the documentation and plan your migration= before upgrading. </para> - </warning> - <para>Upgrade information is available directly from the Netatalk = site at <ulink url=3D'http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.= html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html</ulink>. - </para> - <para>The documentation is also included in the netatalk package. = Refer to either <command>/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade= .html</command>, or <command>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Man= ual.pdf</command> (numbered page 25, document page 33). </para> + <para>Fedora includes version 2 of Netatalk, a suite of software tha= t enables Linux to interact with Macintosh systems using the AppleTalk netw= ork protocols. </para> + <itemizedlist> + <listitem> + <table> + <caption/> + <tr> + <td> + <para> + <inlinemediaobject> + <imageobject> + <imagedata width=3D'15' fileref=3D'/wiki/ntheme/img/= alert.png' depth=3D'15'/> + </imageobject> + <textobject> + <phrase>/!\</phrase> + </textobject> + </inlinemediaobject> + <emphasis role=3D'strong'>Use Caution When Upgrading</em= phasis> + </para> + </td> + </tr> + <tr> + <td> + <para> You may experience data loss when upgrading from Ne= tatalk version 1 to version 2. </para> + </td> + </tr> + </table> + </listitem> + </itemizedlist> + <para>Version 2 of Netatalk stores file resource forks using a diffe= rent method from the previous version, and may require a different file nam= e encoding scheme. Please read the documentation and plan your migration be= fore upgrading. Refer to the upgrade information available directly from t= he Netatalk site at <ulink url=3D'http://netatalk.sourceforge.net/2.0/htmld= ocs/upgrade.html'>http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html= </ulink>. </para> + <para>The documentation is also included in the <code>netatalk</code= > package. Refer to either <code>/usr/share/doc/netatalk-2.0.2/doc/htmldocs= /upgrade.html</code> or <code>/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Ma= nual.pdf</code> (numbered page 25, document page 33). </para> </section> </section> </article> Index: FileSystems.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/FileSystems.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- FileSystems.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ FileSystems.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,16 +1,36 @@ <?xml version=3D'1.0' encoding=3D'UTF-8'?> -<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.= docbook.org/xml/4.4/docbookx.dtd"> +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V4.4//EN" "http://www.docb= ook.org/xml/4.4/docbookx.dtd"> <article> <articleinfo> <title>Temp -
- File Systems - - - - - No changes to report. +
+ Docs/Beats/FileSystems + + + + + + + + + + +
+
+ + + + + + + /!\ + + REMOVE ME Before Publishing - Beat Commen= t +
+ This page is a stub for content. If you have a contribut= ion for this release notes beat for the test release of Fedora Core, add it= to this page or create a sub-page. +
+ Beat writers: this is where you want to fill in with ins= tructions about how to post relevant information. Any questions that come = up can be taken to a bugzilla report for discussion to resolution, or to fe= dora-docs-list for wider discussions. +
Index: I18n.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/I18n.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- I18n.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ I18n.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,12 +1,77 @@ - +
Temp -
+
Internationalization (i18n) + This section includes information related to the support of vari= ous languages under Fedora Core. +
+ Input Methods + SCIM (Simple Common Input Method) has replaced IIIMF as the in= put method system for Asian and other languages in Fedora Core in this rele= ase. SCIM uses Ctrl-Space as the default trigger key to toggl= e on and off the input method, though it is easy to change the hotkey or ad= d hotkeys with the SCIM setup configuration tool. When scim-anthy is active Japanese users can now use the Zenkaku_Hankaku = key to toggle between Japanese and ASCII input. +
+ Installation + SCIM should be installed and run by default for Asian langua= ge desktops. Otherwise the required packages can be installed using the la= nguage support section of the package manager or running: + + + su -c 'yum install <SCIM-IMEs>' + + + where <SCIM-IMEs> should be replaced by one = or more of the following: + + + Japanese: scim-anthy + + Korean: scim-hangul + + Simplified Chinese: scim-pinyin scim-tables-chines= e + + Traditional Chinese: scim-chewing scim-tables-chin= ese + + Indian and other languages: scim-m17n m17n-db-<= language> + + + + You also need fonts for the language. The font packages are= named fonts-<language>, where <language> i= s one of arabic, bengali, chinese, <= code>gujarati, hebrew, hindi, japane= se, korean, punjabi, tamil. <= /para> + If your desktop is not running in an Asian locale, to activa= te it in your user account, run these commands, then logout and login again= to your desktop. + + + mkdir ~/.xinput.d ln -s /etc/X11/xinit/xinput.d/scim ~= /.xinput.d/default + + +
+
+ SCIM applet and toolbar + When SCIM is running, an applet icon appears in the notifica= tion area of the desktop panel. The icon is a grey keyboard icon when SCIM= is inactive, and an Input Method Engine (IME) icon when it is active. Whe= n SCIM is active, by default the SCIM input method toolbar with status info= rmation also appears. + Clicking the left mouse button on the applet activates a SCI= M language switching menu for changing the current Input Method Engine. Th= e menu only appears when an application using the Input Method has focus. = Clicking the right mouse button on the applet or SCIM toolbar activates the= setup menu. +
+
+ SCIM configuration + You can configure SCIM and IMEs using the setup configuratio= n tool available from the setup menu. In the IME general configuration pane= , you can select which languages or IMEs appear on the language switching m= enu. +
+
+ New conversion engines -SCIM has replaced IIIMF as the language input framework in Fedora Core in = this release. + anthy, a new Japanese conversion engine replaces th= e old Canna server system, and libchewing, a new Traditional C= hinese conversion engine, has been added. +
+
+
+ Fonts + Support is now available for synthetic emboldening of fonts th= at do not have a bold face. + New fonts for Chinese have been added: AR PL ShanHeiSun Uni (<= code>uming.ttf) and AR PL ZenKai Uni (ukai.ttf). The d= efault font is AR PL ShanHeiSun Uni, which contains embedded bitmaps. If yo= u prefer outline glyphs you can put the following section in your ~/.= font.conf file: + <fontconfig><match target=3D"font"><test name=3D"fa= mily" compare=3D"eq"><string>AR PL ShanHeiSun Uni</string></test>&= lt;edit name=3D"embeddedbitmap" mode=3D"assign"><bool>false</bool><= ;/edit></match></fontconfig> + + +
+
+ gtk2 IM submenu + The Gtk2 context menu IM submenu no longer appears by default.= You can enable it on the command line with the following command: + + + gconftool-2 --type bool --set '/desktop/gnome/interface/= show_input_method_menu' true + + +
Index: Installer.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Installer.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Installer.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Installer.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,69 +1,182 @@ - +
Temp -
+
Installation-Related Notes - This section outlines those issues that are related to Anaconda = (the Fedora Core installation program) and installing Fedora Core in gener= al. - If you intend to download the Fedora Core 5 Test 2 DV= D ISO image, keep in mind that not all file downloading tools can accommoda= te 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. = - Wget 1.9.1-16 and above, curl and ncftpget file downl= oading tools do not have this limitation, and can successfully download fil= es larger than 2GB. - Bittorrent is another method for downloading large fil= es. For information about obtaining and using the torrent file refer to thi= s website: + This section outlines those issues that are related to Anaconda (the Fedora Core installation program)= and installing Fedora Core in general. + + + + + + + + + +
+
- http://to= rrent.fedoraproject.org/ + + + + + + {i} + + + Downloading Large Files +
+ If you intend to download the Fedora Core DVD ISO im= age, keep in mind that not all file downloading tools can accommodate files= larger than 2GB in size. wget 1.9.1-16 and above, curl<= /code> and ncftpget do not have this limitation, and can succe= ssfully download files larger than 2GB. BitTorren= t is another method for downloading large files. For information= about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/ . +
+
+
+
- Installer Notes + Anaconda Notes - The Fedora Core installation program has the ability to te= st the integrity of the installation media. It works with the CD, DVD, hard= drive ISO, and NFS ISO installation methods. Fedora Project recommends tha= t you test all installation media before starting the installation process,= and before reporting any installation-related bugs (many of the bugs repor= ted are actually due to improperly-burned CDs). To use this test, type linu= x mediacheck at the boot: prompt. - The mediacheck function is highly sensitive, and may report = some usable discs as faulty. This result is often caused by disc writing so= ftware that does not include padding when creating discs from ISO files. Fo= r best results with the mediacheck, boot with the option: - linux ide=3Dnodma - Use the sha1sum utility to verify discs before carrying out = an installation. This test accurately identifies discs that are not valid o= r identical to the ISO image files. + + Anaconda tests the integrit= y of installation media by default. This function works with the CD, DVD, h= ard drive ISO, and NFS ISO installation methods. The Fedora Project recomme= nds that you test all installation media before starting the installation p= rocess, and before reporting any installation-related bugs. Many of the bu= gs reported are actually due to improperly-burned CDs. To use this test, t= ype linux mediacheck at the boot: prompt. + The mediacheck function is highly sensitive, an= d may report some usable discs as faulty. This result is often caused by di= sc writing software that does not include padding when creating discs from = ISO files. For best results with mediacheck, boot with the fol= lowing option: + linux ide=3Dnodma + Use the sha1sum utility to verify discs before = carrying out an installation. This test accurately identifies discs that ar= e not valid or identical to the ISO image files. + + + + + + + + + +
+
+ + + + + + + (!) + + + BitTorrent Automatically Ver= ifies File Integrity + +
+ If you use BitTorrent, any files you download are automatically validated. If your fil= e completes downloading, you do not need to check it. Once you burn your C= D, however, you should still use mediacheck. +
+
+
- Memory testing may be performed prior to installing Fedora = Core by entering memtest86 at the boot: prompt. This causes the Memtest86 s= tandalone memory testing software to run. Memtest86 memory testing continue= s until the Esc key is pressed. - - Boot From Installation CD 1 - You must boot from CD-ROM 1 (or a rescue CD-ROM) = in order to use this feature. - + You may perform memory testing before you install Fedora Co= re by entering memtest86 at the boot: prompt. Th= is option runs the Memtest86 standalon= e memory testing software in place of Anaconda. Memtest86 memory testing con= tinues until the Esc key is pressed. + + + + + + + + + +
+
+ + + + + + + {i} + + + + Memtest86 Availability + +
+ You must boot from Installation Disc 1 or a rescu= e CD in order to use this feature. +
+
+
- Fedora Core supports graphical FTP and HTTP installations.= However, due to the necessity of containing the installer image in RAM, on= ly systems with more than 128MB of RAM (or systems booted from CD-ROM 1, wh= ich contains the installer image) can use the graphical installer. Systems = with 128MB or less will continue to use the text-based installer. + Fedora Core supports graphical FTP and HTTP installations.= However, the installer image must either fit in RAM or appear on local sto= rage such as Installation Disc 1. Therefore, only systems with more than 1= 92MiB of RAM, or which boot from Installation Disc 1, can use the graphical= installer. Systems with 192MiB RAM or less will fall back to using the tex= t-based installer automatically. If you prefer to use the text-based instal= ler, type linux text at the boot: prompt.
- Changes In The Installer + Changes in Anaconda - Support of yum for dependancy solver backend has been add= ed and additional repositories are expected to be supported during installa= tion in a future release. + The installer checks hardware capability and installs eit= her the uniprocessor or SMP (Symmetric Multi Processor) kernel as appropria= te in this release. Previous releases installed both variants and used the = appropriate one as default. + + + + Anaconda now supports ins= tallation on several IDE software RAID chipsets using dmraid. = To disable this feature, add the nodmraid option at the boot: prompt. For more information, refer to http://fedoraproject.org/wiki/DmraidSt= atus . + + + + + + + + + + + + +
+
+ + + + + + + /!\ + + + Do not boot only half of a= dmraid RAID1 (mirror) + +
+ Various situations may occur that cause d= mraid to break the mirror, and if you boot in read/write mode into o= nly one of the mirrored disks, it causes the disks to fall out of sync. No= symptoms arise, since the primary disk is reading and writing to itself. = But if you attempt to re-establish the mirror without first synchronizing t= he disks, you could corrupt the data and have to reinstall from scratch wit= hout a chance for recovery. +
+ If the mirror is broken, you should be able to = resync from within the RAID chipset BIOS or by using the dd co= mmand. Reinstallation is always an option. +
+
+
+
+ + Serial mice are no longer formally supported in Anaconda or Fedora Core. - The installer checks the hardware capability and installs= either the uniprocessor or SMP (Symmetric Multi Processor) kernel as appro= priate in this release. Previous releases installed both the variants and u= sed the appropriate one as default. + The disk partitioning screen has been reworked to be more= user friendly. - Partition setting has been reworked to be more user frien= dly + The package selection screen has been revamped. The new,= simplified screen only displays the optional groups Office and P= roductivity (enabled by default), Software Development= , Web Server, and Virtualization = (Xen). However, you may still fully customize your package sele= ction. Refer to http://fedoraproject.org/wiki/Anaconda/PackageSelection for more details. - Remote logging via syslog is supported in this release. p= ass syslog=3Dhost:port (port is optional) at the boot prompt. + Firewall and SELinux configuration has been moved to the = Setup Agent (firstboot), the final phase = of the graphical installation process. - Firewall/SELinux configuration has been moved to the fina= l installation phase called 'firstboot'. + The timezone configuration screen now features zooming ar= eas on the location selection map. - Rendering of html pages is now done using the gtkhtml wid= get for better capability. + This release supports remote logging via syslog. To use this feature, add the option syslog=3Dhost:port at= the boot prompt. The :port specifier is optional. - Kickstart has been refactored into its own package - pyki= ckstart - containing parser and writers. As a result of this change validat= ion and extending kickstart is now much easier. + + Anaconda now renders rele= ase notes with the gtkhtml widget for better capability. - Serial mice is not formally supported in the installer an= d in Fedora Core anymore. + Kickstart has been refactored into its own package, pykickstart, and contains a parser and writers. As a result of this= change, validation and extension is now much easier. - Full support of dmraid (disabled by default). To enable t= hat feature, add this option to the boot command line: - dmraid - For more information, check the DmraidStatus page. + + Anaconda now uses y= um as the backend for solving package dependencies. Additional repo= sitories such as Fedora Extras are expected to be supported during installa= tion in a future release.
@@ -71,38 +184,62 @@ Installation Related Issues - Certain hardware configurations (particularly those with = LCD displays) may experience problems while starting the Fedora Core instal= lation program. In these instances, restart the installation, and add the "= nofb" option to the boot command line. - - CJK Language Support - Chinese, Japanese, and Korean graphical install= ations started using the "nofb" option will start in English, and then swit= ch to the appropriate language once the graphical phase of the installation= process begins. - - - Some Sony VAIO notebook systems may experience problems i= nstalling Fedora Core from CD-ROM. If this happens, restart the installatio= n process and add the following option to the boot command line: + + pci=3Doff ide1=3D0x180,0x386 - This option allows the installation to proceed normally; a= ny devices not detected due to the use of this option are configured the fi= rst time Fedora Core is booted. + + + Installation should proceed normally, and any devices not = detected are configured the first time Fedora Core is booted. + + + Not all IDE RAID controllers are supported. If your RAID = controller is not yet supported by dmraid, you may combine dri= ves into RAID arrays by configuring Linux software RAID. For supported cont= rollers, configure the RAID functions in the computer BIOS.
-
- Upgrading Related Issues - Refer to http://fedoraproject.org/wiki/DistributionUpgrades pag= e for detailedrecommended procedures for upgradation of Fedora. - In general, fresh installations are to be recommended over upg= rades, particularly for systems with software from add-on repositories inst= alled. If third party packages are installed on the system, they might not= work as expected. If an upgrade is attempted, the following may be helpfu= l. + Upgrade Related Issues + Refer to http://fedoraproject.org/wiki/DistributionUpgrades for= detailed recommended procedures for upgrading Fedora. + In general, fresh installations are recommended over upgrades,= particularly for systems which include software from third-party repositor= ies. Third-party packages remaining from a previous installation may not w= ork as expected on an upgraded Fedora system. If you decide to perform an = upgrade anyway, the following information may be helpful. - Before upgrading (or installing), back up the system comp= letely. In particular, preserve /etc, /home= , and possibly /opt and /usr/loca= l if customized packages are installed there. Using a multi-boo= t approach with a "clone" of the old installation on alternate partition[s]= as a fall-back might be considered. Creating alternate boot media, such a= s GRUB floppy would be advisable. - - Make Backups! - Backups of configurations in /etc are also very useful in reconstructing system settings after a fres= h install. - - - - After completing the upgrade, run the command: + Before you upgrade, back up the system completely. In pa= rticular, preserve /etc, /home, and possibly /opt and /usr/local if customized packages are instal= led there. You may wish to use a multi-boot approach with a "clone" of the= old installation on alternate partition(s) as a fallback. In that case, c= reating alternate boot media such as GRUB boot floppy. + + + + + + + + + +
+
+ + + + + + + (!) + + + System Configuration Backu= ps + +
+ Backups of configurations in /etc = are also useful in reconstructing system settings after a fresh installatio= n. +
+
+
+
+ + After you complete the upgrade, run the following command= : + + rpm -qa --last > RPMS_by_Install_Time.txt - - - Inspect the end of the output for packages that pre-date = the upgrade and remove/upgrade those from 3rd party repos, or otherwise dea= l with them as necessary. + + + Inspect the end of the output for packages that pre-date t= he upgrade. Remove or upgrade those packages from third-party repositories= , or otherwise deal with them as necessary.
Index: Java.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Java.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Java.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Java.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,17 +1,117 @@ - +
Temp -
- Java - A free and open source Java environment is available within this= Fedora Core release. - It has three components: GNU Java runtime ("libgcj"), the Eclips= e 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 othe= r Java environments are presented. - Several major software such as Openoffice.org Base, Eclipse, Apa= che Tomcat and several other Java software included in this release is comp= atible with it - For more information see the FAQ at = - http://www.= fedoraproject.org/wiki/JavaFAQ. - - Refer to the Docs/B= eats/PackageNotes/Java page for information about Java packages. +
+ Java and java-gcj-compat + A free and open source Java environment is available within this= Fedora Core release, called . includes a tool suite and execution environ= ment that is capable of building and running many useful programs that are = written in the Java programming language. + + + + + + + + + +
+
+ + + + + + + {i} + + + Fedora Core Does Not Include Jav= a + +
+ Java is a trademark of Sun Microsystems. is an enti= rely free software stack that is not J= ava, but may run Java software. +
+
+
+ The infrastructure has three key components: a 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 a manner similar to other Java environ= ments. + The Java software packages included in this Fedora release use t= he new, integrated environment . These packages include OpenOffice.org Base, Eclipse, and Apache Tomcat. + Refer to the Java FAQ at http://www.fedoraproject.org/wiki/JavaFAQ for mor= e information on the free Java environment in Fedora. + + + + + + + + + + + + +
+
+ + + + + + + (!) + + + Include location and version inf= ormation in bug reports + +
+ When making a bug report, be sure to include the outp= ut from these commands: +
+ + which java && java -version && whic= h javac && javac -version + +
+
+
+
+ Handling Java and Java-like Packages + In addition to the free software stack, Fedora Core is design= ed to let you install multiple Java implementations and switch between them= using the alternatives command line tool. However, every Java= system you install must be packaged using the JPackage Project packaging g= uidelines to take advantage of alternatives. + Once installed properly, the root user should be = able to switch between java and javac implementat= ions using the alternatives command: + + + alternatives --config java alternatives --config javac + + +
+
+ Fedora and the JPackage Java Packages + Fedora Core includes many packages derived from the JPackage P= roject, which provides a Java software repository. These packages have been= modified in Fedora to remove proprietary software dependencies and to make= use of GCJ's ahead-of-time compilation feature. Fedora users should use th= e Fedora repositories for updates to these packages, and may use the JPacka= ge repository for packages not provided by Fedora. + Refer to the JPackage website at http://jpackage.org for more information on the project and t= he software that it provides. + + + + + + + + + +
+
+ + + + + + + /!\ + + + Mixing Packages from Fedora an= d JPackage + +
+ Research package compatibility before you install s= oftware from both the Fedora and JPackage repositories on the same system. = Incompatible packages may cause complex issues. +
+
+
+
Index: Kernel.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Kernel.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Kernel.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Kernel.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,27 +1,35 @@ - +
Temp -
+
Linux Kernel - 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 mig= ht be appropriate for this page or if a sub-page is needed, please contact = SamFolkWilliams or email the Fedora= Documentation Project at fedora-docs-list(a)redhat.com.= + This section covers changes and important information regarding = the kernel in Fedora Core .
Version This distribution is based on the 2.6 series of the Linux kern= el. 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 vanilla kernel from the kernel.org web site: http://www.kernel.org/ - You may obtain a list of any such patches by using the command= on the Fedora Core package: + To obtain a list of these patches, download the source RPM pac= kage and run the following command against it: + + rpm -qpl kernel-<version>.src.rpm + +
Changelog - The package changelog can be retrieved using the following com= mand - rpm -q --changelog <kernel-version> - If you need a user friendly version of the changelog, refer to= http://wiki.kern= elnewbies.org/LinuxChanges. A short and full diff of the kernel is = available from http://kernel.org/git. The Fedora version is based on the Linus tree. - Customisations made for the Fedora version are available from = http://cvs.fedora.redhat.com . + To retrieve a log of changes to the package, run the following= command: + + + rpm -q --changelog kernel-<version> + + + If you need a user friendly version of the changelog, refer to= http://wiki.kern= elnewbies.org/LinuxChanges. A short and full diff of the kernel is = available from http://kernel.org/git. The Fedora version kernel is based on the Linus tree. + Customizations made for the Fedora version are available from = http://cvs.fedora.redhat.com .
Kernel Flavors @@ -31,95 +39,291 @@ Fedora Core includes the following kernel builds: - Native kernel, in both uni-processor and SMP (Symmetric M= ulti-Processor) varieties. SMP kernels provide support for multiple CPU's o= r processors. Configured sources are available in the kernel-[smp-= ]devel-<version>.<arch>.rpm package. + Native kernel, in both uni-processor and SMP (Symmetric M= ulti-Processor) varieties. SMP kernels provide support for multiple CPUs. C= onfigured sources are available in the kernel-[smp-]devel-<version= >.<arch>.rpm package. + + + Virtual kernel hypervisor for use with the Xen emulator p= ackage. Configured sources are available in the kernel-xen-hypervisor= -devel-<version>.<arch>.rpm package. - Virtual kernel hypervisor for use with the Xen emulator p= ackage. Configured sources are available in the kernel-xen-hypervi= sor-devel-<version>.<arch>.rpm package. + Virtual kernel guest for use with the Xen emulator packag= e. Configured sources are available in the kernel-xen-guest-devel-<= ;version>.<arch>.rpm package. - Virtual kernel guest for use with the Xen emulator packag= e. Configured sources are available in the kernel-xen-guest-devel-= <version>.<arch>.rpm package. + Kdump kernel for use with kexec/kdump capabilities. Confi= gured sources are available in the kernel-kdump-devel-<version>.&l= t;arch>.rpm package. + + + You may install sources for all kernel flavors at the same tim= e. The files are installed in the /usr/src/kernels/<version>-[xen-= hypervisor|xen-guest|kdump]-<arch>/ tree. Use the following comma= nd: + + + su -c 'yum install kernel-{xen,hypervisor,xen-guest,kdum= p}-devel' + + Select one or more of these flavors, separated by commas and n= o spaces, as appropriate. Enter the root password when prompted. + - Kdump kernel for use with kexec/kdump capabilities. Confi= gured sources are available in the kernel-kdump-devel-<version>= .<arch>.rpm package. + + + + + + + +
+
+ + + + + + + {i} + + + x86_64 Default Kernel Provides= SMP + +
+ There is no separate SMP kernel available for the x= 86_64 architecture in Fedora Core . +
+ + + + + + + +
+
+ + + + + + + {i} + + + PowerPC Kernel Support + +
+ There is no support for Xen or kdump for the PowerP= C architecture in Fedora Core . +
- Sources for all kernel flavors may be installed at the same - time. The files will be installed into the - /usr/src/kernels/<version>[-xen-hypervisor/xen-guest= /kdump]-<arch>/ - tree. Use this command as appropriate: - rpm -Uvh kernel-[xen-hypervisor/xen-guest/kdump]-devel-&= lt;version>.<arch>.rpm - - Default Kernels in x86_64 Architecture Provide SM= P Capability - There is no separate SMP kernel available for this = architecture in Fedora Core . - +
+
+ Reporting Bugs + Refer to http://kernel.org/pub/linux/docs/lkml/reporting-bugs.ht= ml for information on reporting bugs in the Linux kernel. You may = also use http://bugzilla.redhat.c= om for reporting bugs which are specific to Fedora.
Following Generic Textbooks - Many of the tutorials, examples, and textbooks about Linux ker= nel development assume the kernel sources are installed under the = /usr/src/linux/ directory. If you make a symbolic link, as shown = below, you should be able to use those learning materials with the Fedora C= ore packages. Install the appropriate kernel sources, as shown earlier, and= then: - ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src= /linux + Many of the tutorials, examples, and textbooks about Linux ker= nel development assume the kernel sources are installed under the /us= r/src/linux/ directory. If you make a symbolic link, as shown below,= you should be able to use those learning materials with the Fedora Core pa= ckages. Install the appropriate kernel sources, as shown earlier, and then = run the following command: + + + su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /= usr/src/linux' + + + Enter the root password when prompted.
Preparing for Kernel Development Fedora Core does not include the kernel-source package provid= ed by older versions. Instead, configured sources are available, as describ= ed in this kernel flavors section. - Users that require access to Fedora Core original kernel sourc= es can find them in the kernel .src.rpm package. - To create an exploded source tree from this file, perform the = following steps: - - These Instructions Refer to the Currently-running= Kernel - To simplify the following directions, we have assum= ed that you want to configure the kernel sources to match your currently-ru= nning kernel. In the steps below, you must understand that the phrase <v= ersion> refers to the kernel version shown by the command: uname -= r. - - 1. Obtain the kernel-<version>.src.rpm file from one of the= following sources: - - - The SRPMS directory on the appropriate SRPMS CD iso image= . - - - The FTP site where you got the kernel package. - - - By running the following command: - yum install yum-utilsyumdownloader --source kernel - - - 2. Install kernel-<version>.src.rpm usin= g the command: - rpm -Uvh kernel-<version>.src.rpm` - This writes the RPM contents into /usr/src/redhat/SOU= RCES and /usr/src/redhat/SPECS. - 3. Prepare the kernel sources using the commands: - cd /usr/src/redhat/SPECSrpmbuild -bp --target $(arch) ke= rnel-2.6.spec - The kernel source tree is then located in the /usr/sr= c/redhat/BUILD/kernel-<version>/ directory. It is common pract= ice to move the resulting linux-<version> directory to the /usr= /src/ tree; while not strictly necessary, do this to match the ge= nerally-available documentation. - -cd /usr/src/redhat/BUILD/kernel-<version> -mv linux-<version> /usr/src/ -cd /usr/src -ln -s ./linux-<version> linux -cd /usr/src/linux - - 4. The configurations for the specific kernels shipped in Fedo= ra Core are in the configs/ directory. For example, the i686 SMP configura= tion file is named configs/kernel-<version>-i686-smp.config. Issue the following command to place the desired configuration file= in the proper place for building: - cp configs/<desired-config-file> .config - You can also find the .config file that mat= ches your current kernel configuration in the /lib/modules/<ver= sion>/build/.config file. - 5. Every kernel gets a name based on its version number. This = is the value the uname -r command displays. The kernel n= ame is defined by the first four lines of the kernel Makefile. To protect t= he innocent, the Makefile has been changed to generate a kernel with a diff= erent 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 wi= th the correct name. To do this, you must edit the kernel Makefile. - For example, if the uname -r returns the st= ring 2.6.11-1.234_FC4, change the EXTRAVERSION<= /command> definition from this: - EXTRAVERSION =3D -prep - to this: - EXTRAVERSION =3D -1.234_FC4 - that is, substitute everything from the final dash onward. - 6. Issue the following command: - make oldconfig - You can then proceed as usual. + + + + + + + + + +
+
+ + + + + + + {i} + + + Instructions Refer to Current = Kernel + +
+ To simplify the following directions, we have assum= ed that you want to configure the kernel sources to match your currently-ru= nning kernel. In the steps below, the expression <version> refers to the= kernel version shown by the command: uname -r. +
+
+
+ Users who require access to Fedora Core original kernel source= s can find them in the kernel .src.rpm package. To create an exploded sour= ce tree from this file, perform the following steps: + + + + + + + + + +
+
+ + + + + + + <!> + + + Do Not Build Packages as Super= -user + +
+ Building packages as the superuser is inherently da= ngerous and is not required, even for the kernel. These instructions allow= you to install the kernel source as a normal user. Many general informati= on sites refer to /usr/src/linux in their kernel instructions.= If you use these instructions, simply substitute ~/rpmbuild/BUILD/k= ernel-<version>/linux-<version>. +
+
+
+ + + Prepare a RPM package building environment in your home di= rectory. Run the following commands: + + + su -c 'yum install fedora-rpmdevtools'fedora-buildrp= mtree + Enter the root password when prompted. + + + + + Obtain the kernel-<version>.src.rpm file f= rom one of the following sources: + + + the SRPMS directory on the appropriate SRPMS CD iso i= mage + + + the HTTP or FTP site where you got the kernel package= + + + by running the following command: + + + su -c 'yum install yum-utils'su -c 'yumdownloade= r --source kernel' + + + Enter the root password when prompted. + + + + + Install kernel-<version>.src.rpm using the= command: + + + rpm -Uvh kernel-<version>.src.rpm` + This command writes the RPM contents into ${HOME= }/rpmbuild/SOURCES and ${HOME}/rpmbuild/SPECS, where ${HOME} is your home directory. + + + + + + + +
+
+ + + + + + + (!) + + + Space Required + +
+ The full kernel building process may require se= veral gigabytes of extra space on the file system containing your home dire= ctory. +
+
+
+
+ + Prepare the kernel sources using the commands: + + + cd ~/rpmbuild/SPECSrpmbuild -bp --target $(uname -m)= kernel-2.6.spec + The kernel source tree is located in the ${HOME}= /rpmbuild/BUILD/kernel-<version>/ directory. + + + + + The configurations for the specific kernels shipped in Fed= ora Core are in the configs/ directory. For example, the i686= SMP configuration file is named configs/kernel-<version>-i686-smp= .config. Issue the following command to place the desired configurat= ion file in the proper place for building: + + + cp configs/<desired-config-file> .config + You can also find the .config file that m= atches your current kernel configuration in the /lib/modules/<vers= ion>/build/.config file. + + + + + Every kernel gets a name based on its version number. This= is the value the uname -r command displays. The kernel name i= s defined by the first four lines of the kernel Makefile. The = Makefile has been changed to generate a kernel with a different name from that of the running kernel. To be accepted= by the running kernel, a module must be compiled for a kernel with the cor= rect name. To do this, you must edit the kernel Makefile. + + + For example, if the uname -r returns the = string 2.6.15-1.1948_FC5, change the EXTRAVERSION= definition from this: + EXTRAVERSION =3D -prep + to this: + EXTRAVERSION =3D -1.1948_FC5 + That is, substitute everything from the final dash onw= ard. + + + + + Run the following command: + + + make oldconfig + You may then proceed as usual. + + + +
Building Only Kernel Modules - An exploded source tree is not required to build a kernel modu= le, such as your own device driver, against the currently in-use kernel. Fo= r example, to build the foo.ko module, create the follow= ing Makefile in the directory containing the foo.c file:= - -obj-m :=3D foo.o -KDIR :=3D /lib/modules/$(shell uname -r)/build -PWD :=3D $(shell pwd) -default:$(MAKE) -C $(KDIR) M=3D$(PWD) modules - - Issue the make command to build the foo.ko module. + An exploded source tree is not required to build a kernel modu= le, such as your own device driver, against the currently in-use kernel. Fo= r example, to build the foo.ko module, create the following Makefile in the directory containing the foo.c file= : + + + obj-m :=3D foo.oKDIR :=3D /lib/modules/$(shell uname -r= )/buildPWD :=3D $(shell pwd)default:$(MAKE) -C $(KDIR) M=3D$(PWD) modules= + + + Issue the make command to build the foo.ko<= /code> module.
User Space Dependencies on the Kernel - 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. Co= nsequently, to remove such a kernel, perhaps after an update, you cannot si= mply use the rpm -e kernel-<version> command as in ea= rlier distributions because these user space packages depend on the kernel = package. You may either list both the kernel package and all of its user sp= ace dependent packages on the rpm -e command, or you can= use the yum remove kernel-<version> command instead.= The yum command automatically removes dependent packag= es, if necessary. + Fedora Core has support for clustered storage through the Glo= bal File System (GFS). GFS requires special kernel modules that work in co= njunction with some user-space utilities, such as management daemons. To r= emove such a kernel, perhaps after an update, use the su -c 'yum remo= ve kernel-<version>' command instead. The yum comma= nd automatically removes dependent packages, if necessary. + + + + + + + + + +
+
+ + + + + + + {i} + + + PowerPC does not support GFS + +
+ The GFS kernel modules are not built for the PowerP= C architecture in Fedora Core . +
+
+
Index: Legacy.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Legacy.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Legacy.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Legacy.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,44 +1,26 @@ - +
Temp -
- Legacy Information -
- Systemwide Search Changes - - <command>Slocate</command> Replaced with <command>mlocate</command= > - The /usr/bin/{locate,updatedb} i= mplementation slocate was replaced by mlocate. - - - The locate command should be completel= y compatible - - - - /etc/updatedb.conf is compatible for correc= t configuration files - - - Syntax errors that slocate would not d= etect are now reported - - - The DAILY_UPDATE variable is not suppo= rted - - - The updatedb command is not compatible= , custom scripts using updatedb might have to be changed= . - - - -
-
- LinuxThreads No Longer Available - The LinuxThreads library, which was depre= cated in Fedora Core 4, is no longer available in this release. NP= TL has been the default threading library since Red Hat Linux 9. = -
-
- Legacy Compatability Libraries - Fedora Core includes legacy system libraries for compatibili= ty with older software. This software is part of the Legacy Software Development group that is not installed by d= efault. Users who require this functionality can select this group during i= nstallation or run the following command post-installation. -yum groupinstall "Legacy Software Development" -
-
+
+ Fedora Legacy - Community Maintenance Project + The Fedora Legacy Project is a community-supported open source p= roject to extend the lifecycle of select "maintenance mode" Red Hat Linux a= nd Fedora Core distributions. The Fedora Legacy Project works with the Lin= ux community to provide security and critical bug fix errata packages. Thi= s work extends the effective lifetime of older distributions in environment= s where frequent upgrades are not possible or desirable. For more informati= on about the Fedora Legacy Project, refer to http://fedoraproject.org/wiki/Legacy. + Currently the Fedora Legacy Project maintains the following dist= ributions and releases in maintenance mode: + + + Red Hat Linux 7.3 and 9 + + + Fedora Core 1, 2, and 3 + + + The Fedora Legacy Project will provide updates for these release= s as long as there is community interest. When interest is not sustained f= urther, maintenance mode ends with the second test release for the third su= bsequent Core release. For example, maintenance mode for Fedora Core 4, if= not sustained by the community, ends with the release of Fedora Core 7 tes= t2. This provides an effective supported lifetime (Fedora Core plus Fedora= Legacy Support) of about 18 months. + The Fedora Legacy Project always needs volunteers to perform qua= lity assurance testing on packages waiting to be published as updates. Ref= er to http://= fedoraproject.org/wiki/Legacy/QATesting for more information. Also= visit our issues list at http://www.redhat.com/archives/fe= dora-legacy-list/2005-August/msg00079.html for further information = and pointers to bugs we have in the queue. + If you need help in getting started, visit the project home page= on the Wiki at http://= fedoraproject.org/wiki/Legacy, or the Mentors page at http://fedoraproject.org/wiki/Mento= rs. If you are looking for others ways to participate in Fedora, r= efer to http://fedo= raproject.org/wiki/HelpWanted. + + CategoryLegacy + +
Index: Multimedia.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Multimedia.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Multimedia.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Multimedia.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,39 +1,36 @@ - +
Temp -
+
Multimedia Fedora Core includes applications for assorted multimedia functi= ons, including playback, recording and editing. Additional packages are av= ailable through the Fedora Extras repository.
Multimedia Players - By default, Fedora Core installs with Rhythm Box, Totem, and Helix Player for media playback. In add= ition, many other programs are available in the Fedora Core and Fedora Extr= as repositories, including the popular XMMS 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 Ad= obe/Macromedia's Flash Player, Real Player, VLC, MPlayer, and Xine, can also be installed, but are excluded from t= he Fedora repositories since they are not compatible with Fedora's licensin= g or are usually distributed with support for restricted formats. For more= on this, refer to: the //fedoraproject.org/wiki/Docs/Beats/Multimedia#Excluded_Multim= edia_Software:Excluded Multimedia Software section. - Fedora Core is also equipped to take full advantage of the Adv= anced Linux Sound Architecture (ALSA) sound system. This means that many p= rograms can play sound simultaneously, which was once difficult on Linux sy= stems. When all multimedia software is configured to use ALSA for sound su= pport, the old limitation disappears. For more information about ALSA, vis= it the project website at http:= //www.alsa-project.org/. - + The default installation of Fedora Core includes Rhythmbox, Totem, and Helix Player for media playbac= k. Many other programs are available in the Fedora Core and Fedora Extras = repositories, including the popular XMMS package. Both GNOME = and KDE have a selection of players that can be used with a variety of form= ats. Additional programs are available from third parties to handle other = formats. + Fedora Core also takes full advantage of the Advanced Linux So= und Architecture (ALSA) sound system. Many programs can play sound simulta= neously, which was once difficult on Linux systems. When all multimedia so= ftware is configured to use ALSA for sound support, this limitation disappe= ars. For more information about ALSA, visit the project website at http://www.alsa-project.org/. =
Ogg and Xiph.Org Foundation Formats - Fedora includes complete support for the Ogg media container f= ormat, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio= formats. More information on these formats and how to use them can be fou= nd at the Xiph.Org Foundation's web site at http://www.xiph.org/. - + Fedora includes complete support for the Ogg media container f= ormat, and the Vorbis audio, Theora video, Speex audio, and FLAC lossless a= udio formats. These freely-distributable formats are not encumbered by pat= ent or license restrictions. They provide powerful and flexible alternativ= es to more popular, restricted formats. The Fedora Project encourages the = use of open source formats in place of restricted ones. For more informati= on on these formats and how to use them, refer to the Xiph.Org Foundation's= web site at http://www.xiph.org/.
- MP3 & DVD Support - Fedora Core and Fedora Extras cannot include support for MP3 o= r DVD playback or recording, because the MP3 and MPEG (DVD) formats are pat= ented, and the patent owners have not provided the necessary licenses. For= more information, refer to http://fedoraproject.org/w= iki/Docs/Beats/Multimedia#Excluded_Multimedia_Software. - + MP3, DVD and Other Excluded Multimedia + Fedora Core and Fedora Extras cannot include support for MP3 o= r DVD playback or recording, because the MP3 and MPEG (DVD) formats are pat= ented, and the patent owners have not provided the necessary licenses. Fed= ora also excludes several multimedia application programs due to patent or = license restrictions, such as Flash Player and Real Player. For more on th= is subject, please refer to http://fedoraproject.org/wiki/ForbiddenItems.
- Excluded Multimedia Software - - - - Several programs are excluded from Fedora Core and Fedora Extr= as due to patent or license restrictions. These include programs which pro= vide MP3 and DVD support, Flash Player, and Real Player. For more on this = subject, please see http://fedoraproject.org/wiki/ForbiddenItems. - + CD and DVD Authoring and Burning + Fedora Core and Extras include a variety of tools for easily m= astering and burning CDs and DVDs. GNOME users can burn directly from the = Nautilus file manager, or choose the gnomebaker or grave= man packages from Fedora Extras, or the older xcdroast = package from Fedora Core. KDE users can use the robust k3b pa= ckage for these tasks. Console tools include cdrecord, = readcd, mkisofs, and other typical Linux applications. =
- CD and DVD Authoring and Burning - Tools are included in Fedora Core and Fedora Extras for easily= mastering and burning CDs and DVDs. Tools that can be used from the conso= le include cdrecord, readcd, mkisofs, and other typical Linux applications. For GNOME users,= the xcdroast package from Fedora Core and the = graveman package from Fedora Extras allows for easy preparation o= f audio and data discs. For KDE users, the k3b package = provides a very robust tool for these tasks. + Screencasts + You can use Fedora to create and play back screencas= ts, which are recorded desktop sessions, using open technologies= . Fedora Extras 5 includes istanbul, which creates screencast= s using the Theora video format. These videos can be played back using one= of several players included in Fedora Core. This is the preferred way to = submit screencasts to the Fedora Project for either developer or end-user u= se. For a more comprehensive how-to, refer to http://fedoraproject.org/wiki/ScreenCasting<= /ulink>. +
+
+ Extended Support through Plugins + Most of the media players in Fedora Core and Fedora Extras sup= port the use of plugins to add support for additional media formats and sou= nd output systems. Some use powerful backends, like gstreamer= , to handle media format support and sound output. Plugin packages for the= se backends and for individual applications are available in Fedora Core an= d Fedora Extras, and additional plugins may be available from third parties= to add even greater capabilities.
Index: Networking.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Networking.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Networking.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Networking.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,77 +1,99 @@ - +
Temp -
+
Networking
- Major Kernel Changes 2.6.11 - 2.6.14 + Major Kernel Changes 2.6.11 - 2.6.15 + Refer to http://wiki.kernelnewbies.org/LinuxChanges for a list of major= changes. Some of them are highlighted below.
IPv4 Address Promotion - Starting with version 2.6.12 of the kernel a new feature has= been added called named address promotion. 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 net.ipv4.conf.all.promote_secondaries= (or one of the interface specific variants) this behaviour can b= e changed to promote one of the secondary addresses to be the new primary a= ddress. + Starting with version 2.6.12 of the kernel, a new feature ha= s been added called named address promotion. This feat= ure allows secondary IPv4 addresses to be promoted to primary addresses. Us= ually when the primary address is deleted, all secondary addresses are dele= ted as well. If you enable the new sysctl key net.ipv4.c= onf.all.promote_secondaries, or one of the interface specific varian= ts, you can change this behavior to promote one of the secondary addresses = to be the new primary address.
Configurable Source Address for ICMP Errors - The current behaviour when selecting the source address for = ICMP error messages is to use the address of the interface the ICMP error i= s going to be sent out. Kernel version 2.6.12 introduces a new sysctl net.ipv4.icmp_errors_use_inbound_ifaddr that allows changing = this behaviour to use the address of the interface that received the origin= al error-causing packet. - For example, the kernel receives an ICMP echo request on eth= 0. Because the new sysctl option is enabled, this causes the ICMP echo repl= y to be sent out via eth1. The address of eth0 is used when the default beh= aviour would use the address of eth. - This may ease network debugging in asynchronous routing setu= ps. + By default, when selecting the source address for ICMP error= messages, the kernel uses the address of the interface on which the ICMP e= rror is going to be sent. Kernel version 2.6.12 introduces the new sy= sctl key net.ipv4.icmp_errors_use_inbound_ifaddr. If y= ou enable this option the kernel uses the address of the interface that rec= eived the original error-causing packet. + Suppose the kernel receives a packet on interface eth0= which generates an ICMP error, and the routing table causes the err= or message to be generated on interface eth1. If the new sysctl option is enabled, the ICMP error message indicates the sou= rce address as interface eth0, instead of the default et= h1. This feature may ease network debugging in asynchronous routing= setups.
LC-Trie Based Routing Lookup Algorithm - A new routing lookup algorithm called trie has been added. It is intended for large routing tables and shows a cle= ar performance improvement over the original hash implementation at the cos= t of increased memory consumption and complexity. + A new routing lookup algorithm called trie has been added. It is intended for large routing tables and shows a cle= ar performance improvement over the original hash implementation, at the co= st of increased memory consumption and complexity.
Pluggable Congestion Control Algorithm Infrastructure</titl= e> - <para>TCP congestion control algorithms are now pluggable and thus= modular. The legacy New<emphasis role=3D'strong'/>Reno algorithm stays def= ault and acts as the fallback algorithm. The following new congestion contr= ol algorithms have been added: </para> + <para>TCP congestion control algorithms are now pluggable and thus= modular. The legacy New<emphasis role=3D'strong'/>Reno algorithm remains t= he default, and acts as the fallback algorithm. The following new congestio= n control algorithms have been added: </para> <itemizedlist> <listitem> - <para> High Speed TCP congestion control. </para> + <para> High Speed TCP congestion control </para> </listitem> <listitem> - <para> TCP Hybla congestion avoidance. </para> + <para> TCP Hybla congestion avoidance </para> </listitem> <listitem> - <para> H-TCP congestion control. </para> + <para> H-TCP congestion control </para> </listitem> <listitem> - <para> Scalable TCP congestion control. </para> + <para> Scalable TCP congestion control </para> + </listitem> + </itemizedlist> + <para>All existing congestion control modules have been converted = to this new infrastructure, and the BIC congestion control has received enh= ancements from BICTCP 1.1 to handle low latency links. </para> + <itemizedlist> + <listitem> + <table> + <caption/> + <tr> + <td> + <para> + <inlinemediaobject> + <imageobject> + <imagedata width=3D'16' fileref=3D'/wiki/ntheme/im= g/icon-info.png' depth=3D'16'/> + </imageobject> + <textobject> + <phrase>{i}</phrase> + </textobject> + </inlinemediaobject> + <emphasis role=3D'strong'>Affecting the Congestion Con= trol Algorithm</emphasis> + </para> + </td> + </tr> + <tr> + <td> + <para> The congestion control algorithm is socket specif= ic, and may be changed via the socket option <code>TCP_CONGESTION</code>. <= /para> + </td> + </tr> + </table> </listitem> </itemizedlist> - <para>All existing congestion control modules have been converted = to this new infrastructure and the BIC congestion control has received enha= ncements from BICTCP 1.1 to handle low latency links. </para> - <note> - <title> -Affecting the Congestion Control Algorithm - An interesting addition for developers is that the conge= stion control algorithm is socket specific and can be changed via the socke= t option TCP_CONGESTION. -
Queue Avoidance upon Carrier Loss - When a network driver notices a carrier loss, for example, w= hen the cable is pulled out, the driver stops the queue in front of the dri= ver. This has been causing the packets to be queued at the queueing discipl= ine layer for an unbound period of time causing unexpected effects. In orde= r to prevent this effect, the core networking stack now ceases to accept an= y packets for queueing for any device that is operationally down, that is, = has its queue disabled. + When a network driver notices a carrier loss, such as when t= he cable is pulled out, the driver stops the queue in front of the driver. = In the past, this stoppage caused the packets to be queued at the queueing = discipline layer for an unbound period of time causing unexpected effects. = In order to prevent this effect, the core networking stack now refuses to q= ueue any packets for a device that is operationally down, that is, has its = queue disabled.
DCCP Protocol Support - Kernel version 2.6.14-rc1 was the first version to receive s= upport 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. + Kernel version 2.6.14-rc1 was the first version to receive s= upport for the DCCP protocol. The implementation is still experimental, but= is known to work. Developers have begun work to make userspace application= s aware of this new protocol.
Wireless - A new driver named HostAP has been added to 2.6.14-rc1 allow= ing the emulation of a wireless access point in software. Currently this dr= iver 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. + A new HostAP driver appears in the kernel starting in 2.6.14= -rc1, which allows the emulation of a wireless access point through softwar= e. Currently this driver only works for Intersil Prism2-based cards (PC Car= d/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 = has been added.
Miscellaneous - A lot of TCP Segmentation Offloading (TSO) related fixe= s have been included. + Many TCP Segmentation Offloading (TSO) related fixes ar= e included. - A new textsearch infrastructure has been added useable = with the corresponding iptables and extended match. + A new textsearch infrastructure has been added, and is = usable with corresponding iptables and extended match. Both the IPv4 and IPv6 multicast joining interface visi= ble by userspace have been reworked and brought up to the latest standards.= - The SNMPv2 MIB counter ipInAddrErrors is finally suppor= ted for IPv4. + The SNMPv2 MIB counter ipInAddrErrors is supported for = IPv4. Various new socket options proposed in Advanced API (RF= C3542) have been added. @@ -80,22 +102,22 @@
- Userspace Tools - The IPv4 address deletion algorithm did not take the prefix le= ngth 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: - -ip addr list dev eth0 -4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_= fast qlen 1000 -inet 10.0.0.3/24 scope global eth0 -su -c 'ip addr del 10.0.0.3 dev eth0' -Warning: Executing wildcard deletion to stay compatible wi= th old -scripts. Explicitly specify the prefix length (10.0.0.3/32) to -avoid this warning. This special behaviour is likely to disappear -in further releases, fix your scripts! - + User Tools + The IPv4 address deletion algorithm did not take the prefix le= ngth 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 prov= ided, to warn about possible unintended deletions: + + + ip addr list dev eth0 4: eth0: <BROADCAST,MULTICAST,U= P> mtu 1500 qdisc pfifo_fast qlen 1000inet 10.0.0.3/24 scope global eth0 + su -c 'ip addr del 10.0.0.3 dev eth0' Warning: Executing= wildcard deletion to stay compatible with oldscripts. Explicitly specify t= he prefix length (10.0.0.3/32) toavoid this warning. This special behaviour= is likely to disappearin further releases, fix your scripts! + + The correct method of deleting the address and thus avoiding t= he warning is: -su -c 'ip addr del 10.0.0.3/24 dev eth0' - Previously, it has not been possible to tell if an interface i= s down administratively or because no carrier can be found (cable unplugged= ). The flag NO-CARRIER has been introduced that shows up= as a link flag if the link is administratively up but no carrier can be fo= und. - The ip command now supports a batch mode via the argument -batch that works similar to the tc command to speed up batc= hes of tasks. + + + su -c 'ip addr del 10.0.0.3/24 dev eth0' + + + Previously, it was not possible to tell if an interface was do= wn administratively or because no carrier was found, such as if a cable wer= e unplugged. The new flag NO-CARRIER now appears as a link fla= g if the link is administratively up but no carrier can be found. + The ip command now supports a batch mode via the = argument -batch, which works similar to the tc co= mmand to speed up batches of tasks.
Index: OverView.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/OverView.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- OverView.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ OverView.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,62 +1,103 @@ - +
Temp -
+
Fedora Core 5 Tour - Welcome to Fedora. In this new exciting new release, we present = you a sneak preview of Fedora Core 5 filled with pictures and videos availa= ble at http:= //fedoraproject.org/wiki/Tours/FedoraCore5. + You can find a tour filled with pictures and videos of this exci= ting new release at http://fedoraproject.org/wiki/Tours/FedoraCore5.
What Has Changed Since Fedora Core 4 - - Your Participation Is Requested - -We request active participation from the community to test the following m= ajor 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 (http://redhat.com/mailman/listinfo/fedora= -test-list/) mailing list. Thank you for your interest and particip= ation in the development of Fedora. - + This release is the culmination of nine months of development,= and includes significant new versions of many key products and technologie= s. The following sections provide a brief overview of major changes from th= e last release of Fedora Core.
Desktop + Some of the highlights of this release include: - A completely revamped look and feel including a bubbly = new theme, wallpaper, screensaver and logo has been provided that is visual= ly appealing and demonstrates the exciting and user friendly nature of Fedo= ra. + There is a completely revamped appearance with a bubbly= new theme and the first use of the new Fedora logo. - GNOME 2.13.4 (http://live.gnome.org/TwoPointThirteen) development re= lease and KDE 3.5 (http://kde.org/announcements/announce-3.5.php) general release= of popular desktop environments is available. + Early work from the Fedora Rendering Project is integra= ted into the desktop. This new project (http://fedoraproject.org/wiki/RenderingProject) is going to provide the technical foundations for advanced desktop = interfaces based on OpenGL. - GNOME Power Manager and GNOME Screensaver are available= as a technology preview within this release. + Popular desktop environments GNOME and KDE have innovat= ive new versions included in this release. The GNOME desktop is based on t= he 2.14 release (htt= p://www.gnome.org/~davyd/gnome-2-14/), and the KDE 3.5 desktop is t= he general 3.5 release (http://kde.org/announcements/announce-3.5.php). - OpenOffice.org 2.0 (http://www.openoffice.= org/product/index.html/) release is included. OpenOffice.org now uses system versions for many of the libraries lea= ding to increased performance and efficiency. + The latest versions of GNOME = Power Manager (http://www.gnome.org/projects/gnome-power-manager/= ) and GNOME Screensaver(http://live.gnome.org/GnomeScreens= aver/) provide new and integrated power management capabilities. - Firefox 1.5(http://www.mozilla.com/firefox/releases/1.5.html) web browser with many new features is included in this release + The new GNOME User Share facility provides simple and efficient file sharing. - Pup, the package updater has been joined by Pirut, whic= h is the replacement for system-config-packages providing comprehensive sof= tware package management using yum as a backend. + Software suspend (hibernate) capability is now provided= for a wide variety of hardware. - Beagle which provides a index based search interface, f= -spot for photo management and tomboy, a note taking application has been a= dded to this release. + The previous graphical software management utilities ha= ve been replaced with the first versions of a new generation of tools. This= release includes Pup, a simple interf= ace for system updates, and Pirut, a n= ew package manager that replaces system-config-packages. These= build on the yum utility, to provide consistent software inst= allation and update facilities throughout the system. - Support for Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/) has bee= n included in the kernel. + This release of Fedora includes Mono support for the fi= rst time, and Mono applications such as Beagle, a desktop search interface; F-Spot, a photo management utility; and Tomboy, a note-taking application. - I18N support has drastically improved through the use o= f SCIM language input framework which has replaced IIMF in this release + You can now enjoy enhanced multimedia support with vers= ion 0.10 of the Gstreamer media framew= ork. This milestone release brings major improvements in robustness, compat= ibility, and features, over previous versions of = Gstreamer. The Totem movie = player and other media software in this release have been updated to use th= e new framework. - Gstreamer media framework 0.10 which brings major impro= vements 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. + There is dramatically improved internationalization sup= port with SCIM in Fedora Core . The SCIM language input framework provides a= n easy to use interface for inputting many different non-English languages.= SCIM replaces the IIIMF system used in previous Fedora releases. + + + The default Web browser is Fi= refox 1.5 (http://www.mozilla.com/firefox/releases/1.5.html), which= has many new features for faster, safer, and more efficient browsing. + + + The office applications suite OpenOffice.org 2.0 (http://www.openoffice.org/product/index.html) now = makes better use of general system libraries for increased performance and = efficiency. + + + A large number of GTK and GNOME programs take advantage = of the Cairo 2D graphics library (http://cairographics.org/), in= cluded in this release, to provide streamlined attractive graphical interfa= ces. + + + There are new drivers that provide support for the wide= ly-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/). + + + This release includes libnotify, a library= that features simple and attractive notifications for the desktop. + + + Fedora Core now uses gnome-mount, a more = efficient mechanism that replaces fstab-sync, and uses HAL to = handle mounting. + + + Printing support is improved in this release with the i= nclusion of the hplip utility, which replaces hpijs.
System Administration + Improvements for administrators and developers include: - Xen Virtualisation software and yum package manager are= now well integrated within the Fedora installer. The installer interface i= s more streamlined. Remote logging and improved support for tracebacks is = included. + The Xen virtualiza= tion system has enhanced support. The tools to configure Xen virtual machines on your Fedora Core system now use= the standard graphical installation process, run as a window on your deskt= op. Fedora developers have also created gnome-applet-vm, whic= h provides a simple virtual domains monitor applet, and libvirt (http://libvirt.org/), a libra= ry providing an API to use Xen virtualization capabilities. + + + The industry-leading anaconda installation= system continues to evolve. New features for this release include remote l= ogging and improved support for tracebacks. Package management in the insta= llation system is now provided by yum. This enhancement is th= e first step in enabling access to Fedora Extras from within the installati= on process. + + + Version 2.2 of the Apache HTTP server is now included. This release provides enhancements to = authentication, database support, proxy facilities, and content filtering. = + + + The latest generation of database servers are packaged = in this release, including both MySQL = 5.0 and PostgreSQL 8.1. + + + Several native Java programs are now available compiled= with GCJ, such as the Geronimo J2EE server and the Apache Jakarta Project, in addition to the Java programs and development capabilities = in the previous releases. - System Tap (http://sourceware.org/systemtap/) a instrumentation system fo= r debugging and analysing performance bottle necks and Frysk (http://sourceware.org/frysk/), an ex= ecution analysis technology for monitoring running processes or threads is = included within this release. + There are new tools for system monitoring and performan= ce analysis. This release includes SystemTap + (http://fedoraproject.org/wiki/SystemTap), an instrumentatio= n system for debugging and analyzing performance bottle necks, and Frysk (http://fedoraproject.org/wiki/Frysk), an execution anal= ysis technology for monitoring running processes or threads. + + + This release includes system-config-cluster, a utility that allows you to manage cluster configuration in a graphical= setting. + + + The combination of Kexec and Kdump utilities provides mo= dern crash dumping facilities and potential for faster bootup, bypassing th= e firmware on reboots. Kexec loads a n= ew kernel from a running kernel, and Kdump can provide a memory dump of the previous kernel for debugging. + + + This release includes iscsi-initiator-utils, iSCSI daemon and utility programs that provide support for hardware usin= g the iSCSI interface.
@@ -64,23 +105,26 @@ System Level Changes - Xorg X11R7.0 has been includ= ed in this release. This is the first modular version, which helps in prov= iding additional features and bug fixes at a faster pace. + X.org X11R7.0 is included in this release. The new modu= lar architecture of R7.0 enables easier driver upgrades and simplifies deve= lopment, opening the way for rapid improvement in Linux graphics. + + + The GCC 4.1 compiler is included, and the entire set of= Fedora packages is built with this technology. This provides security and = performance enhancements throughout the system. - gcc 4.1 compiler is included and the entire set of Fedo= ra packages is now build using this new compiler version which brings in ne= w security and performance enhancements. + The kernels for this release are based on Linux 2.6.16.= Refer to the section on the kernel in these release notes for other detail= s. - PCMCIA framework used by laptop and mobile devices had = changed as with kernel version 2.6.13-rc1 onwards. The older pcmcia-cs pack= age using the cardmgr/pcmcia service has been replaced with a new pcmciauti= ls package where the PCMCIA devices are handled directly with the hotplug s= ystem using udev dynamically in this Fedora release. This increases both e= fficiency and performance of the system. More information about this change= s are available from http://www.kernel.org/pub/linux/utils/kernel/pcmci= a/pcmcia.html. + The PCMCIA framework used by laptop and mobile devices = has changed. The older pcmcia-cs package using the cardm= gr/pcmcia service has been replaced with a new pcmciautils package. With pcmciautils, PCMCIA devices are handled dir= ectly and dynamically by the hotplug and udev sub= systems. This update increases both efficiency and performance of the syst= em. For more information about these changes, refer to http://www.kerne= l.org/pub/linux/utils/kernel/pcmcia/pcmcia.html. - SELinux implementation has undergone a major change wit= h a switchover to refere= nce policy. SELinux reference policy can support binary policy modu= les. It is possible now to move SELinux policies into individual packages a= nd make it easier for users to ship site-specific policy customizations whe= n required. This version also adds support for MCS (Multi Category System) = enabled by default and MLS (Multi Level System) in addition to the the prev= ious versions which have TE (Type Enforcement) which is enabled by default = and RBAC (Role Based Access Contro) security sub systems within the SELinux= framework. + SELinux implementation has undergone a major change, wi= th a switch to the SELinux reference policy (http://serefpolicy.sourceforge.net/). The SELi= nux reference policy can support binary policy modules. It is now possible = to move SELinux policies into individual packages, making it easier for use= rs to ship site-specific policy customizations when required. This version = also adds support for Multi-Category Security (MCS), enabled by default, an= d Multi-Level Security (MCS). SELinux continues to offer support for TE (T= ype Enforcement), enabled by default, and RBAC (Role-Based Access Control).= Refer to the section on SELinux in these release notes for other details = and links to SELinux resources on the Fedora Project pages.
Road Map - The proposed plans for Fedora in this version are available fr= om http://fedoraprojec= t.org/wiki/RoadMap. + The proposed plans for the next release of Fedora are availabl= e at http://fedoraproj= ect.org/wiki/RoadMap.
Index: PackageChanges.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/PackageChanges.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- PackageChanges.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ PackageChanges.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,15 +1,45 @@ - +
Temp -
+
Package Changes - - <command>LinuxThreads</command> library is no longer availabl= e - - LinuxThreads was been deprecated in F= edora Core 4 and is no longer available in this release. NPTL, which has be= en the default threading library since Red Hat Linux 9, has replaced this c= ompletely. - + + + + + + + + + + + +
+
+ + + + + + + {i} + + + This list is automatically gener= ated + +
+ This list is automatically generated. It is not a go= od choice for translation. +
+
+
+ This list was made using the treediff utility, ran = as treediff newtree oldtree against the rawhide tree of 28 Feb= . 2006. + For a list of which packages were updated since FC 4, refer to t= his page: + + http://fedoraproject.org/wiki/Docs/Beats/PackageChanges/= UpdatedPackages + + New package adaptxAdaptXNew package aggAnti-Grain GeometryNew = package amtuAbstract Machine Test Utility (AMTU)New package anthyJapanese c= haracter set input libraryNew package aspell-ruRussian dictionaries for Asp= ell.New package aspell-slSlovenian dictionaries for Aspell.New package aspe= ll-srSerbian dictionaries for Aspell.New package avahiLocal network service= discoveryNew package axisA SOAP implementation in JavaNew package beagleTh= e Beagle Search InfrastructureNew package bsfBean Scripting FrameworkNew pa= ckage bshLightweight Scripting for JavaNew package cairoA vector graphics l= ibraryNew package cairo-javaJava bindings for the Cairo libraryNew package = castorAn open source data binding framework for JavaNew package concurrentU= tility classes for concurrent Java programmingNew package dev86A real mode = 80x86 assembler and linker.New package dhcdbdDHCP D-BUS daemon (dhcdbd) con= trols dhclient sessions with D-BUS, stores and presents DHCP options.New pa= ckage ekigaA G! nome based SIP/H323 teleconferencing applicationNew package eliloELILO lin= ux boot loader for EFI-based systemsNew package evolution-sharpEvolution Da= ta Server Mono BindingsNew package f-spotPhoto management applicationNew pa= ckage fryskFrysk execution analysis toolNew package gecko-sharp2Gecko bindi= ngs for MonoNew package geronimo-specsGeronimo J2EE server J2EE specificati= onsNew package giflibLibrary for manipulating GIF format image filesNew pac= kage glib-javaBase Library for the Java-GNOME librariesNew package gmimeLib= rary for creating and parsing MIME messagesNew package gnome-applet-vmSimpl= e virtual domains monitor which embed themselves in the GNOME panelNew pack= age gnome-mountMount replacement which uses HAL to do the mountingNew packa= ge gnome-power-managerGNOME Power ManagerNew package gnome-python2-desktopT= he sources for additional PyGNOME Python extension modules for the GNOME de= sktop.New package gnome-screensaverGNOME SreensaverNew package gnome-user-s= hareGnome user! file sharingNew package gnu-efiDevelopment Libraries and head! ers fo FINew package gpartA program for recovering corrupt partition tables.New pa= ckage gsf-sharpMono bindings for libgsfNew package gstreamer-plugins-baseGS= treamer streaming media framework base plug-insNew package gstreamer-plugin= s-goodGStreamer plug-ins with good code and licensingNew package gtk-sharpG= TK+ and GNOME bindings for MonoNew package gtk-sharp2GTK+ and GNOME binding= s for MonoNew package hplipHP Linux Imaging and Printing ProjectNew package= hsqldbHsqldb Database EngineNew package icon-naming-utilsA script to handl= e icon names in desktop icon themesNew package icuInternational Components = for UnicodeNew package imakeimake source code configuration and build syste= mNew package iscsi-initiator-utilsiSCSI daemon and utility programsNew pack= age iso-codesISO code lists and translationsNew package jakarta-commons-cod= ecJakarta Commons Codec PackageNew package jakarta-commons-daemonJakarta Co= mmons Daemon PackageNew package jakarta-commons-discoveryJakarta Commons Di= scoveryNew pac! kage jakarta-commons-httpclientJakarta Commons HTTPClient PackageNew packa= ge javaccA parser/scanner generator for javaNew package jdomJava alternativ= e to DOM and SAXNew package jgroupsToolkit for reliable multicast communica= tion.New package jrefactoryJRefactory and Pretty PrintNew package kasumiAn = anthy dictionary management tool.New package kexec-toolsThe kexec/kdump use= rspace component.New package lcmsColor Management SystemNew package libFSX.= Org X11 libFS runtime libraryNew package libICEX.Org X11 libICE runtime lib= raryNew package libSMX.Org X11 libSM runtime libraryNew package libX11X.Org= X11 libX11 runtime libraryNew package libXScrnSaverX.Org X11 libXss runtim= e libraryNew package libXTrapX.Org X11 libXTrap runtime libraryNew package = libXauX.Org X11 libXau runtime libraryNew package libXawX.Org X11 libXaw ru= ntime libraryNew package libXcompositeX.Org X11 libXcomposite runtime libra= ryNew package libXcursorX.Org X11 libXcursor runtime libraryNew package lib= XdamageX.Org X! 11 libXdamage runtime libraryNew package libXdmcpX.Org X11 lib! Xdmcp = time libraryNew package libXevieX.Org X11 libXevie runtime libraryNew packa= ge libXextX.Org X11 libXext runtime libraryNew package libXfixesX.Org X11 l= ibXfixes runtime libraryNew package libXfontX.Org X11 libXfont runtime libr= aryNew package libXfontcacheX.Org X11 libXfontcache runtime libraryNew pack= age libXftX.Org X11 libXft runtime libraryNew package libXiX.Org X11 libXi = runtime libraryNew package libXineramaX.Org X11 libXinerama runtime library= New package libXmuX.Org X11 libXmu/libXmuu runtime librariesNew package lib= XpX.Org X11 libXp runtime libraryNew package libXpmX.Org X11 libXpm runtime= libraryNew package libXrandrX.Org X11 libXrandr runtime libraryNew package= libXrenderX.Org X11 libXrender runtime libraryNew package libXresX.Org X11= libXres runtime libraryNew package libXtX.Org X11 libXt runtime libraryNew= package libXtstX.Org X11 libXtst runtime libraryNew package libXvX.Org X11= libXv runtime libraryNew package libXvMCX.Org X11 libXvMC runtime libraryN= ew package lib! Xxf86dgaX.Org X11 libXxf86dga runtime libraryNew package libXxf86miscX.Org= X11 libXxf86misc runtime libraryNew package libXxf86vmX.Org X11 libXxf86vm= runtime libraryNew package libchewingIntelligent phonetic input method lib= rary for Traditional ChineseNew package libdaemonlibrary for writing UNIX d= aemonsNew package libdmxX.Org X11 libdmx runtime libraryNew package libdrml= ibdrm Direct Rendering Manager runtime libraryNew package libeventAbstract = asynchronous event notification libraryNew package libfontencX.Org X11 libf= ontenc runtime libraryNew package libgdipluslibgdiplus: An Open Source impl= ementation of the GDI+ APINew package libgpodLibrary to access the contents= of an iPodNew package libgssapiGeneric Security Services Application Progr= amming Interface LibraryNew package libiec61883Streaming library for IEEE13= 94New package liblbxutilX.Org X11 liblbxutil runtime libraryNew package lib= nlConvenience library for kernel netlink socketsNew package libnotifylibnot= ify notificati! on libraryNew package liboilLibrary of Optimized Inner Loops, ! CPU op ized functionsNew package liboldXX.Org X11 liboldX runtime libraryNew packa= ge libpfma performance monitoring library for Linux/ia64New package librtas= Libraries to provide access to RTAS calls and RTAS events.New package libse= manageSELinux binary policy manipulation libraryNew package libsetransSELin= ux Translation libraryNew package libstdc++so7libstdc++.so.7 previewNew pac= kage libunwindAn unwinding library for ia64.New package libvirtLibrary prov= iding an API to use the Xen virtualizationNew package libvte-javaWrapper li= brary for GNOME VTENew package libxkbfileX.Org X11 libxkbfile runtime libra= ryNew package libxkbuiX.Org X11 libxkbui runtime libraryNew package luceneH= igh-performance, full-featured text search engineNew package m17n-dbMultili= ngualization datafiles for m17n-libNew package m17n-libMultilingual text li= braryNew package mesaMesa graphics librariesNew package mlocateAn utility f= or finding files by nameNew package mockobjectsJava MockObjects packageNew = package monoa ! .NET runtime environmentNew package mysql-connector-odbcODBC driver for My= SQLNew package mysqlclient14Backlevel MySQL shared libraries.New package na= utilus-sendtoNautilus context menu for sending filesNew package nfs-utils-l= ibNetwork File System Support LibraryNew package notify-daemonNotification = DaemonNew package nsprNetscape Portable RuntimeNew package opalOpen Phone A= bstraction LibraryNew package openCryptokiImplementation of Cryptoki v2.11 = for IBM Crypto HardwareNew package openspSGML and XML parserNew package pcm= ciautilsPCMCIA utilities and initialization programsNew package perl-Net-IP= Perl module for manipulation of IPv4 and IPv6 addressesNew package perl-Str= ing-CRC32Perl interface for cyclic redundency check generationNew package p= erl-XML-SimpleEasy API to maintain XML in PerlNew package pfmona performanc= e monitoring tool for Linux/ia64New package php-pearPHP Extension and Appli= cation Repository frameworkNew package pirutPackage Installation, Removal a= nd Update Tool! sNew package prctlUtility to perform process operationsNew pac! kage p iroPython bindings for the cairo libraryNew package pykickstartA python lib= rary for manipulating kickstart filesNew package python-pyblockPython modul= es for dealing with block devicesNew package rhpxlPython library for config= uring and running X.New package s390utilsLinux/390 specific utilities.New p= ackage salinfoSAL info tool.New package scimSmart Common Input Method platf= ormNew package scim-anthySCIM IMEngine for anthy for Japanese inputNew pack= age scim-chewingChewing Chinese input method for SCIMNew package scim-hangu= lHangul Input Method Engine for SCIMNew package scim-m17nSCIM IMEngine for = m17n-libNew package scim-pinyinSmart Pinyin IMEngine for Smart Common Input= Method platformNew package scim-qtimmSCIM input method module for QtNew pa= ckage scim-tablesSCIM Generic Table IMEngineNew package squashfs-toolssquas= hfs utilitiesNew package system-config-clustersystem-config-cluster is a ut= ility which allows you to manage cluster configuration in a graphical setti= ng.New package! systemtapInstrumentation SystemNew package tanukiwrapperJava Service Wrap= perNew package tog-pegasusOpenPegasus WBEM Services for LinuxNew package to= mboyTomboy is a desktop note-taking application for Linux and Unix.New pack= age velocityJava-based template engineNew package werken.xpathXPath impleme= ntation using JDOMNew package wpa_supplicantWPA/WPA2/IEEE 802.1X Supplicant= New package wsdl4jWeb Services Description Language Toolkit for JavaNew pac= kage xdocletXDoclet Attribute Orientated Programming FrameworkNew package x= javadocThe XJavaDoc engineNew package xmlrpcJava XML-RPC implementationNew = package xorg-x11-appsX.Org X11 applicationsNew package xorg-x11-driversX.Or= g X11 driver installation packageNew package xorg-x11-drv-acecadXorg X11 ac= ecad input driverNew package xorg-x11-drv-aiptekXorg X11 aiptek input drive= rNew package xorg-x11-drv-apmXorg X11 apm video driverNew package xorg-x11-= drv-arkXorg X11 ark video driverNew package xorg-x11-drv-atiXorg X11 ati vi= deo driverNew ! package xorg-x11-drv-calcompXorg X11 calcomp input driverNew p! ackage rg-x11-drv-chipsXorg X11 chips video driverNew package xorg-x11-drv-cirrusX= org X11 cirrus video driverNew package xorg-x11-drv-citronXorg X11 citron i= nput driverNew package xorg-x11-drv-cyrixXorg X11 cyrix video driverNew pac= kage xorg-x11-drv-digitaledgeXorg X11 digitaledge input driverNew package x= org-x11-drv-dmcXorg X11 dmc input driverNew package xorg-x11-drv-dummyXorg = X11 dummy video driverNew package xorg-x11-drv-dynaproXorg X11 dynapro inpu= t driverNew package xorg-x11-drv-elo2300Xorg X11 elo2300 input driverNew pa= ckage xorg-x11-drv-elographicsXorg X11 elographics input driverNew package = xorg-x11-drv-evdevXorg X11 evdev input driverNew package xorg-x11-drv-fbdev= Xorg X11 fbdev video driverNew package xorg-x11-drv-fpitXorg X11 fpit input= driverNew package xorg-x11-drv-glintXorg X11 glint video driverNew package= xorg-x11-drv-hyperpenXorg X11 hyperpen input driverNew package xorg-x11-dr= v-i128Xorg X11 i128 video driverNew package xorg-x11-drv-i740Xorg X11 i740 = video driverNe! w package xorg-x11-drv-i810Xorg X11 i810 video driverNew package xorg-x11-= drv-jamstudioXorg X11 jamstudio input driverNew package xorg-x11-drv-joysti= ckXorg X11 joystick input driverNew package xorg-x11-drv-keyboardXorg X11 k= eyboard input driverNew package xorg-x11-drv-magellanXorg X11 magellan inpu= t driverNew package xorg-x11-drv-magictouchXorg X11 magictouch input driver= New package xorg-x11-drv-mgaXorg X11 mga video driverNew package xorg-x11-d= rv-microtouchXorg X11 microtouch input driverNew package xorg-x11-drv-mouse= Xorg X11 mouse input driverNew package xorg-x11-drv-mutouchXorg X11 mutouch= input driverNew package xorg-x11-drv-neomagicXorg X11 neomagic video drive= rNew package xorg-x11-drv-nscXorg X11 nsc video driverNew package xorg-x11-= drv-nvXorg X11 nv video driverNew package xorg-x11-drv-palmaxXorg X11 palma= x input driverNew package xorg-x11-drv-penmountXorg X11 penmount input driv= erNew package xorg-x11-drv-renditionXorg X11 rendition video driverNew pack= age xorg-x11-d! rv-s3Xorg X11 s3 video driverNew package xorg-x11-drv-s3virgeX! org X1 3virge video driverNew package xorg-x11-drv-savageXorg X11 savage video dri= verNew package xorg-x11-drv-siliconmotionXorg X11 siliconmotion video drive= rNew package xorg-x11-drv-sisXorg X11 sis video driverNew package xorg-x11-= drv-sisusbXorg X11 sisusb video driverNew package xorg-x11-drv-spaceorbXorg= X11 spaceorb input driverNew package xorg-x11-drv-summaXorg X11 summa inpu= t driverNew package xorg-x11-drv-tdfxXorg X11 tdfx video driverNew package = xorg-x11-drv-tek4957Xorg X11 tek4957 input driverNew package xorg-x11-drv-t= ridentXorg X11 trident video driverNew package xorg-x11-drv-tsengXorg X11 t= seng video driverNew package xorg-x11-drv-ur98Xorg X11 ur98 input driverNew= package xorg-x11-drv-v4lXorg X11 v4l video driverNew package xorg-x11-drv-= vesaXorg X11 vesa video driverNew package xorg-x11-drv-vgaXorg X11 vga vide= o driverNew package xorg-x11-drv-viaXorg X11 via video driverNew package xo= rg-x11-drv-vmwareXorg X11 vmware video driverNew package xorg-x11-drv-voidX= org X11 void i! nput driverNew package xorg-x11-drv-voodooXorg X11 voodoo video driverNew = package xorg-x11-filesystemX.Org X11 filesystem layoutNew package xorg-x11-= font-utilsX.Org X11 font utilitiesNew package xorg-x11-fontsX.Org X11 fonts= New package xorg-x11-proto-develX.Org X11 Protocol headersNew package xorg-= x11-resutilsX.Org X11 X resource utilitiesNew package xorg-x11-serverX.Org = X11 X serverNew package xorg-x11-server-utilsX.Org X11 X server utilitiesNe= w package xorg-x11-twmX.Org X11 twm window managerNew package xorg-x11-util= -macrosX.Org X11 Autotools macrosNew package xorg-x11-utilsX.Org X11 X clie= nt utilitiesNew package xorg-x11-xauthX.Org X11 X authority utilitiesNew pa= ckage xorg-x11-xbitmapsX.Org X11 application bitmapsNew package xorg-x11-xd= mX.Org X11 xdm - X Display ManagerNew package xorg-x11-xfsX.Org X11 xfs fon= t serverNew package xorg-x11-xfwpX.Org X11 X firewall proxyNew package xorg= -x11-xinitX.Org X11 X Window System xinit startup scriptsNew package xorg-x= 11-xkb-utilsX.! Org X11 xkb utilitiesNew package xorg-x11-xkbdataxkb data file! s for = X.Org X11 X serverNew package xorg-x11-xsmX.Org X11 X Session ManagerNew p= ackage xorg-x11-xtrans-develX.Org X11 developmental X transport libraryRemo= ved package CannaRemoved package 4SuiteRemoved package MyODBCRemoved packag= e apelRemoved package VFlib2Removed package anaconda-helpRemoved package aq= hbciRemoved package cdicconfRemoved package fonts-xorgRemoved package gimp-= gapRemoved package gnome-kerberosRemoved package gnomemeetingRemoved packag= e hotplugRemoved package howlRemoved package hpijsRemoved package hpojRemov= ed package iiimfRemoved package iiimf-le-chinputRemoved package iiimf-le-xc= inRemoved package libgal2Removed package libungifRemoved package lvm2-clust= erRemoved package mod_jkRemoved package nvi-m17nRemoved package openh323Rem= oved package openmotif21Removed package pcmcia-csRemoved package perl-Filte= rRemoved package perl-Filter-SimpleRemoved package perl-Parse-YappRemoved p= ackage perl-RPM2Removed package perl-Time-HiResRemoved package perl-XML-Enc= odingRemoved p! ackage perl-libxml-ennoRemoved package python-twistedRemoved package sashR= emoved package schedutilsRemoved package selinux-policy-targetedRemoved pac= kage selinux-policy-strictRemoved package slocateRemoved package struts11Re= moved package system-config-mouseRemoved package system-config-packagesRemo= ved package taipeifontsRemoved package w3c-libwwwRemoved package xinitrcRem= oved package usbview
Index: PackageNotes.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/PackageNotes.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- PackageNotes.xml 17 Feb 2006 00:49:51 -0000 1.2 +++ PackageNotes.xml 28 Feb 2006 17:25:26 -0000 1.3 @@ -1,39 +1,103 @@ - +
- Package Notes + Temp -
+
Package Notes - The following sections contain information regarding packages th= at have undergone significant changes for Fedora Core . For easier access, = they are generally organized using the same groups used in Anaconda. + The following sections contain information regarding software pa= ckages that have undergone significant changes for Fedora Core . For easier= access, they are generally organized using the same groups that are shown = in the installation system. +
+ Kernel device, module loading, and hotplug changes + The hotplug and device handling subsystem has undergone signif= icant changes in Fedora Core . The udev method now handles all= module loading, both on system boot and for hotplugged devices. The = hotplug package has been removed, as it is no longer needed. + Support for hotplug helpers via the /etc/hotplug,= /etc/hotplug.d, and /etc/dev.d directories is de= precated, and may be removed in a future Fedora Core release. These helpers= should be converted to udev rules. Please see http://www.reactivated.n= et/writing_udev_rules.html for examples. +
+
+ Systemwide Search Changes + + + + + + + + + +
+
+ + + + + + + {i} + + + + mlocate Has Replaced slocate + + +
+ The new mlocate package provides the i= mplementations of /usr/bin/locate and /usr/bin/updatedb<= /code>. Previous Fedora releases included the slocate version= s of these programs. +
+
+ + The locate command should be completely comp= atible. + + + The configuration file /etc/updatedb.conf is= compatible. + + + Syntax errors that slocate would not detect = are now reported. + + + The DAILY_UPDATE variable is not supported. = + + + The updatedb command is not compatible, and custom scripts that use updatedb may have= to be updated. + +
+
+
+ Mouse Configuration Utility Removed + The system-config-mouse configuration utility has= been dropped in this release because synaptic and three-butto= n mouse configuration is handled automatically. Serial mice are no longer s= upported. +
+
+ NetworkManager + Fedora systems use Network + Manager to automatically detect, select, and configur= e wired and wireless network connections. Wireless network devices may requ= ire third-party software or manual configuration to activate after the inst= allation process completes. For this reason, Fedora Core provides Ne= twork + Manager as an optional component. + Refer to http://fedoraproject.org/wiki/Tools/NetworkManager for= more information on how to install and enable Network + Manager. +
+
+ Dovecot + Fedora Core includes a new version of the dovecot IMAP server software, which has has many changes in its configuration fil= e. These changes are of particular importance to users upgrading from a pre= vious release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information = on the changes. +
+
+ Kudzu + The kudzu utility, libkudzu library,= and /etc/sysconfig/hwconf hardware listing are all deprecated= , and will be removed in a future release of Fedora Core. Applications whi= ch need to probe for available hardware should be ported to use the HAL lib= rary. More information on HAL is available at http://freedesktop.org/wiki/Software/hal= . +
+
+ No automatic fstab editing for removable media + The fstab-sync facility has been removed. In Fed= ora Core , the fstab-sync program is removed in favor of deskt= op specific solutions for mounting removable media. Entries for hotplug de= vices or inserted media are no longer automatically added to the /etc= /fstab file. Command-line users may migrate to gnome-mount, which provides similar functionality. +
+
+ GnuCash + The PostgreSQL backend for GnuCash has been removed, as it is unmaintained upstream, does not suppor= t the full set of GnuCash features, an= d can lead to crashes. Users who use the PostgreSQL backend should load the= ir data and save it as an XML file before upgrading GnuCash. +
+
+ Mozilla + The Mozilla application s= uite is deprecated. It is shipped in Fedora Core and applications can exp= ect to build against mozilla-devel, however it will be removed= in a future release of Fedora Core. +
+
+ libstc++ preview + The libstdc++so7 package has been added. This pa= ckage contains a preview of the GNU Standard C++ Library from libstdc= xx_so_7-branch. It is considered experimental and unsupported. Do = not build any production software against it, as its ABI and so-version wil= l change in future upgrades. To build software using this library, invoke = g++-libstdc++so_7 instead of g++. +
- Basic Components - This section contains information related to basic system comp= onents. -
- Mouse Configuration Utility Removed - The system-config-mouse= configuration utility has been dropped in this release because synaptic an= d 3 button mouse configuration is being done automatically. Serial mice ar= e no longer supported. -
-
- Screensavers Not Installed by Default - Screensavers not installed by default anymore? Explain why a= nd provide commands to install them. -
-
- NetworkManager - Because it is not possible to test NetworkManager in all configurations, it is not enabled by de= fault in Fedora Core . - Refer to this page for information about enabling this appli= cation: - - http://fedoraproject.org/wiki/Tools/NetworkManager - -
-
- Dovecot - 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 previ= ous release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information on= the changes. - - -
+ LinuxThreads support removed + The LinuxThreads library is no longer available. LinuxThreads= was deprecated in Fedora Core 4 and is no longer available in this release= . The Native POSIX Threading Library (NPTL), which has been the default th= reading library since Red Hat Linux 9, has replaced LinuxThreads completely= .
-
Index: Printing.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Printing.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Printing.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Printing.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,16 +1,36 @@ - +
Temp -
- Printing - - - - - No changes to report. +
+ Docs/Beats/Printing + + + + + + + + + + +
+
+ + + + + + + /!\ + + REMOVE ME Before Publishing - Beat Commen= t +
+ This page is a stub for content. If you have a contributi= on for this release notes beat for the test release of Fedora Core, add it = to this page or create a sub-page. +
+ Beat writers: this is where you want to fill in with inst= ructions about how to post relevant information. Any questions that come u= p can be taken to a bugzilla report for discussion to resolution, or to fed= ora-docs-list for wider discussions. +
Index: ProjectOverview.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ProjectOverview.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ProjectOverview.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ProjectOverview.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,48 +1,74 @@ - +
Temp -
+
An Overview of the Fedora Project - The goal of the Fedora Project is to work with the Linux communi= ty to build a complete, general-purpose operating system exclusively from o= pen source software. Development is done in a public forum. The project pro= duces time-based releases of Fedora Core approximately 2-3 times a year, wi= th a public release schedule. The Red Hat engineering team continues to par= ticipate in building Fedora Core and invites and encourages more outside pa= rticipation 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 fre= e software and more appealing to the open source community. + The goal of the Fedora Project is to work with the Linux communi= ty to build a complete, general-purpose operating system exclusively from o= pen source software. Development is done in a public forum. The project pro= duces time-based releases of Fedora Core approximately 2-3 times a year, wi= th a public release schedule available at http://fedora.redhat.com/About/schedule/. Th= e 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. For more information, refer to the Fedora Project website: http://fedora.redhat.com/ - Your participation is welcome. See http://fedoraproject.org/wiki/HelpWanted= for details. - For communication in the Fedora Project look at http://fedoraproject.org/wiki/Comm= unicate. + The Fedora Project is driven by the individuals that contribute = to it. As a tester, developer, documenter or translator, you can make a dif= ference. See http:/= /fedoraproject.org/wiki/HelpWanted for details. + This page explains the channels of communication for Fedora user= s and contributors: + + http://fedo= raproject.org/wiki/Communicate. In addition to the website, the following mailing lists are avai= lable: - - - - fedora-list(a= )redhat.com - For users of Fedora Core releases - - - - fedora-t= est-list(a)redhat.com - For testers of Fedora Core test releases - - - - fedora-= devel-list(a)redhat.com - For developers, developers, developers - - - - fedora-d= ocs-list(a)redhat.com - For participants of the Documentation Proje= ct - - - 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.) - Alternately, you can subscribe through the Web interface: + + + + fedora-list(a)red= hat.com =EF=BF=BD=EF=BF=BD=EF=BF=BD For users of Fedora Core releas= es + + + + fedora-test-= list(a)redhat.com =EF=BF=BD=EF=BF=BD=EF=BF=BD For testers of Fedora= Core test releases + + + + fedora-deve= l-list(a)redhat.com =EF=BF=BD=EF=BF=BD=EF=BF=BD For developers, dev= elopers, developers + + + + fedora-docs-= list(a)redhat.com =EF=BF=BD=EF=BF=BD=EF=BF=BD For participants of t= he Documentation Project + + + To subscribe to any of these lists, send an email with the word = "subscribe" in the subject to <listname>-request, w= here <listname> is one of the above list names. + Alternately, you can subscribe to Fedora mailing lists through t= he Web interface: http://www.re= dhat.com/mailman/listinfo/ - The Fedora Project also includes an IRC (Internet Relay Chat) ch= annel. IRC is a real-time, text-based form of communication. With it, you c= an have conversations with multiple people in an open channel or chat with = someone privately one-on-one. - To talk with other Fedora Project participants via IRC, acce= ss freenode IRC network. Refer to the freenode website (http://www.freenode.net/) for more information= . Fedora Project participants frequent the #fedora channel, while Fedora Pr= oject developers can often be found on the #fedora-devel channel. Some of t= he larger projects may have their own channels as well; this information ca= n be found on the project pages and at http://fedoraproject.org/wiki/Communicate. - In order to talk on the #fedora channel, you will need to regist= er your nickname (nick). Instructions are given when you /join the channel.= - - IRC Content is Uncontrolled - Red Hat has no control over the Fedora Project IRC channels o= r their content. - + The Fedora Project also uses several IRC (Internet Relay Chat) c= hannels. IRC is a real-time, text-based form of communication, similar to I= nstant Messaging. With it, you may have conversations with multiple people = in an open channel, or chat with someone privately one-on-one. + To talk with other Fedora Project participants via IRC, access t= he Freenode IRC network. Refer to the Freenode website (http://www.freenode.net/) for more information= . + Fedora Project participants frequent the #fedora ch= annel on the Freenode network, whilst Fedora Project developers may often b= e found on the #fedora-devel channel. Some of the larger proje= cts may have their own channels as well; this information may be found on t= he webpage for the project, and at http://fedoraproject.org/wiki/Communicate. + In order to talk on the #fedora channel, you will n= eed to register your nickname, or nick. Instructions a= re given when you /join the channel. + + + + + + + + + +
+
+ + + + + + + {i} + + + IRC Channels + +
+ Fedora Foundation or Red Hat has no control over the = Fedora Project IRC channels or their content. +
+
+
Index: Samba.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Samba.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- Samba.xml 20 Feb 2006 19:01:04 -0000 1.2 +++ Samba.xml 28 Feb 2006 17:25:26 -0000 1.3 @@ -1,37 +1,15 @@ - +
Temp -
- Samba - - Content temporarily removed - - This section has been removed for the Fedora Core 5 test3 publication of - these release notes that is happening under the Opencontent Public - License (OPL), as specified in the . We - were not able to obtain permission from the contributor of this content - in time for publication. This or similar content is going to return for - the Fedora Core 5 final release. - - - + Windows Network Browsing + Fedora can now browse Windows shares, a feature known as SMB b= rowsing. In releases prior to Fedora Core , the firewall prevented the prop= er function of SMB browsing. With the addition of the ip_conntrack_n= etbios_ns kernel module to the 2.6.14 kernel, and corresponding enha= ncements to system-config-securitylevel, the firewall now properly handles SMB broadcasts and permits network bro= wsing. +
Index: Security.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Security.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Security.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Security.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,75 +1,68 @@ - +
Temp -
+
Security This section highlights various security items from Fedora Core.=
General Information - General introduction to the many proactive security features i= n Fedora, current status and policies is available from this page: - - http://fedor= aproject.org/wiki/Security - + A general introduction to the many proactive security features= in Fedora, current status and policies is available at http://fedoraproject.org/wiki/Security.
What's New
- PAM Module Deprecation + PAM module Deprecation - Pam_stack is deprecated in this release. - Linux-PAM 0.78 and later contains the include directive whic= h obsoletes the pam_stack module. pam_stack module usage is logged with a deprecation warning. It might be remov= ed in a future release. It must not be used in individual service configura= tions anymore. All packages in Fedora Core using PAM were modified so they = do not use it. - - Upgraded installations using older PAM stacks n= eed manual intervention - When a system is upgraded from previous Fedora Core rel= eases and the system admininstrator previously modified some service config= urations, those modified configuration files are not replaced when new pack= ages are installed. Instead, the new configuration fiels are created as .rpmnew files. Such service configurations must be fixed so= the pam_stack module is not used. Refer to the .rpmnew files for the actual changes needed. + Pam_stack is deprecated in this release. Linux-PAM= 0.78 and later contains the include directive which obsoletes= the pam_stack module. pam_stack 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 pack= ages in Fedora Core using PAM were modified so they do not use it. + + + + + + + + + +
+
+ + + + + + + (!) + + + Upgrading and PAM Stacks + +
+ When a system is upgraded from previous Fedora Co= re 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 configurati= on files are created as .rpmnew files. Such service configurat= ions must be fixed so the pam_stack module is not used. Refer = to the .rpmnew files for the actual changes needed. +
diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew - - Example /etc/pam.d/login: - -# OLD VERSION -#%PAM-1.0 -auth required pam_securetty.so -auth required pam_stack.so service=3Dsystem-auth -auth required pam_nologin.so -account required pam_stack.so service=3Dsystem-auth -password required pam_stack.so service=3Dsystem-auth -# pam_selinux.so close should be the first session rule -session required pam_selinux.so close -session required pam_stack.so service=3Dsystem-auth -session required pam_loginuid.so -session optional pam_console.so -# pam_selinux.so open should be the last session rule -session required pam_selinux.so open - - -# NEW VERSION -#%PAM-1.0 -auth required pam_securetty.so -auth include system-auth -# no module should remain after 'include' if 'sufficient' might -# be used in the included configuration file -# pam_nologin moved to account phase - it's more appropriate there -# other modules might be moved before the system-auth 'include' -account required pam_nologin.so -account include system-auth -password include system-auth -# pam_selinux.so close should be the first session rule -session required pam_selinux.so close -session include system-auth -# the system-auth config doesn't contain sufficient modules -# in the session phase -session required pam_loginuid.so -session optional pam_console.so -# pam_selinux.so open should be the last session rule -session required pam_selinux.so open - +
+
+ The following example shows the /etc/pam.d/login configuration file in its original form using pam_stack, and= then revised with the include directive. + + + #%PAM-1.0auth required pam_securetty.soauth = required pam_stack.so service=3Dsystem-authauth required = pam_nologin.soaccount required pam_stack.so service=3Dsystem-authp= assword required pam_stack.so service=3Dsystem-auth# pam_selinux.so c= lose should be the first session rulesession required pam_selinux.so= closesession required pam_stack.so service=3Dsystem-authsession = required pam_loginuid.sosession optional pam_console.so# pam_sel= inux.so open should be the last session rulesession required pam_sel= inux.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_nologi= n.soaccount include system-authpassword include system-auth#= pam_selinux.so close should be the first session rulesession required = pam_selinux.so closesession include system-auth# the system-auth= config doesn't contain sufficient modules# in the session phasesession = required pam_loginuid.sosession optional pam_console.so# pam_sel= inux.so open should be the last session rulesession required pam_sel= inux.so open + +
Buffer Overflow detection and variable reordering - All of the software in Fedora Core and Extras software repos= itory for this release is compiled using a security feature called fstack-protecter. fstack-protector puts a can= ary value on the stack of key functions, just before t= he return address and just before returning from that value. Then the cana= ry value is verified, and if there was a buffer overflow, the canary will n= o 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 imp= lementation of the IBM ProPolice/SSP feature and available as part of GC= C 4.1 compiler used in Fedora Core . - This is in addition to using FORTIFY_SOURCE from Fedora Core 4 onwards. + All of the software in Fedora Core and Extras software repos= itory for this release is compiled using a security feature called fs= tack-protector. fstack-protector places a canary value = on the stack of functions containing a local character array. Before retur= ning from a protected function, the canary value is verified. If there was= a buffer overflow, the canary will no longer match the expected value, abo= rting the program. The canary value is random each time the application is = started, making remote exploitation very difficult. The fstack-prote= ctor feature does not protect against heap-based buffer overflows. <= /para> + This is a security feature written by Red Hat developers, im= plementing the IBM ProPolice/SSP feature.= For more information about ProPolice/SS= P, refer to http://www.research.ibm.com/trl/projects/security/ssp/. Thi= s feature is available as part of the GCC 4.1 compiler used in Fedora Core = . + The FORTIFY_SOURCE security feature for g= cc and glibc introduced in Fedora Core 4 remains availa= ble. For more information about security features in Fedora, refer to http://fedorapro= ject.org/wiki/Security/Features. + + + + CategorySecurity +
Index: SecuritySELinux.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/SecuritySELinux.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- SecuritySELinux.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ SecuritySELinux.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,77 +1,42 @@ - +
Temp
SELinux - The new SELinux project pages have troubleshooting tips, explana= tions, and pointers to documentation and references: + The new SELinux project pages have troubleshooting tips, explana= tions, and pointers to documentation and references. Some useful links inc= lude the following: - New SELinux project pages: - - - - http://= fedoraproject.org/wiki/SELinux - - - + New SELinux project pages: http://fedoraproject.org/wiki/SELinux + - If you are having trouble: - - - - http://fedoraproject.org/wiki/SELinux/Troubleshooting - - - + Troubleshooting tips: http://fedoraproject.org/wiki/SELinux/Troub= leshooting + - Questions? - - - - ht= tp://fedora.redhat.com/docs/selinux-faq/ - - - + Frequently Asked Questions: http://fedora.redhat.com/docs/selinux-faq/ + - Looking for a list of SELinux commands? - - - - http://fedoraproject.org/wiki/SELinux/Commands - - - + Listing of SELinux commands: http://fedoraproject.org/wiki/SELinux/Comma= nds + - Want to know which domains are confined? - - - - http://fedoraproject.org/wiki/SELinux/Domains - - - + Details of confined domains: http://fedoraproject.org/wiki/SELinux/Domain= s +
Multi Category Security (MCS) - General use implementation of the more stringent Multilevel Se= curity (MLS). MCS is an enhancement to SELinux to allow users to label fil= es with categories. For example, Company_Con= fidential, CEO_EYES_ONLY, or Sysadmin= _Passwords. - For more information, you can read this article from the creat= or of MCS: - - http:= //james-morris.livejournal.com/5583.html - + MCS is a general-use implementation of the more stringent Mult= ilevel Security (MLS). MCS is an enhancement to SELinux to allow users to = label files with categories. Categories might include= Company_Confidential, CEO_EYES_ONLY, or Sy= sadmin_Passwords. For more information about MCS, refer to http://james-morris.li= vejournal.com/5583.html, an article by the author.
Multilevel Security (MLS) - A specific Mandatory Access Control (MAC) scheme that labels= processes and objects with special security levels. For example, an objec= t (a document file) can have the security level of { Secret, Proje= ctMeta }, where Secret is the sensitivity leve= l, and the ProjectMeta is the category. - Refer to this technical article for more information: + MLS is a specific Mandatory Access Control (MAC) scheme that= labels processes and objects with special security levels. For example, a= n object such as a document file can have the security level of { Sec= ret, ProjectMeta }, where Secret is the sensitivity lev= el, and ProjectMeta is the category. For more information abo= ut MLS, refer to http://james-morris.livejournal.com/5020.html. - htt= p://james-morris.livejournal.com/5020.html + CategorySecurity
Index: ServerTools.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/ServerTools.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- ServerTools.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ ServerTools.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,33 +1,43 @@ - +
Temp -
- Server Tools +
+ Docs/Beats/ServerTools This section highlights changes and additions to the various GUI= server and system configuration tools in Fedora Core.
system-config-printer
SMB Browsing Outside Local Network - Browsing for Samba print shares across subnets is now possib= le. In addition, if at least one WINS server has been specified in /etc/samba/smb.conf, the first address specified is used when= browsing. + You can now browse for Samba print shares across subnets. I= f you specify at least one WINS server in /etc/samba/smb.conf,= the first address is used when browsing.
Kerberos Support for SMB Printers - The system-config-printer application supports Kerberos auth= entication when adding a new SMB printer. To add the printer, the user mus= t possess a valid Kerberos ticket and /usr/sbin/printconf-gui must be launched via sudo. No username and password is stored in <= emphasis>/etc/cups/printers.conf. Printing is still possible if= the SMB print queue permits anonymous printing. + The system-config-printer application supports Kerberos authentication when adding a new SMB print= er. To add the printer, the user must possess a valid Kerberos ticket and = launch the printer configuration tool. Select System>= Administration>Printing from the = main menu, or use the following command: + + + su -c 'system-config-printer' + + + No username and password is stored in /etc/cups/printe= rs.conf. Printing is still possible if the SMB print queue permits = anonymous printing.
system-config-securitylevel
Trusted Service Additions - Samba is now listed in the "Trusted services" list and can t= hus be enabled to permit the firewall to pass SMB traffic. + Samba is now listed in the Trusted services list. To permit the firewall to pass SMB traffic, enable this option.=
Port Ranges - When defining "Other Ports" in the system-config-se= curitylevel tool, port ranges can now be specified. For example,= specifying "6881-6999:tcp" results in the addition of the following line t= o /etc/sysconfig/iptables: + When you define Other Ports in the system-config-securitylevel tool, you may = now specify port ranges. For example, if you specify 6881-6999:tcp, the following line is added to /etc/sysconfig/iptables:= + + A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p t= cp --dport 6881:6999 -j ACCEPT + +
Index: SystemDaemons.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/SystemDaemons.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- SystemDaemons.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ SystemDaemons.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,21 +1,41 @@ - +
Temp -
- System Daemons - - - - - No changes to report. +
+ Docs/Beats/SystemDaemons + + + + + + + + + + +
+
+ + + + + + + /!\ + + REMOVE ME Before Publishing - Beat Commen= t +
+ This page is a stub for content. If you have a contributi= on for this release notes beat for the test release of Fedora Core, add it = to this page or create a sub-page. +
+ Beat writers: this is where you want to fill in with inst= ructions about how to post relevant information. Any questions that come u= p can be taken to a bugzilla report for discussion to resolution, or to fed= ora-docs-list for wider discussions. +
+
System Services - No changes to report.
Index: WebServers.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/WebServers.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- WebServers.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ WebServers.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,46 +1,88 @@ - +
Temp -
+
Web Servers This section contains information on Web-related applications. <= /para>
httpd - Version 2.2 of the Apache HTTP Server is now included in Fedor= a Core. This release brings a number of improvements since the 2.0 series,= including: + Fedora Core now includes version 2.2 of the Apache HTTP Server= . This release brings a number of improvements over the 2.0 series, includ= ing: - greatly improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache)= + greatly improved caching modules (mod_cache,= mod_disk_cache, mod_mem_cache) - refactored authentication and authorization support + a new structure for authentication and authorization supp= ort, replacing the security modules provided in previous versions - support for proxy load balancing (mod_proxy_bala= nce) + support for proxy load balancing (mod_proxy_balance= ) - large file support for 32-bit platforms (including suppor= t for >2Gb request bodies) - - - new modules mod_dbd and mod_f= ilter bring SQL database support and enhanced filtering + large file support for 32-bit platforms (including suppor= t for serving files larger than 2Gb) + + + new modules mod_dbd and mod_filter, which bring SQL database support and enhanced filtering + + + + + + + +
+
+ + + + + + + {*} + + + Upgrading and Security Modules= + +
+ If you upgrade from a previous version of htt= pd, update your server configuration to use the new authentication a= nd authorization modules. Refer to the page listed below for more details. = +
- The following changes have been made to the default h= ttpd configuration: + The following changes have been made to the default http= d configuration: - the mod_cern_meta and mod_asi= s modules are no longer loaded by default + The mod_cern_meta and mod_asis = modules are no longer loaded by default. - the mod_ext_filter module is now loade= d by default + The mod_ext_filter module is now loaded by d= efault. + + + + + + + +
+
+ + + + + + + {*} + + + Third-party Modules + +
+ Any third-party modules compiled for httpd 2.0 must be rebuilt for httpd 2.2. +
- Any third-party modules compiled for httpd = 2.0 must be rebuilt for httpd 2.2. - Any existing configuration files might need adapting for 2.2. = For - more information, refer to - htt= p://httpd.apache.org/docs/2.2/upgrading.html. - + For more information on upgrading existing installations, refe= r to http://= httpd.apache.org/docs/2.2/upgrading.html.
php @@ -57,68 +99,68 @@ - date, hash, and Reflection (built-in with the php package) + date, hash, and Reflection (built-in with the php package) - pdo and pdo_psqlite (in = the php-pdo package) + pdo and pdo_psqlite (in the ph= p-pdo package) - pdo_mysql (in the php-mysql package) + pdo_mysql (in the php-mysql package)= - pdo_pgsql (in the php-pgsql package) + pdo_pgsql (in the php-pgsql package)= - pdo_odbc (in the php-odbc package) + pdo_odbc (in the php-odbc package) <= /para> - xmlreader and xmlwriter = (in the php-xml package) + xmlreader and xmlwriter (in the php-xml package) The following extension modules are no longer built: - dbx + dbx - dio + dio - yp + yp
The PEAR framework - The PEAR framework is now packaged in the php-pear<= /command> package; only the following PEAR components are included in Fedor= a Core: + The PEAR framework is now packaged in the php-pear package. Only the following PEAR components are included in Fedora Core= : - Archive_Tar + Archive_Tar - Console_Getopt + Console_Getopt - XML_RPC + XML_RPC - additional components may be packaged in Fedora Extras. + Additional components may be packaged in Fedora Extras.
Index: Welcome.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Welcome.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Welcome.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Welcome.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,36 +1,47 @@ - +
Temp -
+
+ Docs/Beats/Welcome +
Welcome to Fedora Core - - Fedora Core Test Release - This is a test release and is provided for develo= pers and testers to participate and provide feedback. It is not meant for e= nd users. - - - Join the Community for More Information - Subscribe to the fedora-test and fedora-devel mai= lings lists to keep track of important changes in the current development v= ersions and provide feedback to the developers. Fedora Project requests you= to file bug reports and enhancements to provide a improved final release t= o end users. See the following document for more information. - - http://fedoraproject.org/wiki/BugsAndFeatureRequests. Thank y= ou for your participation. - - - Latest Release Notes on the Web - These release notes may be updated. Visit http://fedora.redhat.com/docs/r= elease-notes/ to view the latest release notes for Fedora Core . - - Refer to these webpages to find out more information about Fed= ora: - Docs/Beats/OverView + + + + + + + +
+
+ + + + + + + (!) + + + Latest Release Notes on the We= b + +
+ These release notes may be updated. Visit http://fedora.redhat.com= /docs/release-notes/ to view the latest release notes for Fedora Co= re . +
+
+ You can help the Fedora Project community continue to improve = Fedora if you file bug reports and enhancement requests. Refer to http://fedorapr= oject.org/wiki/BugsAndFeatureRequests for more information about bu= gs. Thank you for your participation. + To find out more general information about Fedora, refer to th= e following Web pages: + - - Docs/Beats/Introductio= n - + Fedora Overview (http://fedoraproject.org/wiki/Overview) Fedora FAQ (http://fedoraproject.org/wiki/FAQ) @@ -45,5 +56,6 @@ About the Fedora Project (http://fedora.redhat.com/About/) +
Index: Xorg.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /cvs/docs/release-notes/en/Xorg.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Xorg.xml 17 Feb 2006 00:47:01 -0000 1.1 +++ Xorg.xml 28 Feb 2006 17:25:26 -0000 1.2 @@ -1,59 +1,100 @@ - +
Temp -
+
X Window System (Graphics) This section contains information related to the X Window System= implementation provided with Fedora.
xorg-x11 - X.org X11 is an open source implementation of the X Window Sys= tem. It provides the basic low level functionality which full fledged graph= ical user interfaces (GUIs) such as GNOME and KDE are designed upon. - For more information about Xorg refer to http://xorg.freedesktop.org/wiki/ - - You can use Applications =3D> System Settings =3D> Display or = system-config-display to configure the settings. The configuration file for= Xorg is located in /etc/X11/xorg.conf - Modular X.Org X11R7 RC2 was released into Fedora development (= rawhide) on November 16, 2005. This is the first modular release of Xorg wh= ich among several other benefits, enable users to receive updates in a fast= er pace and helps developers to develop and release specific components in = a rapid fashion. - More information on the current status of the Xorg modularizat= ion effort in Fedora is available from = http://fedoraproject.org/wiki/Xorg/Modularization - + X.org X11 is an open source implementation of the X Window Sys= tem. It provides the basic low-level functionality upon which full-fledged = graphical user interfaces (GUIs) such as GNOME and KDE are designed. For m= ore information about X.org, refer to http://xorg.freedesktop.org/wiki/. + You may use Applications > System Settings > Display= or system-config-display t= o configure the settings. The configuration file for X.org is located in /etc/X11/xorg.conf. + X.org X11R7 is the first modular release of X.org, which, amon= g several other benefits, promotes faster updates and helps programmers rap= idly develop and release specific components. More information on the curr= ent status of the X.org modularization effort in Fedora is available at http://fedora= project.org/wiki/Xorg/Modularization.
- Xorg X11R7.0 Developer Notes - X11R7.0 is included in this release and there are a number of = things that software developers, and packagers in Fedora repositories need = to be aware of in order to ensure that their software or software packages = properly compile and work with X11R7. Some are s= imple changes, while others may be more involved. Here is a summary of issu= es that may arise and where possible, suggestions on how to fix them. -
- The /usr/X11R6 Directory Hierarchy - X11R7 install into /usr directly = now, and no longer uses the /usr/X11R6 hierarchy= . Applications which rely on files being present at fixed paths under /usr/= X11R6 at compile time or at run time, must be up= dated to use the system PATH, or some other mechanism to dynamically determ= ine where the files reside, or alternatively to hard code the new locations= , possibly with fallbacks. -
-
- Imake - Imake is no longer used to build the X Window System, and as= such is now officially deprecated. Imake, xmkmf and other utilities previo= usly supplied by the X Window System, are still supplied in X11R7, 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 t= ransition away from it, and not use it for any new software projects. -
-
- The Systemwide <filename>app-defaults</filename> Directory<= /title> - <para>The system app-defaults directory for X resources, is now "%= {_datadir}/X11/app-defaults", which expands to /usr/share/X11/app-defaults = on Fedora Core 5 and for future Red Hat Enterprise Linux systems. </para> - </section> - <section> - <title>xft-config Can't Be Found - Modular X now uses GNU autotools, and pkg-config for its bui= ldsystem configuration, etc. xft-config has been deprecated for 2-3 years n= ow, and pkgconfig *.pc files have been provided for most of this time. Appl= ications which previously used xft-config to obtain the Cflags or libs opti= ons for building with, must now be updated to use pkg-config. -
+ X.org X11R7 End-User Notes + + + + + + + + + +
+
+ + + + + + + <!> + + + Installing Third Party Drivers= + +
+ Before you install any third party drivers from any= vendor, including ATI or nVidia, please read http://fedoraproject.org/wiki/Xor= g/3rdPartyVideoDrivers. +
+
+
+ The xorg-x11-server-Xorg package install scripts = automatically remove the RgbPath line from the xorg.conf= file if it is present. You may need to reconfigure your keyboard d= ifferently from what you are used to. You are encouraged to subscribe to t= he upstream xorg(a)freedesktop= .org mailing list if you do need assistance reconfiguring your keyb= oard.
- Xorg X11R7 Developer Overview - Here is a short list of some of the more developer/package vis= ible changes that are present in X11R7: + X.org X11R7 Developer Overview + The following list includes some of the more visible changes f= or developers in X11R7: - The entire buildsystem has changed from "Imake" to the GN= U autotools collection. + The entire buildsystem has changed from imake to the GNU autotools collection. - All of the libraries now install pkgconfig *.pc files, wh= ich should now always be used by software that depends on these libraries, = instead of hard coding paths to them in /usr/X11= R6/lib or elsewhere. + Libraries now install pkgconfig + *.pc files, which should now always be used by so= ftware that depends on these libraries, instead of hard coding paths to the= m in /usr/X11 + R6/lib or elsewhere. - Everything is now installed directly into /usr instead of= /usr/X11R6. All software which hard codes paths= to anything in /usr/X11R6, must now be changed = preferably to dynamically detect the proper location of the object, or to h= ard code the new paths that X11R7 uses by defaul= t. It is strongly advised to use autodetection methods than to hard code pa= ths. + Everything is now installed directly into /usr instead of /usr/X11 + R6. All software that hard codes paths to anythin= g in /usr/X11 + R6 must now be changed, preferably to dynamically= detect the proper location of the object. Developers are strongly advised against hard-coding the new X11R7 d= efault paths. - 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 libr= aries by using "BuildRequires: (XFree86-devel|xo= rg-x11-devel)", must now individually list each library dependency individu= ally. When doing this, it is greatly preferred and strongly recommended to = use "virtual" build dependencies instead of hard coding the library rpm pac= kage names of the xorg implementation. This means you should use: "BuildRequires: libXft-devel" instead of using: "BuildRequires: xorg-x11-Xft-devel". If your software tru= ly does depend on the X.Org X11 implementation of a specific library, and t= here 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/require= s mechanism, this ma! kes it painless if and when the libraries move to another location in the = future. + Every library has its own private source RPM package, whi= ch creates a runtime binary subpackage and a -devel subpackage= .
+
+ X.org X11R7 Developer Notes + This section includes a summary of issues of note for develope= rs and packagers, and suggestions on how to fix them where possible. +
+ The /usr/X11R6/ Directory Hierarchy + X11R7 files install into /usr directly now, and= no longer use the /usr/X11 + R6/ hierarchy. Applications that rely on files bein= g present at fixed paths under /usr/X11 + R6/, either at compile time or run time, must be up= dated. They should now use the system PATH, or some other mec= hanism to dynamically determine where the files reside, or alternatively to= hard code the new locations, possibly with fallbacks. +
+
+ Imake + The imake utility is no longer used to build th= e X Window System, and is now officially deprecated. X11R7 includes i= make, xmkmf, and other build utilities previously suppl= ied by the X Window System. X.Org highly recommends, however, that people= migrate from imake to use GNU autotools and pkg-config. Support for imake may be removed in a fut= ure X Window System release, so developers are st= rongly encouraged to transition away from it, and not use it for= any new software projects. +
+
+ The Systemwide app-defaults/ Directory + The system app-defaults/ directory for X resour= ces is now %{_datadir}/X11/app-defaults, which expands to /usr/share/X11/app-defaults/ on Fedora Core and for future Red Ha= t Enterprise Linux systems. +
+
+ Correct Package Dependencies + Any software package that previously used Build + Requires: (XFree86-devel|xorg-x11-devel) to satisfy= build dependencies must now individually list each library dependency. T= he preferred and recommended method is to use virtual = build dependencies instead of hard coding the library package names of the = xorg implementation. This means you should use Build + Requires: libXft-devel instead of Build + Requires: xorg-x11-Xft-devel. If your software trul= y does depend on the X.Org X11 implementation of a specific library, and th= ere is no other clean or safe way to state the dependency, then use the xorg-x11-devel form. If you use the virtual provides/requires mec= hanism, you will avoid inconvenience if the libraries move to another locat= ion in the future. +
+
+ xft-config + Modular X now uses GNU autotools and pkg-= config for its buildsystem configuration and execution. The x= ft-config utility has been deprecated for some time, and pkgco= nfig + *.pc files have been provided for most of this time= . Applications that previously used xft-config to obtain the <= code>Cflags or libs build options must now be updated t= o use pkg-config. +
+
--- PackageNotesJava.xml DELETED --- --===============7842936827611291603==--