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:=
code> 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"'=
screen>
+
+
+ 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) =
para>
- 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) =
para>
- =
YoshinariTakaoka (translator, tools)
+ TommyReynolds (tools) =
para>
- 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
-
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
-
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=
ulink>.
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
-