Download
FAQCopyright © 2005 Red Hat, Inc.
This document is released under the terms of the GNU Free Documentation License. For more details, read the full legalnotice in Section 2, “Legalnotice”.
![[Tip]](./stylesheet-images/tip.png) |
Latest Release Notes on the Web |
|---|---|
|
These release notes may be updated. Visit http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core 5 test1. Another source for updated information about the test release is http://fedoraproject.org/wiki/FC5Test1CommonProblems. | |
- 1. Welcome to Fedora Core 5 test1
- 2. Legalnotice
- 3. Introduction and Technical Release Notes
- 4. Hardware Requirements
- 5. Overview of This Release
- 6. Installation-Related Notes
- 7. Package-Specific Notes
- 8. Legacy Information
- 9. Packages Movement
- 10. Notes
- 11. An Overview of the Fedora Project
Fedora Core is a completely free, user friendly, and secure general purpose platform based on Linux that is always free for anyone to use, modify, and distribute, now and forever. The Fedora Project is an open source project that pioneers leading edge technology and concepts, which is sponsored by Red Hat and supported by the Fedora community.
![[Caution]](./stylesheet-images/caution.png) |
This is a test release, not intended for end-users |
|---|---|
|
This is a test release and is provided for developers and testers to participate and provide feedback. It is not meant for end users. Subscribe to the fedora-test and fedora-devel mailing lists to keep track of important changes in the current development versions and provide feedback to the developers. Fedora Project requests you to file bug reports and enhancements to provide a improved final release to end users. For more information on this, refer to the following document: | |
|
Latest Release Notes on the Web |
|---|---|
These release notes may be updated. Visit http://fedora.redhat.com/docs/release-notes/ to view the latest release notes for Fedora Core 5 test1. | |
Refer to these webpages to find out more information about Fedora:
Section 3, “Introduction and Technical Release Notes” — Technical release notes
Help and Support (http://fedora.redhat.com/participate/communicate/)
Participate in the Fedora Project (http://fedora.redhat.com/participate/)
About the Fedora Project (http://fedora.redhat.com/about/)
Xen virtualisation software and yum package manager are now well integrated within the Fedora installer. The installer interface is more streamlined. Remote logging and improved support for tracebacks is included.
Pup, a graphical updater using yum, has replaced rhn-applet.
GNOME 2.12 and KDE 3.4 desktop environments are available.
GNOME Power Manager and GNOME Screensaver are available as a technology preview within this release.
OpenOffice.org 2.0 final release is included. OpenOffice.org now uses system versions for many of the libraries leading to increased performance and efficiency.
Xorg X11R7 release candidate 2 has been included in this release. This is the first modular version, which helps in providing additional features and bug fixes at a faster pace.
Kernel 2.6.14 is included. Software suspend is enabled in this release.
SCIM has replaced IIMF in Fedora Core in this release.
There are changes in the animated mouse cursor theme.
Fedora Project now has a new logo.
The proposed plans for Fedora in this version are available from http://fedoraproject.org/wiki/RoadMap.
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 noncommercially, 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.
Garrett LeSage created the admonition graphics (note, tip, important, caution, and warning). Tommy Reynolds <Tommy.Reynolds@MegaCoder.com> created the callout graphics. They all may be freely redistributed with documentation produced for the Fedora Project.
RELEASE-NOTES-FC5 test1 (2005-11-24-T23:10+0000)
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other countries.
All other trademarks and copyrights referred to are the property of their respective owners.
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, which is a complete, general-purpose operating system built exclusively from open source software.
![[Note]](./stylesheet-images/note.png) |
Note |
|---|---|
|
Fedora Core is a community supported project. Fedora Core is not a commercially supported product of Red Hat, Inc.. | |
For more information, refer to Section 5, “Overview of This Release”.
Additional important information about this release may be made available at http://fedora.redhat.com/docs/release-notes/. Users are advised to check this link regularly for updates.
For reporting errors or other requests about these release notes, file a bug report using this pre-filled bugzilla template.
This http://tinyurl.com/byvk2 will take you to the same pre-filled bugzilla template.
The following information represents the minimum hardware requirements necessary to successfully install Fedora Core 5 test1.
|
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. | |
This section lists the CPU specifications required by Fedora Core 5 test1.
|
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 5 test1 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
AMD64 processors (both Athlon64 and Opteron)
Intel processors with Intel® Extended Memory 64 Technology (Intel® EM64T)
This section lists the disk space required to install Fedora Core 5 test1.
|
Note |
|---|---|
|
The disk space requirements listed below represent the disk space taken up by Fedora Core 5 test1 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. | |
This list is for 32-bit x86 systems:
Custom Installation (Minimal): 620MB
Server: 1.1GB
Personal Desktop: 2.3GB
Workstation: 3.0GB
Custom Installation (Everything): 6.9GB
This list is for 64-bit x86_64 systems:
Custom Installation (Minimal): 900MB
Server: 1.5GB
Personal Desktop: 2.7GB
Workstation: 3.4GB
Custom Installation: (Everything) 7.5GB
This section lists the memory required to install Fedora Core 5 test1.
This list is for 32-bit x86 systems:
Minimum for text-mode: 64MB
Minimum for graphical: 192MB
Recommended for graphical: 256MB
This list is for 64-bit x86_64 systems:
Minimum for text-mode: 128MB
Minimum for graphical: 256MB
Recommended for graphical: 512MB
This section lists the minimum PowerPC (PPC) hardware needed to install Fedora Core 5 test1.
Minimum: PowerPC G3 / POWER4
Fedora Core 5 test1 supports the “New World” generation of Apple Power Macintosh (shipped circa 1999 onwards), Genesi Pegasos II, and IBM 32-bit RS/6000 machines. It also supports the 64-bit G5 processor, and POWER processors in the IBM eServer pSeries.
Recommended for text-mode: 233 MHz G3 or better
Recommended for graphical: 400 MHz G3 or better
This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core 5 test1 in general.
|
Note |
|---|---|
|
If you intend to download the Fedora Core 5 test1 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GiB in size. For example, wget before version 1.9.1.16 in exits with a File size limit exceeded error. The wget version 1.9.1-16 and later, curl and ncftpget file downloading tools do not have this limitation, and can successfully download files larger than 2GiB. Bittorrent is another method for downloading large files. For information about obtaining and using the torrent file refer to this website: | |
The DVD or first CD of the installation set of Fedora Core is set to be bootable on supported hardware. In addition, bootable CD images can be found in the images/ directory of the DVD or first CD. These behave differently according to the hardware:
Boot Image Behavior by Hardware
- Apple Macintosh
The bootloader automatically boots the appropriate 32-bit or 64-bit installer. Power management support, including sleep and backlight level management, is present in the apmud package, which is in Fedora Extras. Fedora Extras for Fedora Core is configured by default for yum. Following installation, apmud can be installed by running the command yum install apmud in a terminal.
- 64-bit IBM eServer pSeries (POWER4/POWER5)
After using OpenFirmware to boot the CD, the bootloader (yaboot) automatically boots the 64-bit installer.
- 32-bit CHRP (IBM RS/6000 and others)
After using OpenFirmware to boot the CD, select the linux32 boot image at the boot: prompt to start the 32-bit installer. Otherwise, the 64-bit installer is started, which does not work.
- Genesi Pegasos II
-
As of Fedora Core 5 test1, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, the network boot image can be used. At the OpenFirmware prompt, enter the command:
boot cd: /images/netboot/ppc32.imgYou also need to configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, you need to set the boot-device and boot-file environment variables appropriately.
- Network booting
-
There are combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the install tree. These are intended for network booting with TFTP, but can be used in many ways.
The command yaboot supports TFTP booting for IBM eServer pSeries and Apple Macintosh. Fedora recommends using yaboot over the netboot images.
-
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.
The mediacheck function is highly sensitive, and may report some usable discs as faulty. This result is often caused by disc writing software that does not include padding when creating discs from ISO files. For best results with the mediacheck, boot with the option:
linux ide=nodma
Use the sha1sum utility to verify discs before carrying out an installation. This test accurately identifies discs that are not valid or identical to the ISO image files.
-
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 5 test1 supports graphical FTP and HTTP installations. However, due to the necessity of containing the installer image in RAM, only systems with more than 128MiB of RAM (or systems booted from CD-ROM 1, which contains the installer image) can use the graphical installer. Systems with 128MiB of RAM or less must continue to use the text-based installer.
Support has been added for yum as the dependancy solver backend for software packages has been added. Additional repositories are expected to be supported during installation in a future release.
In this release, the installer checks the hardware capability and installs either the uniprocessor or SMP (Symmetric Multi Processor) kernel, as appropriate. Previous releases installed both the variants and used the appropriate one as default.
Partition setting has been reworked to be more user friendly.
Remote logging via syslog is supported in this release. To enable, pass syslog=host:port at the boot prompt. Specifying the port is optional.
Firewall/SELinux configuration has been moved to the final installation phase called firstboot.
Rendering of HTML pages during install is now done using the gtkhtml widget for better capability.
Kickstart has been refactored into its own package - pykickstart - containing parser and writers. As a result of this change, validation and extension of kickstart is now much easier.
Serial mice are no long formally supported in the installer nor in Fedora Core.
-
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® 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,0x386This 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:
-
There have been issues observed when upgrading Red Hat Linux 7.<x>, 8.0, 9, and Fedora Core 1, 2, and 3 systems where third party packages are installed that conflict with packages provided by Fedora Project. One example is Ximian GNOME.
The issue with Ximian GNOME 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 particular issue:
You may remove Ximian GNOME from your system prior to upgrading to Fedora Core.
You may upgrade your system, and then immediately reinstall Ximian GNOME.
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.
The following sections contain information regarding packages that have undergone significant changes for Fedora Core 5 test1. For easier access, they are generally organized using the same groups used in Anaconda.
This section contains information related to basic system components.
Fedora Extras is part of the larger Fedora Project and is a volunteer-based community effort to create a repository of packages that compliment Fedora Core. The Fedora Extras repository is enabled by default from Fedora Core 5 test1 onwards.
You can lean more about Fedora Extras from:
http://fedoraproject.org/wiki/Extras
If you would like to install any software available from Fedora extras you can use yum.
yum install <packagename>
Where <packagename> is the name of the package you want to install. For example, if you wanted to install the abiword package, the command yum install abiword automatically installs the package and all dependencies.
The audit daemon, auditd, is now enabled by default. When auditd is running, the kernel directs audit messages to /var/log/audit/audit.log. The location of this file is specified in /etc/auditd.conf.
AVC messages for SELinux are sent using the audit infrastructure. These messages are now in /var/log/audit/audit.log.
When auditd is not running, the kernel passes audit messages to syslog. These logs are typically kept in /var/log/messages and are viewable using dmesg.
Audit extensions are now compiled into PAM. All programs that do grant entry to the system or change user account attributes will generate an audit message.
To enable auditing within the kernel, you must pass the parameter audit=1 to the kernel during boot. Otherwise, you can use this command to enable auditing during run time:
auditctl -e 1
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.
The version of OpenSSH in Fedora Core 5 test1 is based on OpenSSH 3.9 and includes strict permission and ownership checks for the user configuration file ~/.ssh/config. If this file does not have appropriate ownership and permissions, ssh will exit.
Check that ~/.ssh/config is owned by the owner of ~/, and that its permissions are set to mode 600.
ls -l ~/.ssh/config -rw------- 1 username username 400 May 5 18:44 /home/username/.ssh/config
The directory ~/ is command-line shorthand for the logged in user's home directory, usually /home/username/.
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 option 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 option instead of the -X option, or set ForwardX11Trusted in the ~/.ssh/config file.
Fedora Core 5 test1 users are advised not to use the Java RPM provided by Sun. It contains Provides that conflict with names used in packages provided as part of Fedora Core 5 test1. Because of this, Sun Java might disappear from an installed system during package upgrade operations.
Fedora Core 5 test1 users should use either the RPM from jpackage.org or manually install the Sun Java tarball into /opt.
This section contains the most elemental components of Fedora Core, including the kernel.
This distribution is based on the 2.6 series of the Linux kernel. Fedora Core may include patches for improvements, bug fixes, or additional features. For this reason, the Fedora Core kernel may not be line-for-line equivalent to the vanilla kernel from the http://www.kernel.org/ website.
You may obtain a list of any such patches by using this command on the Fedora Core package:
rpm -qpl kernel-<version>.src.rpm
Fedora Core includes the following kernel builds:
Native kernel, in both uniprocessor and SMP (Symmetric Multi Processor) varieties. Configured sources are available in the kernel-devel-version.arch.rpm package.
Virtual kernel for use with the Xen emulator package. Configured sources are available in the kernel-xen0-devel-version.arch.rpm package.
Sources for both kernel flavors may be installed at the same time. The files are installed into the /usr/src/kernels/version[-xen0]-arch/ tree. Use the command rpm -Uvh kernel-devel[-xen0]-version.arch.rpm as appropriate.
|
No separate SMP kernel for x86_64 |
|---|---|
The default kernels in x86_64 architecture provide the SMP capability. There is no seperate SMP kernel available for this architecture in Fedora Core 5 test1. | |
Many of the tutorials, examples, and textbooks about Linux kernel development assume the kernel sources are installed under the /usr/src/linux/ directory. If you make a symbolic link, as shown below, you should be able to use those learning materials with the Fedora Core packages. Install the appropriate kernel sources, as shown earlier, and then do this:
ln -s /usr/src/kernels/kernel-version-arch /usr/src/linux
Fedora Core 5 test1 does not include the kernel-source package provided by older versions. Instead, configured sources are available as described in Section 7.2.1.2, “Kernel Flavors”. Users that require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package.
To create an exploded source tree from this file, perform the following steps:
|
Instructions refer to currently-running kernel |
|---|---|
To simplify the following directions, it is assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, the phrase version refers to the kernel version shown by the command uname -r. | |
-
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.
Install by running this command:
yum install yum-utils yumdownloader --source kernel -
Install kernel-version.src.rpm using the command rpm -Uvh kernel-version.src.rpm.
This writes the RPM contents into /usr/src/redhat/SOURCES and /usr/src/redhat/SPECS.
-
Prepare the kernel sources with these commands:
cd /usr/src/redhat/SPECS rpmbuild -bp --target $(arch) kernel-2.6.specThe kernel source tree is then located in the /usr/src/redhat/BUILD/kernel-version/ directory. It is common practice to move the resulting linux-version directory to the /usr/src/ tree; while not strictly necessary, you can do this to match the generally-available kernel documentation.
cd /usr/src/redhat/BUILD/kernel-version mv linux-version /usr/src/ cd /usr/src\ ln -s ./linux-version linux cd /usr/src/linux -
The configurations for the specific kernels shipped in Fedora Core are in the configs/ directory. For example, the i686 SMP configuration file is named configs/kernel-version-i686-smp.config. Issue the following command to place the desired configuration file in the proper place for building: cp configs/desired-config-file .config
You can also find the .config file that matches your current kernel configuration in the /lib/modules/version/build/.config file.
-
Every kernel gets a name based on its version number. This is the value displayed by the command uname -r. The kernel name is defined by the first four lines of the kernel Makefile. To protect from mistakes, the Makefile has been changed to generate a kernel with a different name from that of the running kernel. Before a module can be accepted by the running kernel, that module must have been compiled for a kernel with the correct name. To do this, you must edit the kernel Makefile.
For example, if uname -r returns the string 2.6.11-1.234_FC4, change the EXTRAVERSION definition from this:
EXTRAVERSION = -prep
to this:
EXTRAVERSION = -1.234_FC4
This represents everything from the final dash onward in the package name.
-
Issue the following command:
make oldconfigYou can then proceed as usual.
An exploded source tree is not required to build a kernel module, such as your own device driver, against the currently in-use kernel. For example, to build the foo.ko module, create the following Makefile in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
ndefault:
$(MAKE) -C $(KDIR) M=$(PWD) modules
Issue the make command to build the foo.ko module.
Fedora Core 5 test1 has support for clustered storage through the Red Hat GFS file system. This requires a special kernel that works in conjunction with some user-space utilities, such as management daemons. Consequently, to remove such a kernel, perhaps after an update, you cannot simply use the rpm -e kernel-version command as in earlier distributions because these user space packages depend on the kernel package.
You may either list both the kernel package and its user space dependent packages on the rpm -e command, or you may wish to use the yum remove kernel-version command instead since yum automatically removes dependent packages if necessary.
This section highlights various security items from Fedora Core.
Pam_stack is deprecated. Linux-PAM 0.78 and later contain the include directive that obsoletes the pam_stack module. pam_stack module usage is logged with a deprecation warning. It might be removed in a future release.
This section highlights various security items from Fedora Core.
- Buffer Overflow detection and variable reordering
-
For this release, all of the software in the Fedora Core and Fedora Extras software repositories is compiled using a security feature called fstack-protecter. fstack-protector puts a canary value on the stack of key functions. Just before the return address and just before returning from that value, that canary value is verified. If there was a buffer overflow, the canary no longer matches and the program aborts. The canary value is random for each time the application is started and makes it impossible to guess remotely. This is a security feature that has been backported from GCC 4.1 to the version of the GCC compiler used in Fedora Core 5 test1.
This is in addition to using FORTIFY_SOURCE from Fedora Core 4 onwards.
- Digital certificates
Digital certificates are now centralised in directories under /etc/pki/. Users performing an upgrade must relocate their digital certificates.
- OpenSSL
For OpenSSL, the /usr/share/ssl/ contents have moved to /etc/pki/tls/ and /etc/pki/CA/.
- Dovecot
The dovecot-openssl.cnf file is automatically installed in /etc/pki/dovecot/.
Mult-Category Security (MCS) SELinux is included in Fedora Core 5 test1. For more information, read this informative article:
A Java-like free and open source environment is available within the Fedora Core 5 test1 release.
It has three components: GNU Java runtime (libgcj), the Eclipse Java compiler (ecj), and a set of wrappers and links (java-gcj-compat) that present the runtime and compiler to the user in the same way as other Java environments are presented.
Several major software packages such as Openoffice.org Base, Eclipse, and Apache Tomcat, as well as several other Java software packages included in this release, are compatible with this environment.
For more information, refer to the FAQ:
SCIM has replaced all the other input methods. Major highlight.
Fedora Core includes applications for assorted multimedia functions, including playback, recording, and editing. Additional packages are available through the Fedora Extras repository.
- Multimedia Players
-
By default, Fedora Core installs with rhythmbox, totem, and Helix Player (hxplay) for media playback. In addition, many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular xmms package. Both GNOME and KDE also have specific sets of programs that can be used with a variety of formats. Other popular programs, such as Adobe/Macromedia's Flash Player, Real Player, VLC, MPlayer, and Xine, can also be installed, but are excluded from the Fedora repositories since they are not compatible with Fedora's licensing or are usually distributed with support for restricted formats. For more on this, refer to Section 7.5.1, “Excluded Multimedia Software”.
Fedora Core is also equipped to take full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. This means that many programs can play sound simultaneously, which was once difficult on Linux systems. When all multimedia software is configured to use ALSA for sound support, this old limitation disappears. For more information about ALSA, visit the project website:
- Ogg and Xiph.Org Foundation Formats
-
Fedora includes complete support for the Ogg media container format, the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. More information on these formats and how to use them can be found at the Xiph.Org Foundation's web site:
- MP3 & DVD Support
Fedora Core and Fedora Extras cannot include support for MP3 or DVD playback or recording, because the MP3 and MPEG (DVD) formats are patented, and the patent owners have not provided the necessary licenses. For more information, refer to Section 7.5.1, “Excluded Multimedia Software”.
Several programs are excluded from Fedora Core and Fedora Extras due to licensing issues. These include programs that provide MP3 and DVD support, Flash Player and Real Player. For more on this subject, please refer to:
Tools are included in Fedora Core and Fedora Extras for easily mastering and burning CDs and DVDs. Tools that can be used from the console include cdrecord, readcd, mkisofs, and other typical Linux applications. For GNOME users, the xcdroast package from Fedora Core and the graveman package from Fedora Extras allow easy preparation of audio and data discs. For KDE users, the k3b package provides a very robust tool for these tasks.
This section contains information on Web-related applications.
This section contains information related to Samba, the suite of software that enables Linux to interact with Microsoft Windows systems.
Browsing of Windows shares (also known as SMB browsing) fails on Fedora Core 5 test1 systems that have the standard firewall configured. This is most easily noticed in the failure of the desktop to display shares.
The firewall disrupts the broadcast mode of SMB browsing, which is the default. 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]](./stylesheet-images/warning.png) |
Disabling the firewall may make your system vulnerable |
|---|---|
Make sure you fully understand the risks before undertaking this step. | |
For additional information, refer to the following bug report:
This section contains information related to the X Window System implementation provided with Fedora.
X.org X11 is an open source implementation of the X Window System. It provides the basic low level functionality that full fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed upon.
For more information about Xorg refer to http://xorg.freedesktop.org/wiki/
You can use or run system-config-display to configure the settings. The configuration file for Xorg is located in /etc/X11/xorg.conf.
Modular X.Org X11R7 RC2 was released into Fedora development (rawhide) on November 16, 2005. This is the first modular release of Xorg. Among several benefits, modular Xorg enables users to receive updates at a faster pace, while helping developers to develop and release specific components in a rapid fashion.
More information on the current status of the Xorg modularization effort in Fedora is available from http://fedoraproject.org/wiki/Xorg/Modularization
X11R7 RC2 is included in this release and there are a number of things that software developers, and packagers in Fedora repositories, need to be aware of in order to ensure that their software or software packages properly compile and work with X11R7. Some are simple changes, while others may be more involved. Here is a summary of issues that may arise and where possible, suggestions on how to fix them.
X11R7 installs into /usr directly now, and no longer uses the /usr/X11R6 hierarchy. Applications that rely on files being present at fixed paths under /usr/X11R6 at compile time or at run time, must be updated to use the system PATH, or some other mechanism, to dynamically determine where the files reside, or alternatively to hard code the new locations, possibly with fallbacks.
Imake is no longer used to build the X Window System, and as such is now officially deprecated. Imake, xmkmf and other utilities previously supplied by the X Window System, are still supplied in X11R7, however X.Org highly recommends that people migrate from Imake to using GNU autotools and pkg-config. Support for imake may vanish in a future X Window System release, so developers are strongly encouraged to transition away from it, and not to use it for any new software projects.
The system app-defaults directory for X resources, is now %{_datadir}/X11/app-defaults, which expands to /usr/share/X11/app-defaults on Fedora Core 5 test1 and for future Red Hat Enterprise Linux systems.
Modular X now uses GNU autotools, and pkg-config for its buildsystem configuration, etc. xft-config has been deprecated for two to three years, and pkgconfig *.pc files have been provided for most of this time. Applications that previously used xft-config to obtain the Cflags or libs options for building with, must now be updated to use pkg-config.
Here is a short list of some of the more developer/package visible changes that are present in X11R7:
The entire buildsystem has changed from Imake to the GNU autotools collection.
All of the libraries now install pkgconfig *.pc files, which should now always be used by software that depends on these libraries, instead of hard coding paths to them in /usr/X11R6/lib or elsewhere.
Everything is now installed directly into /usr instead of /usr/X11R6. All software that hard codes paths to anything in /usr/X11R6, must now be changed preferably to dynamically detect the proper location of the object, or to hard code the new paths that X11R7 uses by default. It is strongly advised to use autodetection methods rather than to hard code paths.
-
Every library has its own, private source package now, which creates a runtime binary subpackage, and a -devel subpackage.
Any software package that previously picked up the development headers, etc. for X libraries by using BuildRequires: (XFree86-devel|xorg-x11-devel), must now individually list each library dependency individually. When doing this, it is greatly preferred and strongly recommended to use virtual build dependencies instead of hard coding the library package names of the Xorg implementation.
This means you should use: BuildRequires: libXft-devel instead of using: BuildRequires: xorg-x11-Xft-devel. If your software truly does depend on the X.Org X11 implementation of a specific library, and there is no other clean/safe way to state the dependency, then use the xorg-x11--devel form. By sticking to the virtual provides/requires mechanism, this makes it painless if and when the libraries move to another location in the future.
Fedora Core and Fedora Extras provide a selection of games that cover a variety of genres. By default, Fedora Core includes a small package of games for GNOME (called gnome-games). For a list of other games that are available for installation through yum, open a terminal and enter the following command:
yum groupinfo "Games and Entertainment"
For help using yum to install the assorted game packages, refer to the guide available at:
|
Slocate has been replaced with mlocate in this release. |
|---|---|
The /usr/bin/{locate,updatedb} implementation slocate was replaced by mlocate. | |
The locate command should be completely compatible.
/etc/updatedb.conf is compatible for correct configuration files
Syntax errors that slocate would not detect are now reported.
The DAILY_UPDATE variable is not supported.
The updatedb command is not compatible, custom scripts using updatedb might have to be changed.
The LinuxThreads library, which has been deprecated in Fedora Core 4, is no longer available in this release. NPTL has been the default threading library since Red Hat Linux 9.
These packages have been added to Fedora Core for this release notes.
scim-anthy-0.6.1-1.fc5
struts-1.2.4-2jpp_3fc
jonas-4.3.3-1jpp_10fc
nspr-4.6-4
scim-1.4.2-3
anthy-6829-3
system-config-cluster-0.9.69-1.0
axis-1.2.1-1jpp_1fc
bsf-2.3.0-6jpp_2fc
bsh-1.3.0-5jpp_1fc
concurrent-1.3.2-2jpp_1fc
dtdparser-1.21-2jpp_1fc
jakarta-commons-discovery-0.3-1jpp_1fc
jdom-1.0-1jpp_2fc
wsdl4j-1.5.1-1jpp_1fc
javacc-3.2-1jpp_3fc
jakarta-commons-httpclient-3.0-0.rc2.0jpp_1fc
castor-0.9.5-1jpp_1fc
adaptx-0.9.6-1jpp_1fc
amtu-1.0.2-1
xdoclet-1.2.2-2jpp_1fc
xjavadoc-1.1-1jpp_1fc
jgroups-2.2.6-1jpp_1fc
hsqldb-1.80.1-1jpp_1fc
jonathan-core-4.1-1jpp_4fc
jonathan-jeremie-4.2-1jpp_4fc
jrefactory-2.8.9-3jpp_1fc
mockobjects-0.09-12jpp_2fc
monolog-1.8.6-1jpp_5fc
oldkilim-1.1.3-2jpp_3fc
p6spy-1.3-2jpp_3fc
fractal-2.2-2jpp_1fc
velocity-1.4-3jpp_1fc
werken.xpath-0.9.4-0.beta.9jpp_1fc
gnu.regexp-1.1.4-7jpp_1fc
nanoxml-2.2.3-3jpp_3fc
asm-1.5.3-1jpp_1fc
cairo-1.0.0-1
objectweb-anttask-1.2-1jpp_1fc
objectweb-deploysched-0.2-1jpp_1fc
carol-1.8.9.3-1jpp_5fc
jacorb-2.2-3jpp_3fc
jakarta-commons-cli-1.0-6jpp_1fc
tanukiwrapper-3.1.1-4jpp_3fc
tog-pegasus-2.4.1-4.FC5
joram-4.1.5-1jpp_5fc
jotm-2.0.5-1jpp_3fc
lucene-1.4.3-1jpp_1fc
geronimo-specs-1.0-0.M2.2jpp_4fc
jakarta-commons-codec-1.3-2jpp_1fc
howl-logger-0.1.8-1jpp_3fc
dhcdbd-1.8-1
aspell-ru-0.99f7-2
hplip-0.9.5-3
gpart-0.1h-1
iso-codes-0.47-1
gif89encoder-0.90-0.b.1jpp_1fc
jonathan-rmi-3.1-5
pup-0.0.2-1
jorm-2.4.3-1jpp_2fc
jorm-rdb-adapter-2.6-1jpp_1fc
medor-1.4.4-1jpp_1fc
medor-expression-1.4.2-1jpp_1fc
perseus-cache-1.3.4-1jpp_1fc
perseus-concurrency-1.4-1jpp_1fc
perseus-dependency-1.4-1jpp_1fc
perseus-distribution-1.3.2-1jpp_1fc
perseus-fos-1.3.1-1jpp_1fc
perseus-persistence-1.3.4-1jpp_1fc
perseus-pool-1.3.3-1jpp_1fc
systemtap-0.4.1-2
pcmciautils-007-1
scim-tables-0.5.3-4
libsemanage-1.3.2-1
scim-hangul-0.2.0-5.fc5
scim-pinyin-0.5.91-1
scim-chewing-0.2.1-1
scim-qtimm-0.9.4-1
libchewing-0.2.7-1
kasumi-0.9-3.fc5
kexec-tools-1.101-2
libsetrans-0.1.7-1
icu-3.4-4
libiec61883-1.0.0-8.fc5
These packages have been removed:
ccs-0.25-0.17
cman-1.0-0.pre33.15
cman-kernel-2.6.11.5-20050601.152643.FC4.2
dlm-1.0-0.pre21.10
dlm-kernel-2.6.11.5-20050601.152643.FC4.2
fence-1.27-16
GFS-kernel-2.6.11.8-20050601.152643.FC4.2
gnbd-1.0-0.pre14.6
gulm-1.0-0.pre30.1
iddev-1.9-21
magma-1.0-0.pre21.7
magma-plugins-1.0-0.pre18.3
system-config-mouse configuration utility has been dropped in this release because synaptic and 3 button mouse configuration is being done automatically and serial mice are not supported.
Screensavers not installed by default anymore? Explain why and provide commands to install them.
The goal of the Fedora Project is to work with the Linux community to build a complete, general-purpose operating system exclusively from open source software. Development is done in a public forum. The project produces time-based releases of Fedora Core approximately 2-3 times a year, with a public release schedule. The Red Hat engineering team continues to participate in building Fedora Core and invites and encourages more outside participation than was possible in the past. By using this more open process, we hope to provide an operating system more in line with the ideals of free software and more appealing to the open source community.
For more information, refer to the Fedora Project website:
In addition to the website, the following mailing lists are available:
fedora-list@redhat.com — For users of Fedora Core releases
fedora-test-list@redhat.com — For testers of Fedora Core test releases
fedora-devel-list@redhat.com — For developers, developers, developers
fedora-docs-list@redhat.com — For participants of the Documentation Project
fedora-ambassadors-list@redhat.com — For community members who represent the Fedora Project in public.
To subscribe to any of these lists, send an email with the word "subscribe" in the subject to <listname>-request (where <listname> is one of the above list names.)
Alternately, you can subscribe through the Web interface:
http://www.redhat.com/mailman/listinfo/
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 (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.
In order to talk on the #fedora channel, you will need to register your nickname (nick). Instructions are given when you first /join the channel.
|
Note |
|---|---|
Red Hat has no control over the Fedora Project IRC channels or their content. | |