system-config-packages. These applications are built on the yum utility to provide consistent software installation and update facilities throughout the system.
java-gcj-compat include Azureus, a BitTorrent client, and RSSOwl, a RSS feed reader, now available in Fedora Extras.
libnotify, a library that features simple and attractive notifications for the desktop.
gnome-mount, a more efficient mechanism that replaces fstab-sync, and uses HAL to handle mounting.
hplip utility, which replaces hpijs.
gnome-applet-vm, which provides a simple virtual domains monitor applet, and libvirt (http://libvirt.org/), a library providing an API to use Xen virtualization capabilities.
anaconda installation system continues to evolve. New features for this release include remote logging and improved support for tracebacks. Package management in the installation system is now provided by yum. This enhancement is the first step in enabling access to Fedora Extras from within the installation process.
GCJ, such as the Geronimo J2EE server and the Apache Jakarta Project, in addition to the Java programs and development capabilities in the previous releases.
system-config-cluster, a utility that allows you to manage cluster configuration in a graphical setting.
iscsi-initiator-utils, iSCSI daemon and utility programs that provide support for hardware using the iSCSI interface.
fedora-release now includes the software repositories for debuginfo packages and source rpm packages.
fedora-release now includes the software repositories for Fedora Legacy community maintenance project. (disabled by default)
pcmcia-cs package using the cardmgr/pcmcia service has been replaced with a new pcmciautils package. With pcmciautils, PCMCIA devices are handled directly and dynamically by the hotplug and udev subsystems. This update increases both efficiency and performance of the system. For more information about these changes, refer to http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html.
udev provides a new linking for device names that includes the physical name of the device. For example, if your CD-ROM is /dev/hdc, it gets symlinked to the friendly name /dev/cdrom-hdc. If you have additional matching devices, the same rule applies, so /dev/hdd is symlinked to /dev/cdrom-hdd. This is true for /dev/scanner, /dev/floppy, /dev/changer, and so forth.
/dev/cdrom is also created, and udev assigns it randomly to one of the /dev/cdrom-hdX devices. This random assignment usually sticks, but in some configurations the symlink may change on boot to a different device. This does not affect CD burning applications, but some CD player applications such as kscd may be affected. If you wish, you can set your CD player application to point at a specific CD-ROM device, such as /dev/cdrom-hdc. This situation only occurs if you have more than one of a type of device.