fedora-release README-i386-en, 1.1.1.1, 1.2 README-ppc-en, 1.1.1.1, 1.2 README-x86_64-en, 1.1.1.1, 1.2 RELEASE-NOTES-i386-en, 1.1.1.1, 1.2 RELEASE-NOTES-ppc-en, 1.1.1.1, 1.2 RELEASE-NOTES-x86_64-en, 1.1.1.1, 1.2 fedora-release.spec, 1.2, 1.3
Elliot Lee (sopwith)
fedora-extras-commits at redhat.com
Wed Apr 6 21:29:57 UTC 2005
- Previous message (by thread): rpms/xemacs-sumo/devel xemacs-sumo.spec,1.3,1.4
- Next message (by thread): fedora-release RELEASE-NOTES-i386-en, 1.2, 1.3 RELEASE-NOTES-ppc-en, 1.2, 1.3 RELEASE-NOTES-x86_64-en, 1.2, 1.3 index.html, 1.1.1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Author: sopwith
Update of /cvs/fedora/fedora-release
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv8443
Modified Files:
README-i386-en README-ppc-en README-x86_64-en
RELEASE-NOTES-i386-en RELEASE-NOTES-ppc-en
RELEASE-NOTES-x86_64-en fedora-release.spec
Log Message:
3.91
Index: README-i386-en
===================================================================
RCS file: /cvs/fedora/fedora-release/README-i386-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- README-i386-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ README-i386-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,4 +1,4 @@
- Fedora Core 3.90 README
+ Fedora Core 3.91 README
Copyright (c) 2005 Red Hat, Inc.
Index: README-ppc-en
===================================================================
RCS file: /cvs/fedora/fedora-release/README-ppc-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- README-ppc-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ README-ppc-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,4 +1,4 @@
- Fedora Core 3.90 README
+ Fedora Core 3.91 README
Copyright (c) 2005 Red Hat, Inc.
Index: README-x86_64-en
===================================================================
RCS file: /cvs/fedora/fedora-release/README-x86_64-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- README-x86_64-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ README-x86_64-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,4 +1,4 @@
- Fedora Core 3.90 README
+ Fedora Core 3.91 README
Copyright (c) 2005 Red Hat, Inc.
Index: RELEASE-NOTES-i386-en
===================================================================
RCS file: /cvs/fedora/fedora-release/RELEASE-NOTES-i386-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- RELEASE-NOTES-i386-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ RELEASE-NOTES-i386-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,955 +1,1009 @@
- Fedora Core 3.90 Release Notes
+== Fedora Core 4test2 Release Notes ==
- Copyright (c) 2004 Red Hat, Inc.
+Copyright (c) 2005 Red Hat, Inc.
- Permission is granted to copy, distribute, and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.2 or any
- later version published by the Free Software Foundation; with no Invariant
- Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the
- license is available at [1]http://www.gnu.org/licenses/fdl.html.
+Permission is granted to copy, distribute, and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is available at
+http://www.gnu.org/licenses/fdl.html.
+
+This document may be copied and distributed in any medium, either
+commercially or non-commercially, provided that the GNU Free
+Documentation License (FDL), the copyright notices, and the license
+notice saying the GNU FDL applies to the document are reproduced in
+all copies, and that you add no other conditions whatsoever to those
+of the GNU FDL.
+
+Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum
+RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
+RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based
+trademarks and logos are trademarks or registered trademarks of Red
+Hat, Inc. in the United States and other countries.
+
+The Fedora trademark is a trademark of Red Hat, Inc. in the United
+States and other countries.
+
+Linux is a registered trademark of Linus Torvalds.
+
+All other trademarks and copyrights referred to are the property of
+their respective owners.
+
+The GPG fingerprint of the "Fedora Project <fedora at redhat.com>" key
+is:
+
+CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
+
+---------------------------------------------------------------------------
+
+ 1. Fedora Core 4 test2 Release Notes
+ 2. Introduction
+ 3. Hardware Requirements
+ 1. CPU Requirements
+ 2. Hard Disk Space Requirements
+ 3. Memory Requirements
+ 4. Overview of This Release
+ 5. Installation-Related Notes
+ 6. Installation-Related Issues
+ 7. Package-Specific Notes
+ 1. Base
+ 2. Core
+ 3. Language Support
+ 4. Server Configuration Tools
+ 5. Sound and Video
+ 6. Web Server
+ 7. Windows File Server
+ 8. Macintosh File Server
+ 9. X Window System
+ 10. Miscellaneous Notes
+ 8. Packages Added, Moved From Core, Changed, or
+Deprecated/Nuked
+ 1. Packages Added
+ 2. Packages Moved Out Of Core
+ 9. An Overview of the Fedora Project
+ 10. References
+
+== Introduction ==
+
+The Fedora Project is an openly-developed project designed by Red Hat,
+open for general participation, led by a meritocracy, and following a
+set of project objectives. The results from this project include
+Fedora Core, a complete, general-purpose operating system built
+exclusively from open source software.
+
+NOTE: Fedora Core is not a supported product of Red Hat, Inc.
+
+For more information, refer to the Fedora Project overview later in
+this document.
+
+The following topics related to Fedora Core 4test2 are covered in this
+document:
+
+ * Introduction (this section)
+ * Hardware requirements
+ * Overview of this release
+ * Installation-related notes
+ * Package-specific notes
+ * Packages added/removed/deprecated
+ * An overview of the Fedora Project
+
+== Hardware Requirements ==
+
+The following information represents the minimum hardware requirements
+necessary to successfully install Fedora Core 4test2.
+
+Note
+
+The compatibility/availability of other hardware components (such as
+video and network cards) may be required for specific installation
+modes and/or post-installation usage.
+
+=== CPU Requirements ===
+
+This section lists the CPU specifications required by Fedora Core
+4test2.
+
+Note
+
+The following CPU specifications are stated in terms of Intel
+processors. Other processors (notably, offerings from AMD, Cyrix, and
+VIA) that are compatible with and equivalent to the following Intel
+processors may also be used with Fedora Core.
+
+ * Minimum: Pentium-class
+
+Fedora Core 4test2 is optimized for Pentium 4 CPUs, but also supports
+earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III,
+and including AMD and VIA variants). This approach has been taken
+because Pentium-class optimizations actually result in reduced
+performance for non-Pentium-class processors, and Pentium 4 scheduling
+is sufficiently different (while making up the bulk of today's
+processors) to warrant this change.
+
+ * Recommended for text-mode: 200 MHz Pentium-class or better
+
+ * Recommended for graphical: 400 MHz Pentium II or better
+
+=== Hard Disk Space Requirements ===
+
+This section lists the disk space required to install Fedora Core
+4test2.
+
+Note
+
+The disk space requirements listed below represent the disk space
+taken up by Fedora Core 4test2 after the installation is
+complete. However, additional disk space is required during the
+installation to support the installation environment. This additional
+disk space corresponds to the size of /Fedora/base/stage2.img (on
+CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed
+system.
+
+In practical terms, this means that as little as an additional 90MB
+can be required for a minimal installation, while as much as an
+additional 175MB can be required for an "everything" installation.
+
+Also, keep in mind that additional space will be required for any user
+data, and at least 5% free space should be maintained for proper
+system operation.
+
+ * Custom Installation (Minimal): 620MB
+ * Server: 1.1GB
+ * Personal Desktop: 2.3GB
+ * Workstation: 3.0GB
+ * Custom Installation (Everything): 6.9GB
+
+=== Memory Requirements ===
+
+This section lists the memory required to install Fedora Core 4test2.
+
+ * Minimum for text-mode: 64MB
+ * Minimum for graphical: 192MB
+ * Recommended for graphical: 256MB
+
+== Overview of This Release ==
+
+The following list highlights certain new features of Fedora Core
+4test2:
+
+ * GCC 4.0
+ * GNOME 2.10
+ * KDE 3.4
+ * Native Eclipse 3.1M5
+ * MySQL 4.1
+ * PHP 5.0
+
+ * SELinux -- New daemons have been added to the targeted policy For
+ more information, refer to the SELinux FAQ at
+ http://fedora.redhat.com/docs/selinux-faq/ .
+ * amanda
+ * apache
+ * chkpwd
+ * cups
+ * dhcpc
+ * dhcpd
+ * dictd
+ * dovecot
+ * fingerd
+ * ftpd
+ * howl
+ * i18n_input
+ * ifconfig
+ * init
+ * initrc
+ * inetd
+ * innd
+ * kerberos
+ * ktalkd
+ * ldconfig
+ * login
+ * lpd
+ * mailman
+ * modutil
+ * mta
+ * mysqld
+ * NetworkManager
+ * named
+ * nscd
+ * ntpd
+ * portmap
+ * postgresql
+ * privoxy
+ * radius
+ * radvd
+ * rlogind
+ * rpcd
+ * rshd
+ * rsync
+ * samba
+ * slapd
+ * snmpd
+ * squid
+ * stunnel
+ * syslogd
+ * telnetd
+ * tftpd
+ * winbind
+ * ypbind
+ * ypserv
+ * zebra
+
+== Installation-Related Notes ==
+
+This section outlines anything noteworthy that is related to Anaconda
+(the Fedora Core installation program) and installing Fedora Core
+4test2 in general.
+
+Note
+
+If you intend to download the Fedora Core 4test2 DVD ISO image, keep
+in mind that not all file downloading tools can accommodate files
+larger than 2GB in size. For example, wget will exit with a File size
+limit exceeded error.
+
+The curl and ncftpget file downloading tools do not have this
+limitation, and can successfully download files larger than 2GB.
+
+Bittorrent is another method for downloading large files.
+
+Anaconda Notes
+
+ * The Fedora Core installation program has the ability to test the
+integrity of the installation media. It works with the CD, DVD, hard
+drive ISO, and NFS ISO installation methods. Red Hat recommends that
+you test all installation media before starting the installation
+process, and before reporting any installation-related bugs (many of
+the bugs reported are actually due to improperly-burned CDs). To use
+this test, type linux mediacheck at the boot: prompt.
+
+ * Memory testing may be performed prior to installing Fedora Core by
+entering memtest86 at the boot: prompt. This causes the Memtest86
+standalone memory testing software to run. Memtest86 memory testing
+continues until the Esc key is pressed.
+
+NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use
+this feature.
+
+ * Fedora Core 4test2 supports graphical FTP and HTTP
+installations. However, due to the necessity of containing the
+installer image in RAM, only systems with more than 128MB of RAM (or
+systems booted from CD-ROM 1, which contains the installer image) can
+use the graphical installer. Systems with 128MB or less will continue
+to use the text-based installer.
+
+== Installation-Related Issues ==
+
+ * Certain hardware configurations (particularly those with LCD
+displays) may experience problems while starting the Fedora Core
+installation program. In these instances, restart the installation,
+and add the "nofb" option to the boot command line.
+
+NOTE: Chinese, Japanese, and Korean graphical installations started
+using the "nofb" option will start in English, and then switch to the
+appropriate language once the graphical phase of the installation
+process begins.
+
+ * Some Sony VAIO(R) notebook systems may experience problems
+installing Fedora Core from CD-ROM. If this happens, restart the
+installation process and add the following option to the boot command
+line:
+
+pci=off ide1=0x180,0x386
+
+This option allows the installation to proceed normally; any devices
+not detected due to the use of this option will be configured the
+first time Fedora Core is booted.
+
+ * Serial mice are known to be inoperative during
+installation. However, there are indications that serial mice work
+properly in X after the installation has completed. Refer to bug
+119474 for more information:
+
+[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
+
+ * There have been issues observed when upgrading Red Hat Linux
+7.<x>, 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The
+issue is caused by version overlap between the official Red Hat Linux
+RPMs (or the ones from the Fedora Project) and the Ximian RPMs. This
+configuration is not supported. You have several choices in resolving
+this issue:
+
+1) You may remove Ximian GNOME from your system prior to upgrading to
+Fedora Core.
+
+2) You may upgrade your system, and then immediately reinstall Ximian
+GNOME.
+
+3) You may upgrade your system, and then immediately remove all
+remaining Ximian RPMs, replacing them with the corresponding Fedora
+Core RPMs.
+
+You must resolve the version overlap using one of the above choices.
+Failure to do so will result in an unstable GNOME configuration.
+
+== Package-Specific Notes ==
+
+The following sections contain information regarding packages that
+have undergone significant changes for Fedora Core 4test2. For easier
+access, they are organized using the same groups used in Anaconda.
+
+=== Base ===
+
+This section contains information related to basic system components.
+
+slocate database
+
+The database needed by the locate utility is no longer created by
+default. Enable the database creation by setting DAILY_UPDATE to
+"yes" in /etc/updatedb.conf if you want to use locate.
+
+openssh
+
+The version of OpenSSH in Fedora Core 4test2 contains OpenSSH 3.9
+includes strict permission and ownership checks for the ~/.ssh/config
+file. These checks mean that ssh will exit if this file does not have
+appropriate ownership and permissions.
+
+Therefore, make sure that ~/.ssh/config is owned by the owner of ~/,
+and that its permissions are set to mode 600.
+
+In addition, OpenSSH is no longer configured to request X11 forwarding
+by default when connecting to servers. To enable X11 forwarding, the
+-X or -Y option must be specified, or the ForwardX11 option must be
+enabled in the ~/.ssh/config file.
+
+The behavior of ssh clients that are invoked with the -X flag has
+changed. In OpenSSH 3.8 and later, X11 forwarding is performed in a
+way that applications run as untrusted clients by default. Previously,
+X11 forwarding was performed so that applications always ran as
+trusted clients. Some applications may not function properly when run
+as untrusted clients. To forward X11 so that applications are run as
+trusted clients, invoke ssh with the -Y flag instead of the -X flag,
+or set ForwardX11Trusted in the ~/.ssh/config file.
+
+=== Core ===
+
+This section contains the most elemental components of Fedora Core,
+including the kernel.
+
+ * In order to eliminate the redundancy inherent in providing a
+separate package for the kernel source code when that source code
+already exists in the kernel's .src.rpm file, Fedora Core 4test2 no
+longer includes the kernel-source package. Users that require access
+to the kernel sources can find them in the kernel .src.rpm file. To
+create an exploded source tree from this file, perform the following
+steps (note that <version> refers to the version specification for
+your currently-running kernel):
+
+ 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:
+
+ up2date --get-source kernel
+
+ 2. Install kernel-<version>.src.rpm (given the default RPM
+configuration, the files this package contains will be written to
+/usr/src/redhat/)
+
+ 3. Change directory to /usr/src/redhat/SPECS/, and issue the
+following command:
+
+ rpmbuild -bp --target=<arch> kernel.spec
+
+ (Where <arch> is the desired target architecture.)
+
+ On a default RPM configuration, the kernel tree will be
+located in /usr/src/redhat/BUILD/.
+
+ 4. In resulting tree, the configurations for the specific
+kernels shipped in Fedora Core 4test2 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 configuration file in the proper place for
+building:
+
+ cp <desired-file> ./.config
+
+ 5. Issue the following command:
+
+ make oldconfig
+
+You can then proceed as usual.
+
+Note
+
+An exploded source tree is not required to build kernel modules
+against the currently in-use kernel.
+
+For example, to build the foo.ko module, create the following file
+(named Makefile) in the directory containing the foo.c file:
+
+obj-m := foo.o
+
+KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
+
+default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
+
+
+Issue the make command to build the foo.ko module.
+
+=== Language Support ===
+
+This section includes information related to the support of various
+languages under Fedora Core.
+
+=== Server Configuration Tools ===
+
+This section contains information related to various server
+configuration tools.
+
+=== Sound and Video ===
+
+This section contains information related to multimedia applications.
+
+
+=== Web Server ===
+
+This section contains information related to Web-related tools.
+
+php
+
+Version 5.0 of PHP is now included, which includes a number of changes
+to the language along with significant performance improvements.
+Please refer to the PHP documentation for more information on
+migrating from PHP 4.3 to PHP 5.0:
+
+http://www.php.net/manual/en/migration5.php
+
+The following extensions have been added:
+
+ * the "mysqli" extension, the newly MySQL interface designed
+ specifically for MySQL 4; included in the php-mysql
+ * the "soap" extension, which can be used to implement a SOAP server
+ or client
+
+=== Windows File Server ===
+
+This section contains information related to Samba, software that
+makes it possible to share files between Linux and Windows systems.
+
+samba
+
+Browsing of Windows shares (also known as SMB browsing) fails on
+Fedora Core 4test2 systems that have the standard firewall
+configured. This is most easily noticed in the failure of Nautilus to
+display shares. The failure is due to the firewall disrupting the
+broadcast mode of SMB browsing, which is Samba's default
+setting. There are two workarounds:
+
+ * Configure a WINS server on the network, and set the "wins server"
+option in smb.conf to the address of the WINS server.
+
+ * Disable the firewall
+
+Warning
+
+Depending on your system and network configurations, disabling the
+firewall can greatly increase the chance of your system being attacked
+and compromised. Make sure you fully understand the risks before
+undertaking this step.
+
+For additional information, refer to the following bug report:
+
+[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
+
+
+=== Macintosh File Server ===
+
+This section contains information related to netatalk, software that
+makes it possible to share files between Linux and Macintosh systems.
+
+netatalk
+
+The 2.x version of netatalk uses a different method to store resource
+forks, and may use a different file name encoding scheme. Upgrading to
+Fedora Core 4 may result in data loss. Please read the documentation
+of the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.
+
+The netatalk upgrade information is available directly from the
+netatalk site:
+
+http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html
+
+It is also included in the netatalk installation for Fedora Core 4,
+the files are at:
+
+/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page
+25, document page 33.
+
+or
+
+/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html
+
+=== X Window System ===
+
+This section contains information related to the X Window System
+implementation provided with Fedora Core.
+
+xorg-x11
+
+ * Users new to the X.org X11 implementation should take note of a
+few differences between it and the XFree86.org X11 implementation
+which shipped in previous Red Hat operating systems. In particular,
+the names of some files have changed:
+
+X Server Binary:
+
+ * XFree86 X11: XFree86
+
+ * X.org X11: Xorg
+
+X Server Configuration File:
+
+ * XFree86 X11: /etc/X11/XF86Config
+
+ * X.org X11: /etc/X11/xorg.conf
+
+X Server Log File
+
+ * XFree86 X11: /var/log/XFree86.$DISPLAY.log
+
+ * X.org X11: /var/log/Xorg.$DISPLAY.log
+
+When configuring or troubleshooting your X server configuration, be
+sure that you are using the correct files.
+
+ * There has been some confusion regarding font-related issues under
+the X Window System in recent versions of Fedora Core (and versions of
+Red Hat Linux before it.) At the present time, there are two font
+subsystems, each with different characteristics:
+
+- The original (15+ year old) subsystem is referred to as the "core X
+font subsystem". Fonts rendered by this subsystem are not
+anti-aliased, are handled by the X server, and have names like:
+
+-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
+
+The newer font subsystem is known as "fontconfig", and allows
+applications direct access to the font files. Fontconfig is often used
+along with the "Xft" library, which allows applications to render
+fontconfig fonts to the screen with antialiasing. Fontconfig uses more
+human-friendly names like:
+
+Luxi Sans-10
+
+ * Over time, fontconfig/Xft will replace the core X font
+subsystem. At the present time, applications using the Qt 3 or GTK 2
+toolkits (which would include KDE and GNOME applications) use the
+fontconfig and Xft font subsystem; almost everything else uses the
+core X fonts.
+
+In the future, Fedora Core may support only fontconfig/Xft in place of
+the XFS font server as the default local font access method.
+
+NOTE: An exception to the font subsystem usage outlined above is
+OpenOffice.org (which uses its own font rendering technology).
+
+If you wish to add new fonts to your Fedora Core 4test2 system, you
+must be aware that the steps necessary depend on which font subsystem
+is to use the new fonts. For the core X font subsystem, you must:
+
+1. Create the /usr/share/fonts/local/ directory (if it doesn't already
+exist):
+
+mkdir /usr/share/fonts/local/
+
+2. Copy the new font file into /usr/share/fonts/local/
+
+3. Update the font information by issuing the following commands (note
+that, due to formatting restrictions, the following commands may
+appear on more than one line; in use, each command should be entered
+on a single line):
+
+ttmkfdir -d /usr/share/fonts/local/ -o
+/usr/share/fonts/local/fonts.scale
+
+mkfontdir /usr/share/fonts/local/
+
+4. If you had to create /usr/share/fonts/local/, you must then add it
+to the X font server (xfs) path:
+
+chkfontpath --add /usr/share/fonts/local/
+
+Adding new fonts to the fontconfig font subsystem is more
+straightforward; the new font file only needs to be copied into the
+/usr/share/fonts/ directory (individual users can modify their
+personal font configuration by copying the font file into the
+~/.fonts/ directory).
+
+After the new font has been copied, use fc-cache to update the font
+information cache:
+
+fc-cache <directory>
+
+(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
+directories.)
+
+Individual users may also install fonts graphically, by browsing
+fonts:/// in Nautilus, and dragging the new font files there.
+
+NOTE: If the font filename ends with ".gz", it has been compressed
+with gzip, and must be decompressed (with the gunzip command) before
+the fontconfig font subsystem can use the font.
+
+ * Due to the transition to the new font system based on
+fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes
+made via the Font Preferences dialog. For these applications, a font
+can be configured by adding the following lines to the file
+~/.gtkrc.mine:
+
+style "user-font" {
+
+fontset = "<font-specification>"
+
+}
+
+widget_class " *" style "user-font"
+
+(Where <font-specification> represents a font specification in the
+style used by traditional X applications, such as
+"-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
+
+=== Miscellaneous Notes ===
+
+This section contains information related to packages that do not fit
+in any of the proceeding categories.
+
+
+== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
+
+For an overview of orphaned packages, visit
+[:Extras/OrphanedPackages:this list].
+
+This section contains lists of packages that fit into the following
+categories:
+
+ * Packages that have been added to Fedora Core 4test2
+
+ * Packages that have been moved out of Fedora Core 4test2
+
+ * Packages that have a changed version since Fedora Core 3
+
+ * Packages that have been deprecated, and may be removed from a
+future
+ release of Fedora Core
+
+=== Packages Added ===
+
+The following packages have been added to Fedora Core 4test2:
+
+ * ant-1.6.2-3jpp_2fc
+ * antlr-2.7.4-2jpp_1fc
+ * aqbanking-1.0.4beta-2
+ * aqhbci-1.0.2beta-2
+ * avalon-framework-4.1.4-2jpp_5fc
+ * avalon-logkit-1.2-2jpp_4fc
+ * bcel-5.1-1jpp_4fc
+ * classpath-inetlib-1.0-1jpp_1fc
+ * classpathx-jaf-1.0-2jpp_3fc
+ * classpathx-mail-1.0-3jpp_1fc
+ * compat-gcc-296-2.96-132.fc4
+ * compat-gcc-32-3.2.3-47.fc4
+ * compat-readline43-4.3-2
+ * cpufreq-utils-0.2-1.1.12
+ * cpuspeed-1.2.1-1.19
+ * cryptix-3.2.0-4jpp_1fc
+ * cryptix-asn1-20011119-4jpp_1fc
+ * cryptsetup-luks-1.0-1
+ * dcraw-0.0.20050227-1
+ * device-mapper-multipath-0.4.4-0.pre8.0
+ * dmidecode-2.6-1.13
+ * eclipse-3.1.0_fc-0.M5.17
+ * eclipse-bugzilla-0.1.0_fc-9
+ * eclipse-cdt-3.0.0_fc-0.M5.3
+ * eclipse-changelog-2.0.1_fc-19
+ * eclipse-pydev-0.9.0_fc-4
+ * evince-0.1.9-1
+ * fonts-chinese-2.15-1
+ * fonts-indic-1.9-2
+ * fonts-japanese-0.20050222-2
+ * fonts-korean-1.0.11-2
+ * gjdoc-0.7.3-1
+ * gnome-doc-utils-0.1.3-1
+ * gnome-menus-2.10.1-1
+ * gnome-python2-extras-2.10.0-2.1
+ * gnu-crypto-2.0.1-1jpp_1fc
+ * gnu.getopt-1.0.9-4jpp_1fc
+ * gwenhywfar-1.7.2-2
+ * hardlink-1.0-1.11
+ * iiimf-12.1.1-11.svn2435
+ * ipv6calc-0.48-3
+ * irqbalance-1.12-1.18
+ * jakarta-commons-beanutils-1.7.0-1jpp_1fc
+ * jakarta-commons-collections-3.1-1jpp_1fc
+ * jakarta-commons-daemon-1.0-2jpp_1fc
+ * jakarta-commons-dbcp-1.2.1-3jpp_1fc
+ * jakarta-commons-digester-1.6-2jpp_1fc
+ * jakarta-commons-el-1.0-2jpp_1fc
+ * jakarta-commons-fileupload-1.0-3jpp_1fc
+ * jakarta-commons-lang-2.0-2jpp_1fc
+ * jakarta-commons-launcher-0.9-3jpp_1fc
+ * jakarta-commons-logging-1.0.4-2jpp_1fc
+ * jakarta-commons-modeler-1.1-3jpp_1fc
+ * jakarta-commons-pool-1.2-2jpp_1fc
+ * jakarta-commons-validator-1.1.3-1jpp_1fc
+ * jakarta-taglibs-standard-1.1.1-4jpp_1fc
+ * java_cup-0.10-0.k.1jpp_2fc
+ * jdepend-2.6-2jpp_3fc
+ * jessie-1.0.0-3
+ * jlex-1.2.6-1jpp_2fc
+ * jsch-0.1.17-2jpp_1fc
+ * junit-3.8.1-3jpp_4fc
+ * jzlib-1.0.5-2jpp_1fc
+ * kdeaccessibility-3.4.0-1
+ * ksh-20050202-1
+ * latex2html-2002.2.1-1
+ * ldapjdk-4.17-1jpp_2fc
+ * libdbi-drivers-0.7.1-2
+ * libgconf-java-2.10.0-1
+ * libglade-java-2.9.92-1
+ * libgnome-java-2.9.92-1
+ * libgtk-java-2.6.1.1-1
+ * linux-atm-2.5.0-0.20050118.2
+ * lksctp-tools-1.0.2-5
+ * log4j-1.2.8-7jpp_3fc
+ * longrun-0.9-1.8
+ * lvm2-cluster-2.00.29-1.22.FC4
+ * mcelog-0.4-1.8
+ * microcode_ctl-1.11-1.21
+ * mod_jk-1.2.6-3jpp_1fc
+ * mx4j-2.1.0-1jpp_2fc
+ * mysqlclient10-3.23.58-5
+ * openhpi-2.0.3-2
+ * OpenIPMI-1.4.11-5
+ * openssl097a-0.9.7a-2
+ * oro-2.0.8-1jpp_2fc
+ * poppler-0.1.2-1
+ * puretls-0.9-0.b4.1jpp_2fc
+ * python-docs-2.4-102
+ * python-elementtree-1.2.6-4
+ * python-numeric-23.7-2
+ * python-sqlite-1.1.6-1
+ * python-twisted-1.3.0-4
+ * python-urlgrabber-2.9.6-1
+ * readahead-1.0-1.7
+ * regexp-1.3-1jpp_4fc
+ * rng-utils-2.0-1.5
+ * salinfo-0.5-1.4
+ * servletapi5-5.0.18-1jpp_3fc
+ * slib-3a1-2
+ * smartmontools-5.33-1.5
+ * sqlite-3.1.2-2
+ * struts11-1.1-1jpp_2fc
+ * system-config-lvm-0.9.22-1.0
+ * texi2html-1.76-2
+ * tomcat5-5.0.30-1jpp_2fc
+ * x86info-1.13-1.9
+ * xalan-j2-2.6.0-2jpp_1fc
+ * xen-2-20050403
+ * xerces-j2-2.6.2-4jpp_1fc
+ * xml-commons-1.0-0.b2.6jpp_5fc
+ * xml-commons-resolver-1.1-1jpp_4fc
+
+=== Packages Moved Out Of Core ===
+
+This is a new section to the release notes. This is based on a
+treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following
+packages have been moved out of core from Fedora Core 4test2:
+
+ * abiword-2.0.12-3
+ * aiksaurus-1.2.1-2
+ * ash-0.3.8-20
+ * asp2php-0.76.18-3
+ * aspell-ia-0.50-1
+ * aumix-2.8-9
+ * balsa-2.2.4-1.FC3.1
+ * bluez-bluefw-1.0-6
+ * bonobo-1.0.22-9
+ * bzflag-1.10.6-2
+ * cdecl-2.5-30
+ * cdlabelgen-3.0.0-1
+ * cdp-0.33-32
+ * compat-gcc-8-3.3.4.2
+ * compat-pwdb-0.62-9
+ * comsat-0.17-11
+ * cproto-4.7c-3
+ * cryptsetup-0.1-4
+ * cyrus-imapd-2.2.6-2.FC3.6
+ * dbh-1.0.18-5
+ * dbskkd-cdb-1.01-21
+ * ddskk-12.2.0-4
+ * dietlibc-0.27-4
+ * diskcheck-1.6-2
+ * dmalloc-5.3.0-3
+ * exim-4.43-1
+ * flim-1.14.7-1
+ * fonts-bengali-0.1-3
+ * fonts-ja-8.0-16
+ * freeciv-1.14.2-1
+ * FreeWnn-1.10pl020-5
+ * fsh-1.2-5
+ * ftpcopy-0.6.2-7
+ * gcc4-4.0.0-0.8
+ * ggv-2.8.0-1
+ * giftrans-1.12.2-20
+ * Glide3-20010520-33
+ * gnome-vfs-1.0.5-21
+ * gnome-vfs-extras-0.2.0-9
+ * gnuchess-5.07-4
+ * gnumeric-1.2.13-6
+ * gpdf-2.8.0-5
+ * grip-3.2.0-3
+ * gv-3.5.8-29
+ * im-sdk-12.1-4
+ * jed-0.99.16-6
+ * jisksp14-0.1-16
+ * jisksp16-1990-0.1-16
+ * kappa20-0.3-15
+ * kdetoys-3.3.0-1
+ * kernel-utils-2.4-13.1.39
+ * kinput2-v3.1-23
+ * knm_new-1.1-16
+ * koffice-1.3.3-1
+ * lapack-3.0-25
+ * lesstif-0.93.36-6
+ * libesmtp-1.0.3r1-2
+ * libgda-1.0.4-3
+ * libgnomedb-1.0.4-3
+ * libtool-libs13-1.3.5-10
+ * libxfce4mcs-4.0.6-1
+ * libxfce4util-4.0.6-1
+ * libxfcegui4-4.0.6-1
+ * lilo-21.4.4-26
+ * Maelstrom-3.0.6-6
+ * MagicPoint-1.11b-1
+ * memprof-0.5.1-5
+ * mew-3.3-4
+ * miniChinput-0.0.3-58
+ * nabi-0.14-3
+ * namazu-2.0.13-3
+ * nautilus-media-0.8.1-3
+ * ncftp-3.1.8-2
+ * nedit-5.4-3
+ * octave-2.1.57-7
+ * Omni-0.9.1-7
+ * openhbci-0.9.17-1
+ * openssl096b-0.9.6b-19
+ * ots-0.4.2-2
+ * pan-0.14.2-8
+ * pccts-1.33mr33-11
+ * pdksh-5.2.14-30
+ * qmkbootdisk-1.0.2-3
+ * Regina-2.3-1
+ * routed-0.17-18
+ * skkinput-2.06.4-7
+ * splint-3.1.1-4
+ * sylpheed-0.9.12-1
+ * system-logviewer-0.9.11-1
+ * system-switch-im-0.1.2-3
+ * THE-3.1-2
+ * tora-1.3.14.1-2
+ * ttfonts-indic-1.6-1
+ * ttfonts-ja-1.2-36
+ * ttfonts-ko-1.0.11-32.2
+ * ttfonts-zh_CN-2.14-10
+ * ttfonts-zh_TW-2.11-28
+ * ttfprint-0.9-13
+ * tuxracer-0.61-28
+ * w3m-el-1.4.3-2
+ * wl-2.10.1-4
+ * x3270-3.3.2.p1-6
+ * xboard-4.2.7-6
+ * xcin-2.5.3.pre3-24
+ * xemacs-21.4.15-9
+ * xemacs-sumo-20040818-2
+ * xfce4-iconbox-4.0.6-2
+ * xfce4-panel-4.0.6-1
+ * xfce4-systray-4.0.6-2
+ * xfce-mcs-manager-4.0.6-2
+ * xfce-mcs-plugins-4.0.6-2
+ * xfce-utils-4.0.6-1
+ * xfdesktop-4.0.6-2
+ * xffm-4.0.6-1
+ * xffm-icons-4.0.6-2
+ * xfprint-4.0.6-2
+ * xfwm4-4.0.6-1
+ * xfwm4-themes-4.0.6-2
+ * xloadimage-4.1-32
+ * xmms-1.2.10-9
+ * xosview-1.8.2-1
+ * xsnow-1.42-15
+ * ytalk-3.1.2-1
+
+== An Overview of the Fedora Project ==
+
+The goal of the Fedora Project is to work with the Linux community to
+build a complete, general purpose operating system exclusively from
+open source software. Development will be done in a public forum. The
+project will produce time-based releases of Fedora Core about 2-3
+times a year, with a public release schedule. The Red Hat engineering
+team will continue to participate in building Fedora Core and will
+invite and encourage 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:
+
+[10]http://fedora.redhat.com/
+
+In addition to the website, the following mailing lists are available:
+
+ * fedora-list at redhat.com -- For users of Fedora Core releases
+ * fedora-test-list at redhat.com -- For testers of Fedora Core test
+releases
+ * fedora-devel-list at redhat.com -- For developers, developers,
+developers
+ * fedora-docs-list at redhat.com -- For participants of the docs
+project
+
+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.)
+
+NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
+rhl-devel-list, or rhl-docs-list, your subscriptions have been
+retained.
+
+The Fedora Project also includes an IRC (Internet Relay Chat)
+channel. IRC is a real-time, text-based form of communication. With
+it, you can have conversations with multiple people in an open channel
+or chat with someone privately one-on-one.
+
+To talk with other Fedora Project participants via IRC, access
+freenode IRC network. Initially, you can use irc.freenode.net as the
+IRC server, although you may decide to select a server that is
+geographically closer to you. Refer to the freenode website
+([11]http://www.freenode.net/) for more information. Fedora Project
+participants frequent the #fedora channel, while Fedora Project
+developers can often be found on the #fedora-devel channel. Some of
+the larger projects may have their own channels as well; this
+information can be found on the project pages.
+
+NOTE: Red Hat has no control over the Fedora IRC channels or their
+content.
+
+( x86 )
+
+== References ==
+
+Visible links
+
+1. http://www.gnu.org/licenses/fdl.html
+
+2. http://fedora.redhat.com/docs/selinux-faq/
+
+3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
+
+4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
+
+5. http://platan.vc.cvut.cz/ftp/pub/vmware/
+
+6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
+
+7. http://i2o.shadowconnect.com/
- This document may be copied and distributed in any medium, either
- commercially or non-commercially, provided that the GNU Free Documentation
- License (FDL), the copyright notices, and the license notice saying the
- GNU FDL applies to the document are reproduced in all copies, and that you
- add no other conditions whatsoever to those of the GNU FDL.
+8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
- Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM,
- the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember,
- RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and
- logos are trademarks or registered trademarks of Red Hat, Inc. in the
- United States and other countries.
+9. http://people.redhat.com/~harald/udev.html
- The Fedora trademark is a trademark of Red Hat, Inc. in the United States
- and other countries.
+10. http://fedora.redhat.com/
- Linux is a registered trademark of Linus Torvalds.
-
- All other trademarks and copyrights referred to are the property of their
- respective owners.
-
- The GPG fingerprint of the "Fedora Project <fedora at redhat.com>" key is:
-
- CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
-
- ---------------------------------------------------------------------------
-
-Note: These release notes cover Fedora Core 3. Although additional
-changes have been introduced then, we don't yet have a good summary of
-those changes. We do plan to have that summary by FC4 final release.
-
- ---------------------------------------------------------------------------
-Introduction
-
- The Fedora Project is an openly-developed project designed by Red Hat,
- open for general participation, led by a meritocracy, and following a set
- of project objectives. The results from this project include Fedora Core,
- a complete, general-purpose operating system built exclusively from open
- source software.
-
- Note
-
- Fedora Core is not a supported product of Red Hat, Inc.
-
- For more information, refer to the Fedora Project overview later in this
- document.
-
- The following topics related to Fedora Core 3 are covered in this
- document:
-
- o Introduction (this section)
-
- o Hardware requirements
-
- o Overview of this release
-
- o Installation-related notes
-
- o Package-specific notes
-
- o Packages added/removed/deprecated
-
- o An overview of the Fedora Project
-
-Hardware Requirements
-
- The following information represents the minimum hardware requirements
- necessary to successfully install Fedora Core 3.
-
- Note
-
- The compatibility/availability of other hardware components (such as video
- and network cards) may be required for specific installation modes and/or
- post-installation usage.
-
- CPU Requirements
-
- This section lists the CPU specifications required by Fedora Core 3.
-
- Note
-
- The following CPU specifications are stated in terms of Intel processors.
- Other processors (notably, offerings from AMD, Cyrix, and VIA) that are
- compatible with and equivalent to the following Intel processors may also
- be used with Fedora Core.
-
- o Minimum: Pentium-class
-
- Fedora Core 3 is optimized for Pentium 4 CPUs, but also supports
- earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III,
- and including AMD and VIA variants). This approach has been taken
- because Pentium-class optimizations actually result in reduced
- performance for non-Pentium-class processors, and Pentium 4 scheduling
- is sufficiently different (while making up the bulk of today's
- processors) to warrant this change.
-
- o Recommended for text-mode: 200 MHz Pentium-class or better
-
- o Recommended for graphical: 400 MHz Pentium II or better
-
- Hard Disk Space Requirements
-
- This section lists the disk space required to install Fedora Core 3.
-
- Note
-
- The disk space requirements listed below represent the disk space taken up
- by Fedora Core 3 after the installation is complete. However, additional
- disk space is required during the installation to support the installation
- environment. This additional disk space corresponds to the size of
- /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in
- /var/lib/rpm on the installed system.
-
- In practical terms, this means that as little as an additional 90MB can be
- required for a minimal installation, while as much as an additional 175MB
- can be required for an "everything" installation.
-
- Also, keep in mind that additional space will be required for any user
- data, and at least 5% free space should be maintained for proper system
- operation.
-
- o Custom Installation (Minimal): 620MB
-
- o Server: 1.1GB
-
- o Personal Desktop: 2.3GB
-
- o Workstation: 3.0GB
-
- o Custom Installation (Everything): 6.9GB
-
- Memory Requirements
-
- This section lists the memory required to install Fedora Core 3.
-
- o Minimum for text-mode: 64MB
-
- o Minimum for graphical: 192MB
-
- o Recommended for graphical: 256MB
-
-Overview of This Release
-
- The following list includes brief summaries of some of the more
- significant aspects of Fedora Core 3:
-
- o Fedora Core 3 contains the following changes:
-
- o GCC 3.4
-
- o GNOME 2.8
-
- o KDE 3.3
-
- o SELinux -- This includes a new "targeted" policy that monitors
- specific daemons with less intrusion than the strict policy in
- use before. This policy is enabled by default. For more
- information, refer to:
-
- [2]http://fedora.redhat.com/docs/selinux-faq/
-
- o Indic language support
-
- o Kernel and e2fsprogs support for online growing of ext3 file
- systems
-
- o Various desktop-related features, including, but not limited to:
-
- o Remote desktops using VNC
- ([3]http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html)
-
- o Printing improvements
- ([4]http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html)
-
- o Evolution 2.0
-
-Installation-Related Notes
-
- This section outlines those issues that are related to Anaconda (the
- Fedora Core installation program) and installing Fedora Core 3 in general.
-
- Note
-
- If you intend to download the Fedora Core 3 DVD ISO image, keep in mind
- that not all file downloading tools can accommodate files larger than 2GB
- in size. For example, wget will exit with a File size limit exceeded
- error.
-
- The curl and ncftpget file downloading tools do not have this limitation,
- and can successfully download files larger than 2GB.
-
- Anaconda Notes
-
- o The Fedora Core installation program has the ability to test the
- integrity of the installation media. It works with the CD, DVD, hard
- drive ISO, and NFS ISO installation methods. Red Hat recommends that
- you test all installation media before starting the installation
- process, and before reporting any installation-related bugs (many of
- the bugs reported are actually due to improperly-burned CDs). To use
- this test, type linux mediacheck at the boot: prompt.
-
- o Memory testing may be performed prior to installing Fedora Core by
- entering memtest86 at the boot: prompt. This causes the Memtest86
- standalone memory testing software to run. Memtest86 memory testing
- continues until the Esc key is pressed.
-
- NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use
- this feature.
-
- o Fedora Core 3 supports graphical FTP and HTTP installations. However,
- due to the necessity of containing the installer image in RAM, only
- systems with more than 128MB of RAM (or systems booted from CD-ROM 1,
- which contains the installer image) can use the graphical installer.
- Systems with 128MB or less will continue to use the text-based
- installer.
-
- Installation-Related Issues
-
- o Certain hardware configurations (particularly those with LCD displays)
- may experience problems while starting the Fedora Core installation
- program. In these instances, restart the installation, and add the
- "nofb" option to the boot command line.
-
- NOTE: Chinese, Japanese, and Korean graphical installations started
- using the "nofb" option will start in English, and then switch to the
- appropriate language once the graphical phase of the installation
- process begins.
-
- o Some Sony VAIO(R) notebook systems may experience problems installing
- Fedora Core from CD-ROM. If this happens, restart the installation
- process and add the following option to the boot command line:
-
- pci=off ide1=0x180,0x386
-
- This option allows the installation to proceed normally; any devices
- not detected due to the use of this option will be configured the
- first time Fedora Core is booted.
-
- o Serial mice are known to be inoperative during installation. However,
- there are indications that serial mice work properly in X after the
- installation has completed. Refer to bug 119474 for more information:
-
- [5]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
-
- o There have been issues observed when upgrading Red Hat Linux 7.<x>,
- 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The issue is
- caused by version overlap between the official Red Hat Linux RPMs (or
- the ones from the Fedora Project) and the Ximian RPMs. This
- configuration is not supported. You have several choices in resolving
- this issue:
-
- 1) You may remove Ximian GNOME from your system prior to upgrading to
- Fedora Core.
-
- 2) You may upgrade your system, and then immediately reinstall Ximian
- GNOME.
-
- 3) You may upgrade your system, and then immediately remove all
- remaining Ximian RPMs, replacing them with the corresponding Fedora
- Core RPMs.
-
- You must resolve the version overlap using one of the above choices.
- Failure to do so will result in an unstable GNOME configuration.
-
-Package-Specific Notes
-
- The following sections contain information regarding packages that have
- undergone significant changes for Fedora Core 3. For easier access, they
- are organized using the same groups used in Anaconda.
-
- Base
-
- This section contains information related to basic system components.
-
- openssh
-
- Fedora Core 3 contains OpenSSH 3.9, which includes strict permission and
- ownership checks for the ~/.ssh/config file. These checks mean that ssh
- will exit if this file does not have appropriate ownership and
- permissions.
-
- Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and
- that its permissions are set to mode 600.
-
- Core
-
- This section contains the most elemental components of Fedora Core,
- including the kernel.
-
- e2fsprogs
-
- The ext2online utility has been added for online growing of existing ext3
- file systems.
-
- Note
-
- It is important to keep in mind that ext2online does not grow the
- underlying block device itself -- there must be sufficient unused space
- already present on the device. The easiest way to ensure this is to use
- LVM volumes and to run lvresize or lvextend to extend the device.
-
- In addition, file systems must be specially prepared in order to be
- resized past a certain point. The preparation involves reserving a small
- amount of space into which on-disk tables can grow. For newly-created file
- systems, mke2fs reserves such space automatically; the space reserved is
- sufficient to grow the file system by a factor of 1000. The creation of
- this reserved space can be disabled by the following command:
-
- mke2fs -O ^resize_inode
-
- Future releases of Fedora Core will allow the creation of this reserved
- space on existing file systems.
-
- glibc
-
- o The version of glibc provided with Fedora Core 3 performs additional
- internal sanity checks to prevent and detect data corruption as early
- as possible. By default, should corruption be detected, a message
- similar to the following will be displayed on standard error (or
- logged via syslog if stderr is not open):
-
- *** glibc detected *** double free or corruption: 0x0937d008 ***
-
- By default, the program that generated this error will also be killed;
- however, this (and whether or not an error message is generated) can
- be controlled via the MALLOC_CHECK_ environment variable. The
- following settings are supported:
-
- o 0 -- Do not generate an error message, and do not kill the
- program
-
- o 1 -- Generate an error message, but do not kill the program
-
- o 2 -- Do not generate an error message, but kill the program
-
- o 3 -- Generate an error message and kill the program
-
- Note
-
- If MALLOC_CHECK_ is explicitly set a value other than 0, this causes
- glibc to perform more tests that are more extensive than the default,
- and may impact performance.
-
- Should you have a program from a third party ISV that triggers these
- corruption checks and displays a message, you should file a defect
- report with the application's vendor, since this indicates a serious
- bug.
-
- hotplug
-
- The location where hotplug expects firmware to be loaded into (for
- example, firmware for Cardbus cards) has changed from
- /usr/lib/hotplug/firmware to /lib/firmware. Existing firmware files must
- be moved into the new directory.
-
- kernel
-
- o In the past, the process of updating the kernel did not change the
- default kernel in the system's boot loader configuration.
-
- Fedora Core 3 changes this behavior to set newly-installed kernels as
- the default. This behavior applies to all installation methods
- (including rpm -i).
-
- This behavior is controlled by two lines in the /etc/sysconfig/kernel
- file:
-
- o UPGRADEDEFAULT -- Controls whether new kernels will be booted by
- default (default value: yes)
-
- o DEFAULTKERNEL -- kernel RPMs whose names match this value will be
- booted by default (default value: depends on hardware
- configuration)
-
- o In order to eliminate the redundancy inherent in providing a separate
- package for the kernel source code when that source code already
- exists in the kernel's .src.rpm file, Fedora Core 3 no longer includes
- the kernel-source package. Users that require access to the kernel
- sources can find them in the kernel .src.rpm file. To create an
- exploded source tree from this file, perform the following steps (note
- that <version> refers to the version specification for your
- currently-running kernel):
-
- 1. Obtain the kernel-<version>.src.rpm file from one of the
- following sources:
-
- o The SRPMS directory on the appropriate "SRPMS" CD iso image
-
- o The FTP site where you got the kernel package
-
- o By running the following command:
-
- up2date --get-source kernel
-
- 2. Install kernel-<version>.src.rpm (given the default RPM
- configuration, the files this package contains will be written to
- /usr/src/redhat/)
-
- 3. Change directory to /usr/src/redhat/SPECS/, and issue the
- following command:
-
- rpmbuild -bp --target=<arch> kernel.spec
-
- (Where <arch> is the desired target architecture.)
-
- On a default RPM configuration, the kernel tree will be located
- in /usr/src/redhat/BUILD/.
-
- 4. In resulting tree, the configurations for the specific kernels
- shipped in Fedora Core 3 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 configuration file in the proper
- place for building:
-
- cp <desired-file> ./.config
-
- 5. Issue the following command:
-
- make oldconfig
-
- You can then proceed as usual.
-
- Note
-
- An exploded source tree is not required to build kernel modules
- against the currently in-use kernel.
-
- For example, to build the foo.ko module, create the following file
- (named Makefile) in the directory containing the foo.c file:
-
- obj-m := foo.o
-
- KDIR := /lib/modules/$(shell uname -r)/build
- PWD := $(shell pwd)
-
- default:
- $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
-
-
- Issue the make command to build the foo.ko module.
-
- Language Support
-
- This section includes information related to the support of various
- languages under Fedora Core.
-
- iiimf
-
- o The default Input Method (IM) for Chinese (Simplified and
- Traditional), Japanese, and Korean has been changed to IIIMF -- the
- Internet/Intranet Input Method Framework. IIIMF is supported as a
- native GTK2 IM module, and also through XIM using the httx client.
- IIIMF supports the use of multiple Language Engines (LEs) at the same
- time; using the GNOME Input Method Language Engine Tool (GIMLET -- an
- applet) it is possible to switch between LEs of different languages
- inside GTK2 applications.
-
- IIIMF currently defaults to using Ctrl-Space or Shift-Space for
- toggling the input method on and off (Emacs users can use Ctrl-@
- instead of Ctrl-Space to set the mark.)
-
- Depending on your selection at the language support screen during
- installation, one or more IIIMF language engines may be installed. The
- IIIMF server package (iiimf-server) will also be installed if a
- language engine has been selected. The language to language engine
- (LE) package mappings are as follows:
-
- o ja_JP -- iiimf-le-canna
-
- o zh_CN -- iiimf-le-chinput
-
- o zh_TW -- iiimf-le-xcin
-
- o ko_KR -- iiimf-le-hangul
-
- o {bn,gu,pa,ta,hi}_IN -- iiimf-le-unit
-
- Accordingly, input via IIIMF will be enabled if you have chosen one of
- the following as your default locale:
-
- o ja_JP
-
- o zh_CN
-
- o zh_TW
-
- o ko_KR
-
- o {bn,gu,pa,ta,hi}_IN
-
- To aid your use of IIIMF, if you have selected one of the above
- locales and you are using the GNOME Desktop, when you first login the
- GIMLET utility (part of the iiimf-gnome-im-switcher package) will
- automatically be added to your panel.
-
- GIMLET is a utility for switching between the different LEs that are
- installed on your system. Using a different language engine allows you
- to enter text in different languages. Alternatively you may add GIMLET
- manually to your panel by right clicking on the panel and selecting:
-
- Add to Panel -> GIMLET
-
- Should you wish to switch between IIIMF or the legacy input method
- framework XIM, you can use the system-switch-im application. After
- changing the input method framework your changes will be reflected
- when you next start the X Window System.
-
- Mail Server
-
- This section contains information related to the mail transport agents
- included with Fedora Core.
-
- mailman
-
- Earlier mailman RPMs installed all files under the /var/mailman/
- directory. Unfortunately, this did not conform to the Filesystem Hierarchy
- Standard (FHS) and also created security violations when SELinux was
- enabled.
-
- If you previously had mailman installed and had edited files in
- /var/mailman/ (such as mm_cfg.py) you must move those changes to their new
- location, as documented in the following file:
-
- /usr/share/doc/mailman-*/INSTALL.REDHAT
-
- sendmail
-
- o By default, the Sendmail mail transport agent (MTA) does not accept
- network connections from any host other than the local computer. If
- you want to configure Sendmail as a server for other clients, you must
- edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also
- listen on network devices (or comment out this option entirely using
- the dnl comment delimiter). You must then regenerate
- /etc/mail/sendmail.cf by running the following command (as root):
-
- make -C /etc/mail
-
- Note that you must have the sendmail-cf package installed for this to
- work.
-
- Server Configuration Tools
-
- This section contains information related to various server configuration
- tools.
-
- system-config-securitylevel
-
- The firewall constructed by the system-config-securitylevel configuration
- tool now allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the
- present time, these services cannot be disabled by
- system-config-securitylevel.
-
- Sound and Video
-
- This section contains information related to multimedia applications.
-
- k3b
-
- Past users of the CD/DVD burning application k3b may notice that the
- program k3bsetup is missing. This is because k3bsetup is not necessary
- under Fedora Core 3.
-
- Web Server
-
- This section contains information related to Web-related tools.
-
- crypto-utils
-
- The certwatch(1) tool has been added to the crypto-utils package. This
- tool is used to send warning mail to root when any configured SSL
- certificates have expired or are approaching the expiration date. By
- default, the tool checks any certificates that are enabled in the mod_ssl
- configuration.
-
- httpd
-
- By default, the httpd daemon is now started using the C locale, rather
- than using the configured system locale setting. This behavior can be
- changed by setting the HTTPD_LANG variable in the /etc/sysconfig/httpd
- file.
-
- php
-
- The gd, mbstring, and ncurses extensions have been moved to the php-gd,
- php-mbstring, and php-ncurses packages, respectively. Note that you will
- need to install these packages manually (if required) when upgrading from
- an earlier release.
-
- Windows File Server
-
- This section contains information related to Samba, software that makes it
- possible to share files between Linux and Windows systems.
-
- samba
-
- Browsing of Windows shares (also known as SMB browsing) fails on Fedora
- Core 3 systems that have the standard firewall configured. This is most
- easily noticed in the failure of Nautilus to display shares. The failure
- is due to the firewall disrupting the broadcast mode of SMB browsing,
- which is Samba's default setting. There are two workarounds:
-
- o Configure a WINS server on the network, and set the "wins server"
- option in smb.conf to the address of the WINS server.
-
- o Disable the firewall
-
- Warning
-
- Depending on your system and network configurations, disabling the
- firewall can greatly increase the chance of your system being attacked and
- compromised. Make sure you fully understand the risks before undertaking
- this step.
-
- For additional information, refer to the following bug report:
-
- [6]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
-
- X Window System
-
- This section contains information related to the X Window System
- implementation provided with Fedora Core.
-
- xorg-x11
-
- o Users new to the X.org X11 implementation should take note of a few
- differences between it and the XFree86.org X11 implementation which
- shipped in previous Red Hat operating systems. In particular, the
- names of some files have changed:
-
- X Server Binary:
-
- o XFree86 X11: XFree86
-
- o X.org X11: Xorg
-
- X Server Configuration File:
-
- o XFree86 X11: /etc/X11/XF86Config
-
- o X.org X11: /etc/X11/xorg.conf
-
- X Server Log File
-
- o XFree86 X11: /var/log/XFree86.$DISPLAY.log
-
- o X.org X11: /var/log/Xorg.$DISPLAY.log
-
- When configuring or troubleshooting your X server configuration, be
- sure that you are using the correct files.
-
- o There has been some confusion regarding font-related issues under the
- X Window System in recent versions of Fedora Core (and versions of Red
- Hat Linux before it.) At the present time, there are two font
- subsystems, each with different characteristics:
-
- - The original (15+ year old) subsystem is referred to as the "core X
- font subsystem". Fonts rendered by this subsystem are not
- anti-aliased, are handled by the X server, and have names like:
-
- -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
-
- The newer font subsystem is known as "fontconfig", and allows
- applications direct access to the font files. Fontconfig is often used
- along with the "Xft" library, which allows applications to render
- fontconfig fonts to the screen with antialiasing. Fontconfig uses more
- human-friendly names like:
-
- Luxi Sans-10
-
- Over time, fontconfig/Xft will replace the core X font subsystem. At
- the present time, applications using the Qt 3 or GTK 2 toolkits (which
- would include KDE and GNOME applications) use the fontconfig and Xft
- font subsystem; most everything else uses the core X fonts.
-
- In the future, Fedora Core may support only fontconfig/Xft in place of
- the XFS font server as the default local font access method.
-
- NOTE: An exception to the font subsystem usage outlined above is
- OpenOffice.org (which uses its own font rendering technology).
-
- If you wish to add new fonts to your Fedora Core 3 system, you must be
- aware that the steps necessary depend on which font subsystem is to
- use the new fonts. For the core X font subsystem, you must:
-
- 1. Create the /usr/share/fonts/local/ directory (if it doesn't already
- exist):
-
- mkdir /usr/share/fonts/local/
-
- 2. Copy the new font file into /usr/share/fonts/local/
-
- 3. Update the font information by issuing the following commands (note
- that, due to formatting restrictions, the following commands may
- appear on more than one line; in use, each command should be entered
- on a single line):
-
- ttmkfdir -d /usr/share/fonts/local/ -o
- /usr/share/fonts/local/fonts.scale
-
- mkfontdir /usr/share/fonts/local/
-
- 4. If you had to create /usr/share/fonts/local/, you must then add it
- to the X font server (xfs) path:
-
- chkfontpath --add /usr/share/fonts/local/
-
- Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into the
- /usr/share/fonts/ directory (individual users can modify their
- personal font configuration by copying the font file into the
- ~/.fonts/ directory).
-
- After the new font has been copied, use fc-cache to update the font
- information cache:
-
- fc-cache <directory>
-
- (Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
- directories.)
-
- Individual users may also install fonts graphically, by browsing
- fonts:/// in Nautilus, and dragging the new font files there.
-
- NOTE: If the font filename ends with ".gz", it has been compressed
- with gzip, and must be decompressed (with the gunzip command) before
- the fontconfig font subsystem can use the font.
-
- o Due to the transition to the new font system based on fontconfig/Xft,
- GTK+ 1.2 applications are not affected by any changes made via the
- Font Preferences dialog. For these applications, a font can be
- configured by adding the following lines to the file ~/.gtkrc.mine:
-
- style "user-font" {
-
- fontset = "<font-specification>"
-
- }
-
- widget_class "*" style "user-font"
-
- (Where <font-specification> represents a font specification in the
- style used by traditional X applications, such as
- "-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
-
- Miscellaneous Notes
-
- This section contains information related to packages that do not fit in
- any of the proceeding categories.
-
- compat-db
-
- C++ and TCL bindings are no longer contained in the compat-db package.
- Applications requiring these bindings must be ported to the
- currently-shipping DB library.
-
- nscd
-
- The nscd name service cache daemon may now maintain a persistent cache
- across restarts or system reboots. Each database (user, group, and host,
- respectively) can be made selected to be persistent by setting the
- appropriate line in /etc/nscd.conf to "yes". Entries are not removed from
- the cache until they are proven to be no longer of interest. All entries
- whose time-to-live expires but are otherwise interesting are automatically
- reloaded, which helps in situations where the directory and name services
- become temporarily unavailable.
-
- The nscd name service daemon is also able to communicate faster with
- client programs. This feature must be enabled explicitly by setting the
- "shared" entry for the appropriate database in /etc/nscd.conf to "yes".
-
- udev
-
- Fedora Core 3 has switched from a static /dev/ directory to one that is
- dynamically managed via udev. This allows device nodes to be created on
- demand as drivers are loaded.
-
- For more information on udev, refer to the udev(8) man page and the
- following link:
-
- [7]http://people.redhat.com/~harald/udev.html
-
- Additional rules for udev should be placed in a separate file in the
- /etc/udev/rules.d/ directory.
-
- Additional permission rules for udev should be placed in a separate file
- in the /etc/udev/permissions.d/ directory.
-
- Systems upgraded to Fedora Core 3 using Anaconda will automatically be
- reconfigured to use udev. However (although NOT recommended) it is
- possible to perform a "live" upgrade to udev using the following steps:
-
- 1. Ensure that you are running a 2.6 kernel
-
- 2. Ensure that /sys/ is mounted
-
- 3. Install the initscripts RPM supplied with Fedora Core 3
-
- 4. Install the new udev RPM supplied with Fedora Core 3
-
- 5. Execute /sbin/start_udev
-
- 6. Install the new mkinitrd RPM supplied with Fedora Core 3
-
- 7. Perform one of the following steps:
-
- . Install the new kernel RPM supplied with Fedora Core 3
-
- OR:
-
- . Re-run mkinitrd for your existing kernel(s)
-
- Warning
-
- Improperly performing these steps can result in a system configuration
- that will not boot properly.
-
-Packages Added/Removed/Deprecated
-
- This section contains lists of packages that fit into the following
- categories:
-
- o Packages that have been added to Fedora Core 3
-
- o Packages that have been removed from Fedora Core 3
-
- o Packages that have been deprecated, and may be removed from a future
- release of Fedora Core
-
- Note
-
- To reduce the length of the following lists,source packages, and not
- binary packages are listed.
-
- Packages Added
-
- The following packages have been added to Fedora Core 3:
-
- o *** Still being developed ***
-
- Packages Removed
-
- The following packages have been removed from Fedora Core 3:
-
- o *** Still being developed ***
-
- Packages Deprecated
-
- The following packages have been deprecated, and may be removed from a
- future release of Fedora Core:
-
- o ac-archive -- No longer part of Fedora Core profile
-
- o dbskkd-cdb -- Only used by deprecated package skkinput
-
- o devlabel -- udev is the recommended solution
-
- o FAM -- Gamin (which is API/ABI compatible with FAM) is the recommended
- solution
-
- o FreeWnn -- Only used by deprecated package kinput2-canna-wnn6
-
- o kinput2-canna-wnn6 -- IIIMF is the recommended input method
-
- o licq -- Equivalent functionality present in other applications (gaim,
- for example)
-
- o lilo -- GRUB is the recommended bootloader
-
- o miniChinput -- IIIMF is the recommended input method
-
- o nabi -- IIIMF is the recommended input method
-
- o ncpfs -- No longer part of Fedora Core profile
-
- o skkinput -- IIIMF is the recommended input method
-
- o Wnn6-SDK -- Only used by deprecated package kinput2-canna-wnn6
-
- o xcin -- IIIMF is the recommended input method
-
-An Overview of the Fedora Project
-
- The goal of the Fedora Project is to work with the Linux community to
- build a complete, general-purpose operating system exclusively from open
- source software. Development will be done in a public forum. The project
- will produce time-based releases of Fedora Core about 2-3 times a year,
- with a public release schedule. The Red Hat engineering team will continue
- to participate in building Fedora Core and will invite and encourage 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:
-
- [8]http://fedora.redhat.com/
-
- In addition to the website, the following mailing lists are available:
-
- o fedora-list at redhat.com -- For users of Fedora Core releases
-
- o fedora-test-list at redhat.com -- For testers of Fedora Core test
- releases
-
- o fedora-devel-list at redhat.com -- For developers, developers, developers
-
- o fedora-docs-list at redhat.com -- For participants of the docs project
-
- 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.)
-
- NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
- rhl-devel-list, or rhl-docs-list, your subscriptions have been retained.
-
- The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC
- is a real-time, text-based form of communication. With it, you can have
- conversations with multiple people in an open channel or chat with someone
- privately one-on-one.
-
- To talk with other Fedora Project participants via IRC, access freenode
- IRC network. Initially, you can use irc.freenode.net as the IRC server,
- although you may decide to select a server that is geographically closer
- to you. Refer to the freenode website ([9]http://www.freenode.net/) for
- more information. Fedora Project participants frequent the #fedora
- channel, while Fedora Project developers can often be found on the
- #fedora-devel channel. Some of the larger projects may have their own
- channels as well; this information can be found on the project pages.
-
- NOTE: Red Hat has no control over the Fedora IRC channels or their
- content.
-
- ( x86 )
-
-References
-
- Visible links
- 1. http://www.gnu.org/licenses/fdl.html
- 2. http://fedora.redhat.com/docs/selinux-faq/
- 3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
- 4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
- 5. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
- 6. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
- 7. http://people.redhat.com/~harald/udev.html
- 8. http://fedora.redhat.com/
- 9. http://www.freenode.net/
+11. http://www.freenode.net/
Index: RELEASE-NOTES-ppc-en
===================================================================
RCS file: /cvs/fedora/fedora-release/RELEASE-NOTES-ppc-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- RELEASE-NOTES-ppc-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ RELEASE-NOTES-ppc-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,935 +1,1009 @@
- Fedora Core 3.90 Release Notes
+== Fedora Core 4test2 Release Notes ==
- Copyright (c) 2004 Red Hat, Inc.
+Copyright (c) 2005 Red Hat, Inc.
- Permission is granted to copy, distribute, and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.2 or any
- later version published by the Free Software Foundation; with no Invariant
- Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the
- license is available at [1]http://www.gnu.org/licenses/fdl.html.
+Permission is granted to copy, distribute, and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is available at
+http://www.gnu.org/licenses/fdl.html.
+
+This document may be copied and distributed in any medium, either
+commercially or non-commercially, provided that the GNU Free
+Documentation License (FDL), the copyright notices, and the license
+notice saying the GNU FDL applies to the document are reproduced in
+all copies, and that you add no other conditions whatsoever to those
+of the GNU FDL.
+
+Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum
+RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
+RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based
+trademarks and logos are trademarks or registered trademarks of Red
+Hat, Inc. in the United States and other countries.
+
+The Fedora trademark is a trademark of Red Hat, Inc. in the United
+States and other countries.
+
+Linux is a registered trademark of Linus Torvalds.
+
+All other trademarks and copyrights referred to are the property of
+their respective owners.
+
+The GPG fingerprint of the "Fedora Project <fedora at redhat.com>" key
+is:
+
+CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
+
+---------------------------------------------------------------------------
+
+ 1. Fedora Core 4 test2 Release Notes
+ 2. Introduction
+ 3. Hardware Requirements
+ 1. CPU Requirements
+ 2. Hard Disk Space Requirements
+ 3. Memory Requirements
+ 4. Overview of This Release
+ 5. Installation-Related Notes
+ 6. Installation-Related Issues
+ 7. Package-Specific Notes
+ 1. Base
+ 2. Core
+ 3. Language Support
+ 4. Server Configuration Tools
+ 5. Sound and Video
+ 6. Web Server
+ 7. Windows File Server
+ 8. Macintosh File Server
+ 9. X Window System
+ 10. Miscellaneous Notes
+ 8. Packages Added, Moved From Core, Changed, or
+Deprecated/Nuked
+ 1. Packages Added
+ 2. Packages Moved Out Of Core
+ 9. An Overview of the Fedora Project
+ 10. References
+
+== Introduction ==
+
+The Fedora Project is an openly-developed project designed by Red Hat,
+open for general participation, led by a meritocracy, and following a
+set of project objectives. The results from this project include
+Fedora Core, a complete, general-purpose operating system built
+exclusively from open source software.
+
+NOTE: Fedora Core is not a supported product of Red Hat, Inc.
+
+For more information, refer to the Fedora Project overview later in
+this document.
+
+The following topics related to Fedora Core 4test2 are covered in this
+document:
+
+ * Introduction (this section)
+ * Hardware requirements
+ * Overview of this release
+ * Installation-related notes
+ * Package-specific notes
+ * Packages added/removed/deprecated
+ * An overview of the Fedora Project
+
+== Hardware Requirements ==
+
+The following information represents the minimum hardware requirements
+necessary to successfully install Fedora Core 4test2.
+
+Note
+
+The compatibility/availability of other hardware components (such as
+video and network cards) may be required for specific installation
+modes and/or post-installation usage.
+
+=== CPU Requirements ===
+
+This section lists the CPU specifications required by Fedora Core
+4test2.
+
+Note
+
+The following CPU specifications are stated in terms of Intel
+processors. Other processors (notably, offerings from AMD, Cyrix, and
+VIA) that are compatible with and equivalent to the following Intel
+processors may also be used with Fedora Core.
+
+ * Minimum: Pentium-class
+
+Fedora Core 4test2 is optimized for Pentium 4 CPUs, but also supports
+earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III,
+and including AMD and VIA variants). This approach has been taken
+because Pentium-class optimizations actually result in reduced
+performance for non-Pentium-class processors, and Pentium 4 scheduling
+is sufficiently different (while making up the bulk of today's
+processors) to warrant this change.
+
+ * Recommended for text-mode: 200 MHz Pentium-class or better
+
+ * Recommended for graphical: 400 MHz Pentium II or better
+
+=== Hard Disk Space Requirements ===
+
+This section lists the disk space required to install Fedora Core
+4test2.
+
+Note
+
+The disk space requirements listed below represent the disk space
+taken up by Fedora Core 4test2 after the installation is
+complete. However, additional disk space is required during the
+installation to support the installation environment. This additional
+disk space corresponds to the size of /Fedora/base/stage2.img (on
+CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed
+system.
+
+In practical terms, this means that as little as an additional 90MB
+can be required for a minimal installation, while as much as an
+additional 175MB can be required for an "everything" installation.
+
+Also, keep in mind that additional space will be required for any user
+data, and at least 5% free space should be maintained for proper
+system operation.
+
+ * Custom Installation (Minimal): 620MB
+ * Server: 1.1GB
+ * Personal Desktop: 2.3GB
+ * Workstation: 3.0GB
+ * Custom Installation (Everything): 6.9GB
+
+=== Memory Requirements ===
+
+This section lists the memory required to install Fedora Core 4test2.
+
+ * Minimum for text-mode: 64MB
+ * Minimum for graphical: 192MB
+ * Recommended for graphical: 256MB
+
+== Overview of This Release ==
+
+The following list highlights certain new features of Fedora Core
+4test2:
+
+ * GCC 4.0
+ * GNOME 2.10
+ * KDE 3.4
+ * Native Eclipse 3.1M5
+ * MySQL 4.1
+ * PHP 5.0
+
+ * SELinux -- New daemons have been added to the targeted policy For
+ more information, refer to the SELinux FAQ at
+ http://fedora.redhat.com/docs/selinux-faq/ .
+ * amanda
+ * apache
+ * chkpwd
+ * cups
+ * dhcpc
+ * dhcpd
+ * dictd
+ * dovecot
+ * fingerd
+ * ftpd
+ * howl
+ * i18n_input
+ * ifconfig
+ * init
+ * initrc
+ * inetd
+ * innd
+ * kerberos
+ * ktalkd
+ * ldconfig
+ * login
+ * lpd
+ * mailman
+ * modutil
+ * mta
+ * mysqld
+ * NetworkManager
+ * named
+ * nscd
+ * ntpd
+ * portmap
+ * postgresql
+ * privoxy
+ * radius
+ * radvd
+ * rlogind
+ * rpcd
+ * rshd
+ * rsync
+ * samba
+ * slapd
+ * snmpd
+ * squid
+ * stunnel
+ * syslogd
+ * telnetd
+ * tftpd
+ * winbind
+ * ypbind
+ * ypserv
+ * zebra
+
+== Installation-Related Notes ==
+
+This section outlines anything noteworthy that is related to Anaconda
+(the Fedora Core installation program) and installing Fedora Core
+4test2 in general.
+
+Note
+
+If you intend to download the Fedora Core 4test2 DVD ISO image, keep
+in mind that not all file downloading tools can accommodate files
+larger than 2GB in size. For example, wget will exit with a File size
+limit exceeded error.
+
+The curl and ncftpget file downloading tools do not have this
+limitation, and can successfully download files larger than 2GB.
+
+Bittorrent is another method for downloading large files.
+
+Anaconda Notes
+
+ * The Fedora Core installation program has the ability to test the
+integrity of the installation media. It works with the CD, DVD, hard
+drive ISO, and NFS ISO installation methods. Red Hat recommends that
+you test all installation media before starting the installation
+process, and before reporting any installation-related bugs (many of
+the bugs reported are actually due to improperly-burned CDs). To use
+this test, type linux mediacheck at the boot: prompt.
+
+ * Memory testing may be performed prior to installing Fedora Core by
+entering memtest86 at the boot: prompt. This causes the Memtest86
+standalone memory testing software to run. Memtest86 memory testing
+continues until the Esc key is pressed.
+
+NOTE: You must boot from CD-ROM 1 (or a rescue CD-ROM) in order to use
+this feature.
+
+ * Fedora Core 4test2 supports graphical FTP and HTTP
+installations. However, due to the necessity of containing the
+installer image in RAM, only systems with more than 128MB of RAM (or
+systems booted from CD-ROM 1, which contains the installer image) can
+use the graphical installer. Systems with 128MB or less will continue
+to use the text-based installer.
+
+== Installation-Related Issues ==
+
+ * Certain hardware configurations (particularly those with LCD
+displays) may experience problems while starting the Fedora Core
+installation program. In these instances, restart the installation,
+and add the "nofb" option to the boot command line.
+
+NOTE: Chinese, Japanese, and Korean graphical installations started
+using the "nofb" option will start in English, and then switch to the
+appropriate language once the graphical phase of the installation
+process begins.
+
+ * Some Sony VAIO(R) notebook systems may experience problems
+installing Fedora Core from CD-ROM. If this happens, restart the
+installation process and add the following option to the boot command
+line:
+
+pci=off ide1=0x180,0x386
+
+This option allows the installation to proceed normally; any devices
+not detected due to the use of this option will be configured the
+first time Fedora Core is booted.
+
+ * Serial mice are known to be inoperative during
+installation. However, there are indications that serial mice work
+properly in X after the installation has completed. Refer to bug
+119474 for more information:
+
+[6]http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
+
+ * There have been issues observed when upgrading Red Hat Linux
+7.<x>, 8.0, 9, and Fedora Core 1 systems running Ximian GNOME. The
+issue is caused by version overlap between the official Red Hat Linux
+RPMs (or the ones from the Fedora Project) and the Ximian RPMs. This
+configuration is not supported. You have several choices in resolving
+this issue:
+
+1) You may remove Ximian GNOME from your system prior to upgrading to
+Fedora Core.
+
+2) You may upgrade your system, and then immediately reinstall Ximian
+GNOME.
+
+3) You may upgrade your system, and then immediately remove all
+remaining Ximian RPMs, replacing them with the corresponding Fedora
+Core RPMs.
+
+You must resolve the version overlap using one of the above choices.
+Failure to do so will result in an unstable GNOME configuration.
+
+== Package-Specific Notes ==
+
+The following sections contain information regarding packages that
+have undergone significant changes for Fedora Core 4test2. For easier
+access, they are organized using the same groups used in Anaconda.
+
+=== Base ===
+
+This section contains information related to basic system components.
+
+slocate database
+
+The database needed by the locate utility is no longer created by
+default. Enable the database creation by setting DAILY_UPDATE to
+"yes" in /etc/updatedb.conf if you want to use locate.
+
+openssh
+
+The version of OpenSSH in Fedora Core 4test2 contains OpenSSH 3.9
+includes strict permission and ownership checks for the ~/.ssh/config
+file. These checks mean that ssh will exit if this file does not have
+appropriate ownership and permissions.
+
+Therefore, make sure that ~/.ssh/config is owned by the owner of ~/,
+and that its permissions are set to mode 600.
+
+In addition, OpenSSH is no longer configured to request X11 forwarding
+by default when connecting to servers. To enable X11 forwarding, the
+-X or -Y option must be specified, or the ForwardX11 option must be
+enabled in the ~/.ssh/config file.
+
+The behavior of ssh clients that are invoked with the -X flag has
+changed. In OpenSSH 3.8 and later, X11 forwarding is performed in a
+way that applications run as untrusted clients by default. Previously,
+X11 forwarding was performed so that applications always ran as
+trusted clients. Some applications may not function properly when run
+as untrusted clients. To forward X11 so that applications are run as
+trusted clients, invoke ssh with the -Y flag instead of the -X flag,
+or set ForwardX11Trusted in the ~/.ssh/config file.
+
+=== Core ===
+
+This section contains the most elemental components of Fedora Core,
+including the kernel.
+
+ * In order to eliminate the redundancy inherent in providing a
+separate package for the kernel source code when that source code
+already exists in the kernel's .src.rpm file, Fedora Core 4test2 no
+longer includes the kernel-source package. Users that require access
+to the kernel sources can find them in the kernel .src.rpm file. To
+create an exploded source tree from this file, perform the following
+steps (note that <version> refers to the version specification for
+your currently-running kernel):
+
+ 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:
+
+ up2date --get-source kernel
+
+ 2. Install kernel-<version>.src.rpm (given the default RPM
+configuration, the files this package contains will be written to
+/usr/src/redhat/)
+
+ 3. Change directory to /usr/src/redhat/SPECS/, and issue the
+following command:
+
+ rpmbuild -bp --target=<arch> kernel.spec
+
+ (Where <arch> is the desired target architecture.)
+
+ On a default RPM configuration, the kernel tree will be
+located in /usr/src/redhat/BUILD/.
+
+ 4. In resulting tree, the configurations for the specific
+kernels shipped in Fedora Core 4test2 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 configuration file in the proper place for
+building:
+
+ cp <desired-file> ./.config
+
+ 5. Issue the following command:
+
+ make oldconfig
+
+You can then proceed as usual.
+
+Note
+
+An exploded source tree is not required to build kernel modules
+against the currently in-use kernel.
+
+For example, to build the foo.ko module, create the following file
+(named Makefile) in the directory containing the foo.c file:
+
+obj-m := foo.o
+
+KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
+
+default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
+
+
+Issue the make command to build the foo.ko module.
+
+=== Language Support ===
+
+This section includes information related to the support of various
+languages under Fedora Core.
+
+=== Server Configuration Tools ===
+
+This section contains information related to various server
+configuration tools.
+
+=== Sound and Video ===
+
+This section contains information related to multimedia applications.
+
+
+=== Web Server ===
+
+This section contains information related to Web-related tools.
+
+php
+
+Version 5.0 of PHP is now included, which includes a number of changes
+to the language along with significant performance improvements.
+Please refer to the PHP documentation for more information on
+migrating from PHP 4.3 to PHP 5.0:
+
+http://www.php.net/manual/en/migration5.php
+
+The following extensions have been added:
+
+ * the "mysqli" extension, the newly MySQL interface designed
+ specifically for MySQL 4; included in the php-mysql
+ * the "soap" extension, which can be used to implement a SOAP server
+ or client
+
+=== Windows File Server ===
+
+This section contains information related to Samba, software that
+makes it possible to share files between Linux and Windows systems.
+
+samba
+
+Browsing of Windows shares (also known as SMB browsing) fails on
+Fedora Core 4test2 systems that have the standard firewall
+configured. This is most easily noticed in the failure of Nautilus to
+display shares. The failure is due to the firewall disrupting the
+broadcast mode of SMB browsing, which is Samba's default
+setting. There are two workarounds:
+
+ * Configure a WINS server on the network, and set the "wins server"
+option in smb.conf to the address of the WINS server.
+
+ * Disable the firewall
+
+Warning
+
+Depending on your system and network configurations, disabling the
+firewall can greatly increase the chance of your system being attacked
+and compromised. Make sure you fully understand the risks before
+undertaking this step.
+
+For additional information, refer to the following bug report:
+
+[8]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
+
+
+=== Macintosh File Server ===
+
+This section contains information related to netatalk, software that
+makes it possible to share files between Linux and Macintosh systems.
+
+netatalk
+
+The 2.x version of netatalk uses a different method to store resource
+forks, and may use a different file name encoding scheme. Upgrading to
+Fedora Core 4 may result in data loss. Please read the documentation
+of the netatalk 1.x to 2.x upgrade before upgrading to Fedora Core 4.
+
+The netatalk upgrade information is available directly from the
+netatalk site:
+
+http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html
+
+It is also included in the netatalk installation for Fedora Core 4,
+the files are at:
+
+/usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf - numbered page
+25, document page 33.
+
+or
+
+/usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html
+
+=== X Window System ===
+
+This section contains information related to the X Window System
+implementation provided with Fedora Core.
+
+xorg-x11
+
+ * Users new to the X.org X11 implementation should take note of a
+few differences between it and the XFree86.org X11 implementation
+which shipped in previous Red Hat operating systems. In particular,
+the names of some files have changed:
+
+X Server Binary:
+
+ * XFree86 X11: XFree86
+
+ * X.org X11: Xorg
+
+X Server Configuration File:
+
+ * XFree86 X11: /etc/X11/XF86Config
+
+ * X.org X11: /etc/X11/xorg.conf
+
+X Server Log File
+
+ * XFree86 X11: /var/log/XFree86.$DISPLAY.log
+
+ * X.org X11: /var/log/Xorg.$DISPLAY.log
+
+When configuring or troubleshooting your X server configuration, be
+sure that you are using the correct files.
+
+ * There has been some confusion regarding font-related issues under
+the X Window System in recent versions of Fedora Core (and versions of
+Red Hat Linux before it.) At the present time, there are two font
+subsystems, each with different characteristics:
+
+- The original (15+ year old) subsystem is referred to as the "core X
+font subsystem". Fonts rendered by this subsystem are not
+anti-aliased, are handled by the X server, and have names like:
+
+-misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
+
+The newer font subsystem is known as "fontconfig", and allows
+applications direct access to the font files. Fontconfig is often used
+along with the "Xft" library, which allows applications to render
+fontconfig fonts to the screen with antialiasing. Fontconfig uses more
+human-friendly names like:
+
+Luxi Sans-10
+
+ * Over time, fontconfig/Xft will replace the core X font
+subsystem. At the present time, applications using the Qt 3 or GTK 2
+toolkits (which would include KDE and GNOME applications) use the
+fontconfig and Xft font subsystem; almost everything else uses the
+core X fonts.
+
+In the future, Fedora Core may support only fontconfig/Xft in place of
+the XFS font server as the default local font access method.
+
+NOTE: An exception to the font subsystem usage outlined above is
+OpenOffice.org (which uses its own font rendering technology).
+
+If you wish to add new fonts to your Fedora Core 4test2 system, you
+must be aware that the steps necessary depend on which font subsystem
+is to use the new fonts. For the core X font subsystem, you must:
+
+1. Create the /usr/share/fonts/local/ directory (if it doesn't already
+exist):
+
+mkdir /usr/share/fonts/local/
+
+2. Copy the new font file into /usr/share/fonts/local/
+
+3. Update the font information by issuing the following commands (note
+that, due to formatting restrictions, the following commands may
+appear on more than one line; in use, each command should be entered
+on a single line):
+
+ttmkfdir -d /usr/share/fonts/local/ -o
+/usr/share/fonts/local/fonts.scale
+
+mkfontdir /usr/share/fonts/local/
+
+4. If you had to create /usr/share/fonts/local/, you must then add it
+to the X font server (xfs) path:
+
+chkfontpath --add /usr/share/fonts/local/
+
+Adding new fonts to the fontconfig font subsystem is more
+straightforward; the new font file only needs to be copied into the
+/usr/share/fonts/ directory (individual users can modify their
+personal font configuration by copying the font file into the
+~/.fonts/ directory).
+
+After the new font has been copied, use fc-cache to update the font
+information cache:
+
+fc-cache <directory>
+
+(Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
+directories.)
+
+Individual users may also install fonts graphically, by browsing
+fonts:/// in Nautilus, and dragging the new font files there.
+
+NOTE: If the font filename ends with ".gz", it has been compressed
+with gzip, and must be decompressed (with the gunzip command) before
+the fontconfig font subsystem can use the font.
+
+ * Due to the transition to the new font system based on
+fontconfig/Xft, GTK+ 1.2 applications are not affected by any changes
+made via the Font Preferences dialog. For these applications, a font
+can be configured by adding the following lines to the file
+~/.gtkrc.mine:
+
+style "user-font" {
+
+fontset = "<font-specification>"
+
+}
+
+widget_class " *" style "user-font"
+
+(Where <font-specification> represents a font specification in the
+style used by traditional X applications, such as
+"-adobe-helvetica-medium-r-normal-- *-120- *- *- *- *- *- *".)
+
+=== Miscellaneous Notes ===
+
+This section contains information related to packages that do not fit
+in any of the proceeding categories.
+
+
+== Packages Added, Moved From Core, Changed, or Deprecated/Nuked ==
+
+For an overview of orphaned packages, visit
+[:Extras/OrphanedPackages:this list].
+
+This section contains lists of packages that fit into the following
+categories:
+
+ * Packages that have been added to Fedora Core 4test2
+
+ * Packages that have been moved out of Fedora Core 4test2
+
+ * Packages that have a changed version since Fedora Core 3
+
+ * Packages that have been deprecated, and may be removed from a
+future
+ release of Fedora Core
+
+=== Packages Added ===
+
+The following packages have been added to Fedora Core 4test2:
+
+ * ant-1.6.2-3jpp_2fc
+ * antlr-2.7.4-2jpp_1fc
+ * aqbanking-1.0.4beta-2
+ * aqhbci-1.0.2beta-2
+ * avalon-framework-4.1.4-2jpp_5fc
+ * avalon-logkit-1.2-2jpp_4fc
+ * bcel-5.1-1jpp_4fc
+ * classpath-inetlib-1.0-1jpp_1fc
+ * classpathx-jaf-1.0-2jpp_3fc
+ * classpathx-mail-1.0-3jpp_1fc
+ * compat-gcc-296-2.96-132.fc4
+ * compat-gcc-32-3.2.3-47.fc4
+ * compat-readline43-4.3-2
+ * cpufreq-utils-0.2-1.1.12
+ * cpuspeed-1.2.1-1.19
+ * cryptix-3.2.0-4jpp_1fc
+ * cryptix-asn1-20011119-4jpp_1fc
+ * cryptsetup-luks-1.0-1
+ * dcraw-0.0.20050227-1
+ * device-mapper-multipath-0.4.4-0.pre8.0
+ * dmidecode-2.6-1.13
+ * eclipse-3.1.0_fc-0.M5.17
+ * eclipse-bugzilla-0.1.0_fc-9
+ * eclipse-cdt-3.0.0_fc-0.M5.3
+ * eclipse-changelog-2.0.1_fc-19
+ * eclipse-pydev-0.9.0_fc-4
+ * evince-0.1.9-1
+ * fonts-chinese-2.15-1
+ * fonts-indic-1.9-2
+ * fonts-japanese-0.20050222-2
+ * fonts-korean-1.0.11-2
+ * gjdoc-0.7.3-1
+ * gnome-doc-utils-0.1.3-1
+ * gnome-menus-2.10.1-1
+ * gnome-python2-extras-2.10.0-2.1
+ * gnu-crypto-2.0.1-1jpp_1fc
+ * gnu.getopt-1.0.9-4jpp_1fc
+ * gwenhywfar-1.7.2-2
+ * hardlink-1.0-1.11
+ * iiimf-12.1.1-11.svn2435
+ * ipv6calc-0.48-3
+ * irqbalance-1.12-1.18
+ * jakarta-commons-beanutils-1.7.0-1jpp_1fc
+ * jakarta-commons-collections-3.1-1jpp_1fc
+ * jakarta-commons-daemon-1.0-2jpp_1fc
+ * jakarta-commons-dbcp-1.2.1-3jpp_1fc
+ * jakarta-commons-digester-1.6-2jpp_1fc
+ * jakarta-commons-el-1.0-2jpp_1fc
+ * jakarta-commons-fileupload-1.0-3jpp_1fc
+ * jakarta-commons-lang-2.0-2jpp_1fc
+ * jakarta-commons-launcher-0.9-3jpp_1fc
+ * jakarta-commons-logging-1.0.4-2jpp_1fc
+ * jakarta-commons-modeler-1.1-3jpp_1fc
+ * jakarta-commons-pool-1.2-2jpp_1fc
+ * jakarta-commons-validator-1.1.3-1jpp_1fc
+ * jakarta-taglibs-standard-1.1.1-4jpp_1fc
+ * java_cup-0.10-0.k.1jpp_2fc
+ * jdepend-2.6-2jpp_3fc
+ * jessie-1.0.0-3
+ * jlex-1.2.6-1jpp_2fc
+ * jsch-0.1.17-2jpp_1fc
+ * junit-3.8.1-3jpp_4fc
+ * jzlib-1.0.5-2jpp_1fc
+ * kdeaccessibility-3.4.0-1
+ * ksh-20050202-1
+ * latex2html-2002.2.1-1
+ * ldapjdk-4.17-1jpp_2fc
+ * libdbi-drivers-0.7.1-2
+ * libgconf-java-2.10.0-1
+ * libglade-java-2.9.92-1
+ * libgnome-java-2.9.92-1
+ * libgtk-java-2.6.1.1-1
+ * linux-atm-2.5.0-0.20050118.2
+ * lksctp-tools-1.0.2-5
+ * log4j-1.2.8-7jpp_3fc
+ * longrun-0.9-1.8
+ * lvm2-cluster-2.00.29-1.22.FC4
+ * mcelog-0.4-1.8
+ * microcode_ctl-1.11-1.21
+ * mod_jk-1.2.6-3jpp_1fc
+ * mx4j-2.1.0-1jpp_2fc
+ * mysqlclient10-3.23.58-5
+ * openhpi-2.0.3-2
+ * OpenIPMI-1.4.11-5
+ * openssl097a-0.9.7a-2
+ * oro-2.0.8-1jpp_2fc
+ * poppler-0.1.2-1
+ * puretls-0.9-0.b4.1jpp_2fc
+ * python-docs-2.4-102
+ * python-elementtree-1.2.6-4
+ * python-numeric-23.7-2
+ * python-sqlite-1.1.6-1
+ * python-twisted-1.3.0-4
+ * python-urlgrabber-2.9.6-1
+ * readahead-1.0-1.7
+ * regexp-1.3-1jpp_4fc
+ * rng-utils-2.0-1.5
+ * salinfo-0.5-1.4
+ * servletapi5-5.0.18-1jpp_3fc
+ * slib-3a1-2
+ * smartmontools-5.33-1.5
+ * sqlite-3.1.2-2
+ * struts11-1.1-1jpp_2fc
+ * system-config-lvm-0.9.22-1.0
+ * texi2html-1.76-2
+ * tomcat5-5.0.30-1jpp_2fc
+ * x86info-1.13-1.9
+ * xalan-j2-2.6.0-2jpp_1fc
+ * xen-2-20050403
+ * xerces-j2-2.6.2-4jpp_1fc
+ * xml-commons-1.0-0.b2.6jpp_5fc
+ * xml-commons-resolver-1.1-1jpp_4fc
+
+=== Packages Moved Out Of Core ===
+
+This is a new section to the release notes. This is based on a
+treediff of dist-fc3 and dist-fc4 on 14-MAR-2005. The following
+packages have been moved out of core from Fedora Core 4test2:
+
+ * abiword-2.0.12-3
+ * aiksaurus-1.2.1-2
+ * ash-0.3.8-20
+ * asp2php-0.76.18-3
+ * aspell-ia-0.50-1
+ * aumix-2.8-9
+ * balsa-2.2.4-1.FC3.1
+ * bluez-bluefw-1.0-6
+ * bonobo-1.0.22-9
+ * bzflag-1.10.6-2
+ * cdecl-2.5-30
+ * cdlabelgen-3.0.0-1
+ * cdp-0.33-32
+ * compat-gcc-8-3.3.4.2
+ * compat-pwdb-0.62-9
+ * comsat-0.17-11
+ * cproto-4.7c-3
+ * cryptsetup-0.1-4
+ * cyrus-imapd-2.2.6-2.FC3.6
+ * dbh-1.0.18-5
+ * dbskkd-cdb-1.01-21
+ * ddskk-12.2.0-4
+ * dietlibc-0.27-4
+ * diskcheck-1.6-2
+ * dmalloc-5.3.0-3
+ * exim-4.43-1
+ * flim-1.14.7-1
+ * fonts-bengali-0.1-3
+ * fonts-ja-8.0-16
+ * freeciv-1.14.2-1
+ * FreeWnn-1.10pl020-5
+ * fsh-1.2-5
+ * ftpcopy-0.6.2-7
+ * gcc4-4.0.0-0.8
+ * ggv-2.8.0-1
+ * giftrans-1.12.2-20
+ * Glide3-20010520-33
+ * gnome-vfs-1.0.5-21
+ * gnome-vfs-extras-0.2.0-9
+ * gnuchess-5.07-4
+ * gnumeric-1.2.13-6
+ * gpdf-2.8.0-5
+ * grip-3.2.0-3
+ * gv-3.5.8-29
+ * im-sdk-12.1-4
+ * jed-0.99.16-6
+ * jisksp14-0.1-16
+ * jisksp16-1990-0.1-16
+ * kappa20-0.3-15
+ * kdetoys-3.3.0-1
+ * kernel-utils-2.4-13.1.39
+ * kinput2-v3.1-23
+ * knm_new-1.1-16
+ * koffice-1.3.3-1
+ * lapack-3.0-25
+ * lesstif-0.93.36-6
+ * libesmtp-1.0.3r1-2
+ * libgda-1.0.4-3
+ * libgnomedb-1.0.4-3
+ * libtool-libs13-1.3.5-10
+ * libxfce4mcs-4.0.6-1
+ * libxfce4util-4.0.6-1
+ * libxfcegui4-4.0.6-1
+ * lilo-21.4.4-26
+ * Maelstrom-3.0.6-6
+ * MagicPoint-1.11b-1
+ * memprof-0.5.1-5
+ * mew-3.3-4
+ * miniChinput-0.0.3-58
+ * nabi-0.14-3
+ * namazu-2.0.13-3
+ * nautilus-media-0.8.1-3
+ * ncftp-3.1.8-2
+ * nedit-5.4-3
+ * octave-2.1.57-7
+ * Omni-0.9.1-7
+ * openhbci-0.9.17-1
+ * openssl096b-0.9.6b-19
+ * ots-0.4.2-2
+ * pan-0.14.2-8
+ * pccts-1.33mr33-11
+ * pdksh-5.2.14-30
+ * qmkbootdisk-1.0.2-3
+ * Regina-2.3-1
+ * routed-0.17-18
+ * skkinput-2.06.4-7
+ * splint-3.1.1-4
+ * sylpheed-0.9.12-1
+ * system-logviewer-0.9.11-1
+ * system-switch-im-0.1.2-3
+ * THE-3.1-2
+ * tora-1.3.14.1-2
+ * ttfonts-indic-1.6-1
+ * ttfonts-ja-1.2-36
+ * ttfonts-ko-1.0.11-32.2
+ * ttfonts-zh_CN-2.14-10
+ * ttfonts-zh_TW-2.11-28
+ * ttfprint-0.9-13
+ * tuxracer-0.61-28
+ * w3m-el-1.4.3-2
+ * wl-2.10.1-4
+ * x3270-3.3.2.p1-6
+ * xboard-4.2.7-6
+ * xcin-2.5.3.pre3-24
+ * xemacs-21.4.15-9
+ * xemacs-sumo-20040818-2
+ * xfce4-iconbox-4.0.6-2
+ * xfce4-panel-4.0.6-1
+ * xfce4-systray-4.0.6-2
+ * xfce-mcs-manager-4.0.6-2
+ * xfce-mcs-plugins-4.0.6-2
+ * xfce-utils-4.0.6-1
+ * xfdesktop-4.0.6-2
+ * xffm-4.0.6-1
+ * xffm-icons-4.0.6-2
+ * xfprint-4.0.6-2
+ * xfwm4-4.0.6-1
+ * xfwm4-themes-4.0.6-2
+ * xloadimage-4.1-32
+ * xmms-1.2.10-9
+ * xosview-1.8.2-1
+ * xsnow-1.42-15
+ * ytalk-3.1.2-1
+
+== An Overview of the Fedora Project ==
+
+The goal of the Fedora Project is to work with the Linux community to
+build a complete, general purpose operating system exclusively from
+open source software. Development will be done in a public forum. The
+project will produce time-based releases of Fedora Core about 2-3
+times a year, with a public release schedule. The Red Hat engineering
+team will continue to participate in building Fedora Core and will
+invite and encourage 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:
+
+[10]http://fedora.redhat.com/
+
+In addition to the website, the following mailing lists are available:
+
+ * fedora-list at redhat.com -- For users of Fedora Core releases
+ * fedora-test-list at redhat.com -- For testers of Fedora Core test
+releases
+ * fedora-devel-list at redhat.com -- For developers, developers,
+developers
+ * fedora-docs-list at redhat.com -- For participants of the docs
+project
+
+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.)
+
+NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
+rhl-devel-list, or rhl-docs-list, your subscriptions have been
+retained.
+
+The Fedora Project also includes an IRC (Internet Relay Chat)
+channel. IRC is a real-time, text-based form of communication. With
+it, you can have conversations with multiple people in an open channel
+or chat with someone privately one-on-one.
+
+To talk with other Fedora Project participants via IRC, access
+freenode IRC network. Initially, you can use irc.freenode.net as the
+IRC server, although you may decide to select a server that is
+geographically closer to you. Refer to the freenode website
+([11]http://www.freenode.net/) for more information. Fedora Project
+participants frequent the #fedora channel, while Fedora Project
+developers can often be found on the #fedora-devel channel. Some of
+the larger projects may have their own channels as well; this
+information can be found on the project pages.
+
+NOTE: Red Hat has no control over the Fedora IRC channels or their
+content.
+
+( x86 )
+
+== References ==
+
+Visible links
+
+1. http://www.gnu.org/licenses/fdl.html
+
+2. http://fedora.redhat.com/docs/selinux-faq/
+
+3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
+
+4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
+
+5. http://platan.vc.cvut.cz/ftp/pub/vmware/
+
+6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
+
+7. http://i2o.shadowconnect.com/
- This document may be copied and distributed in any medium, either
- commercially or non-commercially, provided that the GNU Free Documentation
- License (FDL), the copyright notices, and the license notice saying the
- GNU FDL applies to the document are reproduced in all copies, and that you
- add no other conditions whatsoever to those of the GNU FDL.
+8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
- Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM,
- the RPM logo, Linux Library, PowerTools, Linux Undercover, RHmember,
- RHmember More, Rough Cuts, Rawhide and all Red Hat-based trademarks and
- logos are trademarks or registered trademarks of Red Hat, Inc. in the
- United States and other countries.
+9. http://people.redhat.com/~harald/udev.html
- The Fedora trademark is a trademark of Red Hat, Inc. in the United States
- and other countries.
+10. http://fedora.redhat.com/
- Linux is a registered trademark of Linus Torvalds.
-
- All other trademarks and copyrights referred to are the property of their
- respective owners.
-
- The GPG fingerprint of the "Fedora Project <fedora at redhat.com>" key is:
-
- CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
-
- ---------------------------------------------------------------------------
-
-Note: These release notes cover Fedora Core 3. Although additional
-changes have been introduced then, we don't yet have a good summary of
-those changes. We do plan to have that summary by FC4 final release.
-
- ---------------------------------------------------------------------------
-
-Introduction
-
- The Fedora Project is an openly-developed project designed by Red Hat,
- open for general participation, led by a meritocracy, and following a set
- of project objectives. The results from this project include Fedora Core,
- a complete, general-purpose operating system built exclusively from open
- source software.
-
- Note
-
- Fedora Core is not a supported product of Red Hat, Inc.
-
- For more information, refer to the Fedora Project overview later in this
- document.
-
- The following topics related to Fedora Core 3 are covered in this
- document:
-
- o Introduction (this section)
-
- o Hardware requirements
-
- o Overview of this release
-
- o Installation-related notes
-
- o Package-specific notes
-
- o Packages added/removed/deprecated
-
- o An overview of the Fedora Project
-
-Hardware Requirements
-
- The following information represents the minimum hardware requirements
- necessary to successfully install Fedora Core 3.
-
- Note
-
- The compatibility/availability of other hardware components (such as video
- and network cards) may be required for specific installation modes and/or
- post-installation usage.
-
- CPU Requirements
-
- This section lists the CPU specifications required by Fedora Core 3.
-
- o Minimum: PowerPC G3 / POWER4
-
- Fedora Core 3 supports only the 'NewWorld' generation of Power
- Macintosh, shipped from around 1999 onwards. It also supports the
- new 64-bit G5 processor, and POWER processors in IBM pSeries machines.
-
- o Recommended for text-mode: 233 MHz G3 or better
-
- o Recommended for graphical: 400 MHz G3 or better
-
- Hard Disk Space Requirements
-
- This section lists the disk space required to install Fedora Core 3.
-
- Note
-
- The disk space requirements listed below represent the disk space taken up
- by Fedora Core 3 after the installation is complete. However, additional
- disk space is required during the installation to support the installation
- environment. This additional disk space corresponds to the size of
- /Fedora/base/stage2.img (on CD-ROM 1) plus the size of the files in
- /var/lib/rpm on the installed system.
-
- In practical terms, this means that as little as an additional 90MB can be
- required for a minimal installation, while as much as an additional 175MB
- can be required for an "everything" installation.
-
- Also, keep in mind that additional space will be required for any user
- data, and at least 5% free space should be maintained for proper system
- operation.
-
- o Custom Installation (Minimal): 620MB
-
- o Server: 1.1GB
-
- o Personal Desktop: 2.3GB
-
- o Workstation: 3.0GB
-
- o Custom Installation (Everything): 6.9GB
-
- Memory Requirements
-
- This section lists the memory required to install Fedora Core 3.
-
- o Minimum for text-mode: 64MB
-
- o Minimum for graphical: 192MB
-
- o Recommended for graphical: 256MB
-
-Overview of This Release
-
- The following list includes brief summaries of some of the more
- significant aspects of Fedora Core 3:
-
- o Fedora Core 3 contains the following changes:
-
- o GCC 3.4
-
- o GNOME 2.8
-
- o KDE 3.3
-
- o SELinux -- This includes a new "targeted" policy that monitors
- specific daemons with less intrusion than the strict policy in
- use before. This policy is enabled by default. For more
- information, refer to:
-
- [2]http://fedora.redhat.com/docs/selinux-faq/
-
- o Indic language support
-
- o Kernel and e2fsprogs support for online growing of ext3 file
- systems
-
- o Various desktop-related features, including, but not limited to:
-
- o Remote desktops using VNC
- ([3]http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html)
-
- o Printing improvements
- ([4]http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html)
-
- o Evolution 2.0
-
-Installation-Related Notes
-
- This section outlines those issues that are related to Anaconda (the
- Fedora Core installation program) and installing Fedora Core 3 in general.
-
- Note
-
- If you intend to download the Fedora Core 3 DVD ISO image, keep in mind
- that not all file downloading tools can accommodate files larger than 2GB
- in size. For example, wget will exit with a File size limit exceeded
- error.
-
- The curl and ncftpget file downloading tools do not have this limitation,
- and can successfully download files larger than 2GB.
-
- Anaconda Notes
-
- o The Fedora Core installation program has the ability to test the
- integrity of the installation media. It works with the CD, DVD, hard
- drive ISO, and NFS ISO installation methods. Red Hat recommends that
- you test all installation media before starting the installation
- process, and before reporting any installation-related bugs (many of
- the bugs reported are actually due to improperly-burned CDs). To use
- this test, type linux mediacheck at the boot: prompt.
-
- o Fedora Core 3 supports graphical FTP and HTTP installations. However,
- due to the necessity of containing the installer image in RAM, only
- systems with more than 128MB of RAM (or systems booted from CD-ROM 1,
- which contains the installer image) can use the graphical installer.
- Systems with 128MB or less will continue to use the text-based
- installer.
-
- Installation-Related Issues
-
- o The first CD of the installation set is not bootable. A bootable CD
- image can be found in the images/ directory of the installation image
- or the first CD. Choose the appropriate boot.iso according to the
- hardware:
-
- o images/mac/boot.iso - 32-bit Apple Macintosh (G3/G4)
- o images/mac64/boot.iso - 64-bit Apple Macintoch (G5)
- o images/pseries/boot.iso - 64-bit IBM pSeries (POWER4/POWER5)
-
- o To perform a CD-based installation, you will need to eject the boot
- CD in order to insert CD 1. Anaconda does not currently enable this
- so if you have a machine where you cannot manually eject the CD, for
- example a Mac Mini, you may need to do a network installation. This
- bug should be fixed before the final release of Fedora Core 4. To
- monitor progress, see https://bugzilla.redhat.com/147272
-
- o Certain hardware configurations (particularly those with LCD displays)
- may experience problems while starting the Fedora Core installation
- program. If the screen is unreadable or the system crashes when the
- graphical phase of the installation process begins, restart the
- installation, and add the "text" option to the boot command line.
-
- You may then need to boot Fedora Core into text mode by entering
- 'linux 3' at the yaboot prompt, and configure the X server manually.
- It is expected that this hardware detection bug will be fixed
- before the final release of Fedora Core 4. The status can be
- monitored at https://bugzilla.redhat.com/149188 which also contains
- a link to an 'Xautoconfig' tool.
-
- o Power management support, including sleep and backlight level management,
- is present in the 'apmud' package, which is in Fedora Extras. After
- installation, you may wish to configure yum to use the Fedora Extras
- repository, and then run the command 'yum install apmud'. Fedora Extras
- can be added to your yum configuration by creating a file
- /etc/yum.repos.d/fedora-extras.repo containing the following:
-
- [extras-ppc]
- name=Fedora Extras PPC Tree
- baseurl=ftp://ftp.uk.linux.org/pub/people/dwmw2/fc3-extras-ppc/
-
- [extras-noarch]
- name=Fedora Extras noarch packages
- baseurl=http://download.fedora.redhat.com/pub/fedora/linux/extras/3/i386/
-
-Package-Specific Notes
-
- The following sections contain information regarding packages that have
- undergone significant changes for Fedora Core 3. For easier access, they
- are organized using the same groups used in Anaconda.
-
- Base
-
- This section contains information related to basic system components.
-
- openssh
-
- Fedora Core 3 contains OpenSSH 3.9, which includes strict permission and
- ownership checks for the ~/.ssh/config file. These checks mean that ssh
- will exit if this file does not have appropriate ownership and
- permissions.
-
- Therefore, make sure that ~/.ssh/config is owned by the owner of ~/, and
- that its permissions are set to mode 600.
-
- Core
-
- This section contains the most elemental components of Fedora Core,
- including the kernel.
-
- e2fsprogs
-
- The ext2online utility has been added for online growing of existing ext3
- file systems.
-
- Note
-
- It is important to keep in mind that ext2online does not grow the
- underlying block device itself -- there must be sufficient unused space
- already present on the device. The easiest way to ensure this is to use
- LVM volumes and to run lvresize or lvextend to extend the device.
-
- In addition, file systems must be specially prepared in order to be
- resized past a certain point. The preparation involves reserving a small
- amount of space into which on-disk tables can grow. For newly-created file
- systems, mke2fs reserves such space automatically; the space reserved is
- sufficient to grow the file system by a factor of 1000. The creation of
- this reserved space can be disabled by the following command:
-
- mke2fs -O ^resize_inode
-
- Future releases of Fedora Core will allow the creation of this reserved
- space on existing file systems.
-
- glibc
-
- o The version of glibc provided with Fedora Core 3 performs additional
- internal sanity checks to prevent and detect data corruption as early
- as possible. By default, should corruption be detected, a message
- similar to the following will be displayed on standard error (or
- logged via syslog if stderr is not open):
-
- *** glibc detected *** double free or corruption: 0x0937d008 ***
-
- By default, the program that generated this error will also be killed;
- however, this (and whether or not an error message is generated) can
- be controlled via the MALLOC_CHECK_ environment variable. The
- following settings are supported:
-
- o 0 -- Do not generate an error message, and do not kill the
- program
-
- o 1 -- Generate an error message, but do not kill the program
-
- o 2 -- Do not generate an error message, but kill the program
-
- o 3 -- Generate an error message and kill the program
-
- Note
-
- If MALLOC_CHECK_ is explicitly set a value other than 0, this causes
- glibc to perform more tests that are more extensive than the default,
- and may impact performance.
-
- Should you have a program from a third party ISV that triggers these
- corruption checks and displays a message, you should file a defect
- report with the application's vendor, since this indicates a serious
- bug.
-
- hotplug
-
- The location where hotplug expects firmware to be loaded into (for
- example, firmware for Cardbus cards) has changed from
- /usr/lib/hotplug/firmware to /lib/firmware. Existing firmware files must
- be moved into the new directory.
-
- kernel
-
- o In the past, the process of updating the kernel did not change the
- default kernel in the system's boot loader configuration.
-
- Fedora Core 3 changes this behavior to set newly-installed kernels as
- the default. This behavior applies to all installation methods
- (including rpm -i).
-
- This behavior is controlled by two lines in the /etc/sysconfig/kernel
- file:
-
- o UPGRADEDEFAULT -- Controls whether new kernels will be booted by
- default (default value: yes)
-
- o DEFAULTKERNEL -- kernel RPMs whose names match this value will be
- booted by default (default value: depends on hardware
- configuration)
-
- o In order to eliminate the redundancy inherent in providing a separate
- package for the kernel source code when that source code already
- exists in the kernel's .src.rpm file, Fedora Core 3 no longer includes
- the kernel-source package. Users that require access to the kernel
- sources can find them in the kernel .src.rpm file. To create an
- exploded source tree from this file, perform the following steps (note
- that <version> refers to the version specification for your
- currently-running kernel):
-
- 1. Obtain the kernel-<version>.src.rpm file from one of the
- following sources:
-
- o The SRPMS directory on the appropriate "SRPMS" CD iso image
-
- o The FTP site where you got the kernel package
-
- o By running the following command:
-
- up2date --get-source kernel
-
- 2. Install kernel-<version>.src.rpm (given the default RPM
- configuration, the files this package contains will be written to
- /usr/src/redhat/)
-
- 3. Change directory to /usr/src/redhat/SPECS/, and issue the
- following command:
-
- rpmbuild -bp --target=<arch> kernel.spec
-
- (Where <arch> is the desired target architecture.)
-
- On a default RPM configuration, the kernel tree will be located
- in /usr/src/redhat/BUILD/.
-
- 4. In resulting tree, the configurations for the specific kernels
- shipped in Fedora Core 3 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 configuration file in the proper
- place for building:
-
- cp <desired-file> ./.config
-
- 5. Issue the following command:
-
- make oldconfig
-
- You can then proceed as usual.
-
- Note
-
- An exploded source tree is not required to build kernel modules
- against the currently in-use kernel.
-
- For example, to build the foo.ko module, create the following file
- (named Makefile) in the directory containing the foo.c file:
-
- obj-m := foo.o
-
- KDIR := /lib/modules/$(shell uname -r)/build
- PWD := $(shell pwd)
-
- default:
- $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
-
-
- Issue the make command to build the foo.ko module.
-
- Language Support
-
- This section includes information related to the support of various
- languages under Fedora Core.
-
- iiimf
-
- o The default Input Method (IM) for Chinese (Simplified and
- Traditional), Japanese, and Korean has been changed to IIIMF -- the
- Internet/Intranet Input Method Framework. IIIMF is supported as a
- native GTK2 IM module, and also through XIM using the httx client.
- IIIMF supports the use of multiple Language Engines (LEs) at the same
- time; using the GNOME Input Method Language Engine Tool (GIMLET -- an
- applet) it is possible to switch between LEs of different languages
- inside GTK2 applications.
-
- IIIMF currently defaults to using Ctrl-Space or Shift-Space for
- toggling the input method on and off (Emacs users can use Ctrl-@
- instead of Ctrl-Space to set the mark.)
-
- Depending on your selection at the language support screen during
- installation, one or more IIIMF language engines may be installed. The
- IIIMF server package (iiimf-server) will also be installed if a
- language engine has been selected. The language to language engine
- (LE) package mappings are as follows:
-
- o ja_JP -- iiimf-le-canna
-
- o zh_CN -- iiimf-le-chinput
-
- o zh_TW -- iiimf-le-xcin
-
- o ko_KR -- iiimf-le-hangul
-
- o {bn,gu,pa,ta,hi}_IN -- iiimf-le-unit
-
- Accordingly, input via IIIMF will be enabled if you have chosen one of
- the following as your default locale:
-
- o ja_JP
-
- o zh_CN
-
- o zh_TW
-
- o ko_KR
-
- o {bn,gu,pa,ta,hi}_IN
-
- To aid your use of IIIMF, if you have selected one of the above
- locales and you are using the GNOME Desktop, when you first login the
- GIMLET utility (part of the iiimf-gnome-im-switcher package) will
- automatically be added to your panel.
-
- GIMLET is a utility for switching between the different LEs that are
- installed on your system. Using a different language engine allows you
- to enter text in different languages. Alternatively you may add GIMLET
- manually to your panel by right clicking on the panel and selecting:
-
- Add to Panel -> GIMLET
-
- Should you wish to switch between IIIMF or the legacy input method
- framework XIM, you can use the system-switch-im application. After
- changing the input method framework your changes will be reflected
- when you next start the X Window System.
-
- Mail Server
-
- This section contains information related to the mail transport agents
- included with Fedora Core.
-
- mailman
-
- Earlier mailman RPMs installed all files under the /var/mailman/
- directory. Unfortunately, this did not conform to the Filesystem Hierarchy
- Standard (FHS) and also created security violations when SELinux was
- enabled.
-
- If you previously had mailman installed and had edited files in
- /var/mailman/ (such as mm_cfg.py) you must move those changes to their new
- location, as documented in the following file:
-
- /usr/share/doc/mailman-*/INSTALL.REDHAT
-
- sendmail
-
- o By default, the Sendmail mail transport agent (MTA) does not accept
- network connections from any host other than the local computer. If
- you want to configure Sendmail as a server for other clients, you must
- edit /etc/mail/sendmail.mc and change the DAEMON_OPTIONS line to also
- listen on network devices (or comment out this option entirely using
- the dnl comment delimiter). You must then regenerate
- /etc/mail/sendmail.cf by running the following command (as root):
-
- make -C /etc/mail
-
- Note that you must have the sendmail-cf package installed for this to
- work.
-
- Server Configuration Tools
-
- This section contains information related to various server configuration
- tools.
-
- system-config-securitylevel
-
- The firewall constructed by the system-config-securitylevel configuration
- tool now allows CUPS and Multicast DNS (mDNS) browsing. Note that, at the
- present time, these services cannot be disabled by
- system-config-securitylevel.
-
- Sound and Video
-
- This section contains information related to multimedia applications.
-
- k3b
-
- Past users of the CD/DVD burning application k3b may notice that the
- program k3bsetup is missing. This is because k3bsetup is not necessary
- under Fedora Core 3.
-
- Web Server
-
- This section contains information related to Web-related tools.
-
- crypto-utils
-
- The certwatch(1) tool has been added to the crypto-utils package. This
- tool is used to send warning mail to root when any configured SSL
- certificates have expired or are approaching the expiration date. By
- default, the tool checks any certificates that are enabled in the mod_ssl
- configuration.
-
- httpd
-
- By default, the httpd daemon is now started using the C locale, rather
- than using the configured system locale setting. This behavior can be
- changed by setting the HTTPD_LANG variable in the /etc/sysconfig/httpd
- file.
-
- php
-
- The gd, mbstring, and ncurses extensions have been moved to the php-gd,
- php-mbstring, and php-ncurses packages, respectively. Note that you will
- need to install these packages manually (if required) when upgrading from
- an earlier release.
-
- Windows File Server
-
- This section contains information related to Samba, software that makes it
- possible to share files between Linux and Windows systems.
-
- samba
-
- Browsing of Windows shares (also known as SMB browsing) fails on Fedora
- Core 3 systems that have the standard firewall configured. This is most
- easily noticed in the failure of Nautilus to display shares. The failure
- is due to the firewall disrupting the broadcast mode of SMB browsing,
- which is Samba's default setting. There are two workarounds:
-
- o Configure a WINS server on the network, and set the "wins server"
- option in smb.conf to the address of the WINS server.
-
- o Disable the firewall
-
- Warning
-
- Depending on your system and network configurations, disabling the
- firewall can greatly increase the chance of your system being attacked and
- compromised. Make sure you fully understand the risks before undertaking
- this step.
-
- For additional information, refer to the following bug report:
-
- [6]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
-
- X Window System
-
- This section contains information related to the X Window System
- implementation provided with Fedora Core.
-
- xorg-x11
-
- o Users new to the X.org X11 implementation should take note of a few
- differences between it and the XFree86.org X11 implementation which
- shipped in previous Red Hat operating systems. In particular, the
- names of some files have changed:
-
- X Server Binary:
-
- o XFree86 X11: XFree86
-
- o X.org X11: Xorg
-
- X Server Configuration File:
-
- o XFree86 X11: /etc/X11/XF86Config
-
- o X.org X11: /etc/X11/xorg.conf
-
- X Server Log File
-
- o XFree86 X11: /var/log/XFree86.$DISPLAY.log
-
- o X.org X11: /var/log/Xorg.$DISPLAY.log
-
- When configuring or troubleshooting your X server configuration, be
- sure that you are using the correct files.
-
- o There has been some confusion regarding font-related issues under the
- X Window System in recent versions of Fedora Core (and versions of Red
- Hat Linux before it.) At the present time, there are two font
- subsystems, each with different characteristics:
-
- - The original (15+ year old) subsystem is referred to as the "core X
- font subsystem". Fonts rendered by this subsystem are not
- anti-aliased, are handled by the X server, and have names like:
-
- -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1
-
- The newer font subsystem is known as "fontconfig", and allows
- applications direct access to the font files. Fontconfig is often used
- along with the "Xft" library, which allows applications to render
- fontconfig fonts to the screen with antialiasing. Fontconfig uses more
- human-friendly names like:
-
- Luxi Sans-10
-
- Over time, fontconfig/Xft will replace the core X font subsystem. At
- the present time, applications using the Qt 3 or GTK 2 toolkits (which
- would include KDE and GNOME applications) use the fontconfig and Xft
- font subsystem; most everything else uses the core X fonts.
-
- In the future, Fedora Core may support only fontconfig/Xft in place of
- the XFS font server as the default local font access method.
-
- NOTE: An exception to the font subsystem usage outlined above is
- OpenOffice.org (which uses its own font rendering technology).
-
- If you wish to add new fonts to your Fedora Core 3 system, you must be
- aware that the steps necessary depend on which font subsystem is to
- use the new fonts. For the core X font subsystem, you must:
-
- 1. Create the /usr/share/fonts/local/ directory (if it doesn't already
- exist):
-
- mkdir /usr/share/fonts/local/
-
- 2. Copy the new font file into /usr/share/fonts/local/
-
- 3. Update the font information by issuing the following commands (note
- that, due to formatting restrictions, the following commands may
- appear on more than one line; in use, each command should be entered
- on a single line):
-
- ttmkfdir -d /usr/share/fonts/local/ -o
- /usr/share/fonts/local/fonts.scale
-
- mkfontdir /usr/share/fonts/local/
-
- 4. If you had to create /usr/share/fonts/local/, you must then add it
- to the X font server (xfs) path:
-
- chkfontpath --add /usr/share/fonts/local/
-
- Adding new fonts to the fontconfig font subsystem is more
- straightforward; the new font file only needs to be copied into the
- /usr/share/fonts/ directory (individual users can modify their
- personal font configuration by copying the font file into the
- ~/.fonts/ directory).
-
- After the new font has been copied, use fc-cache to update the font
- information cache:
-
- fc-cache <directory>
-
- (Where <directory> would be either the /usr/share/fonts/ or ~/.fonts/
- directories.)
-
- Individual users may also install fonts graphically, by browsing
- fonts:/// in Nautilus, and dragging the new font files there.
-
- NOTE: If the font filename ends with ".gz", it has been compressed
- with gzip, and must be decompressed (with the gunzip command) before
- the fontconfig font subsystem can use the font.
-
- o Due to the transition to the new font system based on fontconfig/Xft,
- GTK+ 1.2 applications are not affected by any changes made via the
- Font Preferences dialog. For these applications, a font can be
- configured by adding the following lines to the file ~/.gtkrc.mine:
-
- style "user-font" {
-
- fontset = "<font-specification>"
-
- }
-
- widget_class "*" style "user-font"
-
- (Where <font-specification> represents a font specification in the
- style used by traditional X applications, such as
- "-adobe-helvetica-medium-r-normal--*-120-*-*-*-*-*-*".)
-
- Miscellaneous Notes
-
- This section contains information related to packages that do not fit in
- any of the proceeding categories.
-
- compat-db
-
- C++ and TCL bindings are no longer contained in the compat-db package.
- Applications requiring these bindings must be ported to the
- currently-shipping DB library.
-
- nscd
-
- The nscd name service cache daemon may now maintain a persistent cache
- across restarts or system reboots. Each database (user, group, and host,
- respectively) can be made selected to be persistent by setting the
- appropriate line in /etc/nscd.conf to "yes". Entries are not removed from
- the cache until they are proven to be no longer of interest. All entries
- whose time-to-live expires but are otherwise interesting are automatically
- reloaded, which helps in situations where the directory and name services
- become temporarily unavailable.
-
- The nscd name service daemon is also able to communicate faster with
- client programs. This feature must be enabled explicitly by setting the
- "shared" entry for the appropriate database in /etc/nscd.conf to "yes".
-
- udev
-
- Fedora Core 3 has switched from a static /dev/ directory to one that is
- dynamically managed via udev. This allows device nodes to be created on
- demand as drivers are loaded.
-
- For more information on udev, refer to the udev(8) man page and the
- following link:
-
- [7]http://people.redhat.com/~harald/udev.html
-
- Additional rules for udev should be placed in a separate file in the
- /etc/udev/rules.d/ directory.
-
- Additional permission rules for udev should be placed in a separate file
- in the /etc/udev/permissions.d/ directory.
-
- Systems upgraded to Fedora Core 3 using Anaconda will automatically be
- reconfigured to use udev. However (although NOT recommended) it is
- possible to perform a "live" upgrade to udev using the following steps:
-
- 1. Ensure that you are running a 2.6 kernel
-
- 2. Ensure that /sys/ is mounted
-
- 3. Install the initscripts RPM supplied with Fedora Core 3
-
- 4. Install the new udev RPM supplied with Fedora Core 3
-
- 5. Execute /sbin/start_udev
-
- 6. Install the new mkinitrd RPM supplied with Fedora Core 3
-
- 7. Perform one of the following steps:
-
- . Install the new kernel RPM supplied with Fedora Core 3
-
- OR:
-
- . Re-run mkinitrd for your existing kernel(s)
-
- Warning
-
- Improperly performing these steps can result in a system configuration
- that will not boot properly.
-
-Packages Added/Removed/Deprecated
-
- This section contains lists of packages that fit into the following
- categories:
-
- o Packages that have been added to Fedora Core 3
-
- o Packages that have been removed from Fedora Core 3
-
- o Packages that have been deprecated, and may be removed from a future
- release of Fedora Core
-
- Note
-
- To reduce the length of the following lists,source packages, and not
- binary packages are listed.
-
- Packages Added
-
- The following packages have been added to Fedora Core 3:
-
- o *** Still being developed ***
-
- Packages Removed
-
- The following packages have been removed from Fedora Core 3:
-
- o *** Still being developed ***
-
- Packages Deprecated
-
- The following packages have been deprecated, and may be removed from a
- future release of Fedora Core:
-
- o ac-archive -- No longer part of Fedora Core profile
-
- o dbskkd-cdb -- Only used by deprecated package skkinput
-
- o devlabel -- udev is the recommended solution
-
- o FAM -- Gamin (which is API/ABI compatible with FAM) is the recommended
- solution
-
- o FreeWnn -- Only used by deprecated package kinput2-canna-wnn6
-
- o kinput2-canna-wnn6 -- IIIMF is the recommended input method
-
- o licq -- Equivalent functionality present in other applications (gaim,
- for example)
-
- o lilo -- GRUB is the recommended bootloader
-
- o miniChinput -- IIIMF is the recommended input method
-
- o nabi -- IIIMF is the recommended input method
-
- o ncpfs -- No longer part of Fedora Core profile
-
- o skkinput -- IIIMF is the recommended input method
-
- o Wnn6-SDK -- Only used by deprecated package kinput2-canna-wnn6
-
- o xcin -- IIIMF is the recommended input method
-
-An Overview of the Fedora Project
-
- The goal of the Fedora Project is to work with the Linux community to
- build a complete, general-purpose operating system exclusively from open
- source software. Development will be done in a public forum. The project
- will produce time-based releases of Fedora Core about 2-3 times a year,
- with a public release schedule. The Red Hat engineering team will continue
- to participate in building Fedora Core and will invite and encourage 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:
-
- [8]http://fedora.redhat.com/
-
- In addition to the website, the following mailing lists are available:
-
- o fedora-list at redhat.com -- For users of Fedora Core releases
-
- o fedora-test-list at redhat.com -- For testers of Fedora Core test
- releases
-
- o fedora-devel-list at redhat.com -- For developers, developers, developers
-
- o fedora-docs-list at redhat.com -- For participants of the docs project
-
- 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.)
-
- NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
- rhl-devel-list, or rhl-docs-list, your subscriptions have been retained.
-
- The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC
- is a real-time, text-based form of communication. With it, you can have
- conversations with multiple people in an open channel or chat with someone
- privately one-on-one.
-
- To talk with other Fedora Project participants via IRC, access freenode
- IRC network. Initially, you can use irc.freenode.net as the IRC server,
- although you may decide to select a server that is geographically closer
- to you. Refer to the freenode website ([9]http://www.freenode.net/) for
- more information. Fedora Project participants frequent the #fedora
- channel, while Fedora Project developers can often be found on the
- #fedora-devel channel. Some of the larger projects may have their own
- channels as well; this information can be found on the project pages.
-
- NOTE: Red Hat has no control over the Fedora IRC channels or their
- content.
-
- ( x86 )
-
-References
-
- Visible links
- 1. http://www.gnu.org/licenses/fdl.html
- 2. http://fedora.redhat.com/docs/selinux-faq/
- 3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
- 4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
- 5. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
- 6. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
- 7. http://people.redhat.com/~harald/udev.html
- 8. http://fedora.redhat.com/
- 9. http://www.freenode.net/
+11. http://www.freenode.net/
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.1.1.1 -r 1.2 RELEASE-NOTES-x86_64-en
Index: RELEASE-NOTES-x86_64-en
===================================================================
RCS file: /cvs/fedora/fedora-release/RELEASE-NOTES-x86_64-en,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -r1.1.1.1 -r1.2
--- RELEASE-NOTES-x86_64-en 5 Apr 2005 18:35:02 -0000 1.1.1.1
+++ RELEASE-NOTES-x86_64-en 6 Apr 2005 21:29:55 -0000 1.2
@@ -1,2002 +1,1009 @@
- Fedora Core 3 Release Notes
+== Fedora Core 4test2 Release Notes ==
- Copyright (c) 2004 Red Hat, Inc.
+Copyright (c) 2005 Red Hat, Inc.
- Permission is granted to copy, distribute, and/or modify this document
- under the terms of the GNU Free Documentation License, Version 1.2 or any
- later version published by the Free Software Foundation; with no Invariant
- Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the
- license is available at [1]http://www.gnu.org/licenses/fdl.html.
+Permission is granted to copy, distribute, and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is available at
+http://www.gnu.org/licenses/fdl.html.
+
+This document may be copied and distributed in any medium, either
+commercially or non-commercially, provided that the GNU Free
+Documentation License (FDL), the copyright notices, and the license
+notice saying the GNU FDL applies to the document are reproduced in
+all copies, and that you add no other conditions whatsoever to those
+of the GNU FDL.
+
+Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum
+RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover,
+RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based
+trademarks and logos are trademarks or registered trademarks of Red
+Hat, Inc. in the United States and other countries.
+
+The Fedora trademark is a trademark of Red Hat, Inc. in the United
+States and other countries.
+
+Linux is a registered trademark of Linus Torvalds.
+
+All other trademarks and copyrights referred to are the property of
+their respective owners.
+
+The GPG fingerprint of the "Fedora Project <fedora at redhat.com>" key
+is:
+
+CA B4 4B 99 6F 27 74 4E 86 12 7C DF B4 42 69 D0 4F 2A 6F D2
+
+---------------------------------------------------------------------------
+
+ 1. Fedora Core 4 test2 Release Notes
+ 2. Introduction
+ 3. Hardware Requirements
+ 1. CPU Requirements
+ 2. Hard Disk Space Requirements
+ 3. Memory Requirements
+ 4. Overview of This Release
+ 5. Installation-Related Notes
+ 6. Installation-Related Issues
+ 7. Package-Specific Notes
+ 1. Base
+ 2. Core
+ 3. Language Support
+ 4. Server Configuration Tools
+ 5. Sound and Video
+ 6. Web Server
+ 7. Windows File Server
+ 8. Macintosh File Server
+ 9. X Window System
+ 10. Miscellaneous Notes
+ 8. Packages Added, Moved From Core, Changed, or
+Deprecated/Nuked
+ 1. Packages Added
+ 2. Packages Moved Out Of Core
+ 9. An Overview of the Fedora Project
+ 10. References
+
+== Introduction ==
+
+The Fedora Project is an openly-developed project designed by Red Hat,
+open for general participation, led by a meritocracy, and following a
+set of project objectives. The results from this project include
+Fedora Core, a complete, general-purpose operating system built
+exclusively from open source software.
+
+NOTE: Fedora Core is not a supported product of Red Hat, Inc.
+
+For more information, refer to the Fedora Project overview later in
+this document.
+
+The following topics related to Fedora Core 4test2 are covered in this
+document:
+
+ * Introduction (this section)
+ * Hardware requirements
+ * Overview of this release
+ * Installation-related notes
+ * Package-specific notes
+ * Packages added/removed/deprecated
+ * An overview of the Fedora Project
+
+== Hardware Requirements ==
+
+The following information represents the minimum hardware requirements
+necessary to successfully install Fedora Core 4test2.
+
+Note
+
+The compatibility/availability of other hardware components (such as
+video and network cards) may be required for specific installation
+modes and/or post-installation usage.
+
+=== CPU Requirements ===
+
+This section lists the CPU specifications required by Fedora Core
+4test2.
+
+Note
+
+The following CPU specifications are stated in terms of Intel
+processors. Other processors (notably, offerings from AMD, Cyrix, and
+VIA) that are compatible with and equivalent to the following Intel
+processors may also be used with Fedora Core.
+
+ * Minimum: Pentium-class
+
+Fedora Core 4test2 is optimized for Pentium 4 CPUs, but also supports
+earlier CPUs (such as Pentium, Pentium Pro, Pentium II, Pentium III,
+and including AMD and VIA variants). This approach has been taken
+because Pentium-class optimizations actually result in reduced
+performance for non-Pentium-class processors, and Pentium 4 scheduling
+is sufficiently different (while making up the bulk of today's
+processors) to warrant this change.
+
+ * Recommended for text-mode: 200 MHz Pentium-class or better
+
+ * Recommended for graphical: 400 MHz Pentium II or better
+
+=== Hard Disk Space Requirements ===
+
+This section lists the disk space required to install Fedora Core
+4test2.
+
+Note
+
+The disk space requirements listed below represent the disk space
+taken up by Fedora Core 4test2 after the installation is
+complete. However, additional disk space is required during the
+installation to support the installation environment. This additional
+disk space corresponds to the size of /Fedora/base/stage2.img (on
+CD-ROM 1) plus the size of the files in /var/lib/rpm on the installed
+system.
+
+In practical terms, this means that as little as an additional 90MB
+can be required for a minimal installation, while as much as an
+additional 175MB can be required for an "everything" installation.
+
+Also, keep in mind that additional space will be required for any user
+data, and at least 5% free space should be maintained for proper
+system operation.
+
+ * Custom Installation (Minimal): 620MB
+ * Server: 1.1GB
+ * Personal Desktop: 2.3GB
+ * Workstation: 3.0GB
+ * Custom Installation (Everything): 6.9GB
+
+=== Memory Requirements ===
+
+This section lists the memory required to install Fedora Core 4test2.
+
+ * Minimum for text-mode: 64MB
+ * Minimum for graphical: 192MB
+ * Recommended for graphical: 256MB
+
+== Overview of This Release ==
+
+The following list highlights certain new features of Fedora Core
+4test2:
+
+ * GCC 4.0
+ * GNOME 2.10
+ * KDE 3.4
+ * Native Eclipse 3.1M5
+ * MySQL 4.1
+ * PHP 5.0
+
+ * SELinux -- New daemons have been added to the targeted policy For
+ more information, refer to the SELinux FAQ at
+ http://fedora.redhat.com/docs/selinux-faq/ .
+ * amanda
+ * apache
+ * chkpwd
+ * cups
+ * dhcpc
[...2614 lines suppressed...]
-
- o magicdev
-
- o mod_jk2
-
- o modutils
-
- o mx4j
-
- o mx4j-devel
-
- o mx4j-tools
-
- o mysql-jdbc
-
- o mysql-jdbc-tomcat
-
- o ncurses-c++-devel
-
- o njamd
-
- o nss_db-compat
-
- o pidentd
-
- o policy
-
- o policy-sources
-
- o policy-strict-sources
-
- o printman
-
- o python-optik
-
- o quanta
-
- o quanta-devel
-
- o raidtools
-
- o redhat-java-rpm-scripts
-
- o rep-gtk
-
- o samba (i386)
-
- o sawfish
-
- o servletapi
-
- o servletapi-devel
-
- o shapecfg
-
- o struts
-
- o struts-webapps
-
- o system-config-proc
-
- o tomcat
-
- o tomcat-devel
-
- o tomcat-libs
-
- o tomcat-test
-
- o unarj
-
- o xalan-j
-
- o xalan-j-devel
-
- o xalan-j-xsltc
-
- o xerces-j
-
- o xerces-j-devel
-
- o xffm-icons
-
- o xorg-x11-100dpi-fonts
-
- o xorg-x11-75dpi-fonts
-
- o xorg-x11-ISO8859-14-100dpi-fonts
-
- o xorg-x11-ISO8859-14-75dpi-fonts
-
- o xorg-x11-ISO8859-15-100dpi-fonts
-
- o xorg-x11-ISO8859-15-75dpi-fonts
-
- o xorg-x11-ISO8859-2-100dpi-fonts
-
- o xorg-x11-ISO8859-2-75dpi-fonts
-
- o xorg-x11-ISO8859-9-100dpi-fonts
-
- o xorg-x11-ISO8859-9-75dpi-fonts
-
- o xorg-x11-base-fonts
-
- o xorg-x11-cyrillic-fonts
-
- o xorg-x11-libs-data
-
- o xorg-x11-syriac-fonts
-
- o xorg-x11-truetype-fonts
-
- Packages Deprecated
-
- The following packages have been deprecated, and may be removed from a
- future release of Fedora Core:
-
- o dbskkd-cdb -- Only used by deprecated package skkinput
-
- o FreeWnn -- Only used by deprecated package kinput2-canna-wnn6
-
- o miniChinput -- IIIMF is the recommended input method
-
- o nabi -- IIIMF is the recommended input method
-
- o ncpfs -- No longer part of Fedora Core profile
-
- o skkinput -- IIIMF is the recommended input method
-
- o xcin -- IIIMF is the recommended input method
-
-An Overview of the Fedora Project
-
- The goal of the Fedora Project is to work with the Linux community to
- build a complete, general-purpose operating system exclusively from open
- source software. Development will be done in a public forum. The project
- will produce time-based releases of Fedora Core about 2-3 times a year,
- with a public release schedule. The Red Hat engineering team will continue
- to participate in building Fedora Core and will invite and encourage 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:
-
- [10]http://fedora.redhat.com/
-
- In addition to the website, the following mailing lists are available:
-
- o fedora-list at redhat.com -- For users of Fedora Core releases
-
- o fedora-test-list at redhat.com -- For testers of Fedora Core test
- releases
-
- o fedora-devel-list at redhat.com -- For developers, developers, developers
-
- o fedora-docs-list at redhat.com -- For participants of the docs project
-
- 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.)
-
- NOTE: If you have subscribed in the past to rhl-list, rhl-beta-list,
- rhl-devel-list, or rhl-docs-list, your subscriptions have been retained.
-
- The Fedora Project also includes an IRC (Internet Relay Chat) channel. IRC
- is a real-time, text-based form of communication. With it, you can have
- conversations with multiple people in an open channel or chat with someone
- privately one-on-one.
-
- To talk with other Fedora Project participants via IRC, access freenode
- IRC network. Initially, you can use irc.freenode.net as the IRC server,
- although you may decide to select a server that is geographically closer
- to you. Refer to the freenode website ([11]http://www.freenode.net/) for
- more information. Fedora Project participants frequent the #fedora
- channel, while Fedora Project developers can often be found on the
- #fedora-devel channel. Some of the larger projects may have their own
- channels as well; this information can be found on the project pages.
-
- NOTE: Red Hat has no control over the Fedora IRC channels or their
- content.
-
- ( x86_64 )
-
-References
-
- Visible links
- 1. http://www.gnu.org/licenses/fdl.html
- 2. http://fedora.redhat.com/docs/selinux-faq/
- 3. http://www.redhat.com/archives/fedora-desktop-list/2004-June/msg00007.html
- 4. http://mail.gnome.org/archives/desktop-devel-list/2004-June/msg00370.html
- 5. http://platan.vc.cvut.cz/ftp/pub/vmware/
- 6. http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119474
- 7. http://i2o.shadowconnect.com/
- 8. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133478
- 9. http://people.redhat.com/~harald/udev.html
- 10. http://fedora.redhat.com/
- 11. http://www.freenode.net/
+11. http://www.freenode.net/
Index: fedora-release.spec
===================================================================
RCS file: /cvs/fedora/fedora-release/fedora-release.spec,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- fedora-release.spec 5 Apr 2005 19:02:08 -0000 1.2
+++ fedora-release.spec 6 Apr 2005 21:29:55 -0000 1.3
@@ -1,14 +1,16 @@
+%define release_version 3.91
+%define release_version Pre-FC4
%define builtin_release_version Rawhide
%define builtin_release_name Rawhide
%define real_release_version %{?release_version}%{!?release_version:%{builtin_release_version}}
%define real_release_name %{?release_name}%{!?release_name:%{builtin_release_name}}
Summary: Fedora Core release file
Name: fedora-release
-Version: 3.91
+Version: %{real_release_version}
Release: 1
Copyright: GFDL
Group: System Environment/Base
-Source: fedora-release-3.91.tar.gz
+Source: fedora-release-%{real_release_version}.tar.gz
Obsoletes: rawhide-release
Obsoletes: redhat-release
Obsoletes: indexhtml
- Previous message (by thread): rpms/xemacs-sumo/devel xemacs-sumo.spec,1.3,1.4
- Next message (by thread): fedora-release RELEASE-NOTES-i386-en, 1.2, 1.3 RELEASE-NOTES-ppc-en, 1.2, 1.3 RELEASE-NOTES-x86_64-en, 1.2, 1.3 index.html, 1.1.1.1, 1.2
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the fedora-extras-commits
mailing list