downloadDownload FAQFAQ
Site Navigation:
 
 

Note di rilascio per Fedora Core 5

Fedora Documentation Project

Questo documento è rilasciato sotto i termini della Open Publication License. Per maggiori dettagli, leggi le note legali complete su Sezione 3, «Legal Notice».

[Suggerimento] Ultime note di rilascio sul web

Queste note di rilascio possono essere state aggiornate. Visita http://fedora.redhat.com/docs/release-notes/ per vedere le ultime note di rilascio per Fedora Core 5.

Diario delle Revisioni
Revisione 0.5.0.0 2006-02-28 quaid

(...)


1. Benvenuti in Fedora Core
2. Panoramica di Fedora Core 5
2.1. Cos'è cambiato da Fedora Core 4
2.1.1. Desktop
2.1.2. Amministrazione di sistema
2.1.3. Cambiamenti a livello di sistema
2.2. Piano di sviluppo
3. Legal Notice
4. Providing Feedback for Release Notes
5. Note relative all'installazione
6. Architecture Specific Notes
6.1. Specifiche PPC per Fedora
6.1.1. Requisiti hardware PPC
6.1.2. The Apple keyboard
6.1.3. Note di installazione PPC
6.2. Specifiche x86 per Fedora
6.2.1. Requisiti hardware x86
6.3. Specifiche x86_64 per Fedora
6.3.1. Requisiti hardware x86_64
6.3.2. RPM Multiarch Support on x86_64
7. Note sui pacchetti
7.1. Kernel device, module loading, and hotplug changes
7.2. Cambiamenti nella ricerca sul sistema
7.3. Rimozione dell'utilità di configurazione del mouse
7.4. NetworkManager
7.5. Dovecot
7.6. Kudzu
7.7. No automatic fstab editing for removable media
7.8. GnuCash
7.9. Mozilla
7.10. libstc++ preview
7.11. LinuxThreads support removed
8. Kernel Linux
8.1. Versione
8.2. Changelog
8.3. Tipi di Kernel
8.4. Reporting Bugs
8.5. Seguire libri di testo generici
8.6. Preparazione allo sviluppo del Kernel
8.7. Compilare solo i moduli del Kernel
8.8. Dipendenze User Space nel Kernel
9. Fedora Desktop
10. Strumenti del server
10.1. system-config-printer
10.1.1. Esplorazione SMB fuori dalla rete locale
10.1.2. Supporto Kerberos per le stampanti SMB
10.2. system-config-securitylevel
10.2.1. Aggiunte ai servizi con fiducia
10.2.2. Insiemi di porte
11. File Servers
11.1. Informazioni generali
11.2. Netatalk (Compatibilità Macintosh)
12. Web Servers
12.1. httpd
12.2. php
12.3. Il framework PEAR
13. Strumenti di sviluppo
13.1. Collezione di compilatori GCC
13.1.1. Avvisi
13.1.2. Generazione del codice
13.1.3. Estensione linguaggi
13.2. FORTRAN
13.3. Ambiente di sviluppo Eclipse
14. Sicurezza
14.1. Novità
14.1.1. PAM module Deprecation
14.1.2. Determinazione dei buffer overflow e riordino delle variabili
14.2. SELinux
14.2.1. Multi Category Security (MCS)
14.2.2. Multilevel Security (MLS)
15. Java and java-gcj-compat
15.1. Gestire i pacchetti Java e Java-like
15.2. Fedora and the JPackage Java Packages
16. Samba (Windows Compatibility)
17. Multimedia
17.1. Lettori multimediali
17.2. I formati Ogg e Xiph.Org Foundation
17.3. MP3, DVD and Other Excluded Multimedia
17.4. Authoring e Masterizzazione di CD e DVD
17.5. Screencasts
17.6. Extended Support through Plugins
18. Giochi ed intrattenimento
19. Networking
19.1. Major Kernel Changes 2.6.11 - 2.6.15
19.1.1. Promozione indirizzo IPv4
19.1.2. Indirizzo sorgente configurabile per gli errori ICMP
19.1.3. LC-Trie Based Routing Lookup Algorithm
19.1.4. Pluggable Congestion Control Algorithm Infrastructure
19.1.5. Evitare l'accodamento per la perdita di linea
19.1.6. Supporto protocollo DCCP
19.1.7. Wireless
19.1.8. Miscellanea
19.2. User Tools
20. Virtualization
21. X Window System (Grafica)
21.1. xorg-x11
21.2. X.org X11R7 End-User Notes
21.3. X.org X11R7 Developer Overview
21.4. X.org X11R7 Developer Notes
21.4.1. The /usr/X11R6/ Directory Hierarchy
21.4.2. Imake
21.4.3. The Systemwide app-defaults/ Directory
21.4.4. Correct Package Dependencies
21.4.5. xft-config
22. Database Servers
22.1. MySQL
22.2. PostgreSQL
23. Internazionalizzazione (i18n)
23.1. Input Methods
23.1.1. Installation
23.1.2. SCIM applet and toolbar
23.1.3. SCIM configuration
23.1.4. New conversion engines
23.2. Fonts
23.3. gtk2 IM submenu
24. Compatibilità con il passato
25. Cambiamenti nei pacchetti
26. Fedora Extras - Community Package Repository
26.1. Using the Repository
26.2. About Fedora Extras
27. Fedora Legacy - Community Maintenance Project
28. Fedora Project - Freedom to the Core
29. Colophon
29.1. Informazioni sulla Colophon
29.2. Contributori
29.3. Production Methods

1. Benvenuti in Fedora Core

[Suggerimento] Ultime note di rilascio sul 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.

You can help the Fedora Project community continue to improve Fedora if you file bug reports and enhancement requests. Refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests for more information about bugs. Thank you for your participation.

To find out more general information about Fedora, refer to the following Web pages:

2. Panoramica di Fedora Core 5

You can find a tour filled with pictures and videos of this exciting new release at http://fedoraproject.org/wiki/Tours/FedoraCore5.

2.1. Cos'è cambiato da Fedora Core 4

This release is the culmination of nine months of development, and includes significant new versions of many key products and technologies. The following sections provide a brief overview of major changes from the last release of Fedora Core.

2.1.1. Desktop

Some of the highlights of this release include:

  • There is a completely revamped appearance with a bubbly new theme and the first use of the new Fedora logo.

  • Early work from the Fedora Rendering Project is integrated into the desktop. This new project (http://fedoraproject.org/wiki/RenderingProject) is going to provide the technical foundations for advanced desktop interfaces based on OpenGL.

  • Popular desktop environments GNOME and KDE have innovative new versions included in this release. The GNOME desktop is based on the 2.14 release (http://www.gnome.org/~davyd/gnome-2-14/), and the KDE 3.5 desktop is the general 3.5 release (http://kde.org/announcements/announce-3.5.php).

  • The latest versions of GNOME Power Manager (http://www.gnome.org/projects/gnome-power-manager/) and GNOME Screensaver(http://live.gnome.org/GnomeScreensaver/) provide new and integrated power management capabilities.

  • The new GNOME User Share facility provides simple and efficient file sharing.

  • Suspend to RAM support has also been improved due to infrastructure work done by the hibernate support.

  • The previous graphical software management utilities have been replaced with the first versions of a new generation of tools. This release includes Pup, a simple interface for system updates, and Pirut, a new package manager that replaces system-config-packages. These build on the yum utility, to provide consistent software installation and update facilities throughout the system.

  • This release of Fedora includes Mono support for the first time, and Mono applications such as Beagle, a desktop search interface; F-Spot, a photo management utility; and Tomboy, a note-taking application.

  • You can now enjoy enhanced multimedia support with version 0.10 of the Gstreamer media framework. This milestone release brings major improvements in robustness, compatibility, and features, over previous versions of Gstreamer. The Totem movie player and other media software in this release have been updated to use the new framework.

  • There is dramatically improved internationalization support with SCIM in Fedora Core 5. The SCIM language input framework provides an easy to use interface for inputting many different non-English languages. SCIM replaces the IIIMF system used in previous Fedora releases.

  • The default Web browser is Firefox 1.5 (http://www.mozilla.com/firefox/releases/1.5.html), which has many new features for faster, safer, and more efficient browsing.

  • The office applications suite OpenOffice.org 2.0 (http://www.openoffice.org/product/index.html) now makes better use of general system libraries for increased performance and efficiency.

  • A large number of GTK and GNOME programs take advantage of the Cairo 2D graphics library (http://cairographics.org/), included in this release, to provide streamlined attractive graphical interfaces.

  • There are new experimental drivers that provide support for the widely-used Broadcom 43xx wireless chipsets (http://bcm43xx.berlios.de/).

  • This release includes libnotify, a library that features simple and attractive notifications for the desktop.

  • Fedora Core 5 now uses gnome-mount, a more efficient mechanism that replaces fstab-sync, and uses HAL to handle mounting.

  • Printing support is improved in this release with the inclusion of the hplip utility, which replaces hpijs.

2.1.2. Amministrazione di sistema

Improvements for administrators and developers include:

  • The Xen virtualization system has enhanced support. The tools to configure Xen virtual machines on your Fedora Core 5 system now use the standard graphical installation process, run as a window on your desktop. Fedora developers have also created 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.

  • The industry-leading 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.

  • Version 2.2 of the Apache HTTP server is now included. This release provides enhancements to authentication, database support, proxy facilities, and content filtering.

  • The latest generation of database servers are packaged in this release, including both MySQL 5.0 and PostgreSQL 8.1.

  • Several native Java programs are now available compiled with GCJ, such as the Geronimo J2EE server and the Apache Jakarta Project, in addition to the Java programs and development capabilities in the previous releases.

  • There are new tools for system monitoring and performance analysis. This release includes SystemTap (http://fedoraproject.org/wiki/SystemTap), an instrumentation system for debugging and analyzing performance bottle necks, and Frysk (http://fedoraproject.org/wiki/Frysk), an execution analysis technology for monitoring running processes or threads.

  • This release includes system-config-cluster, a utility that allows you to manage cluster configuration in a graphical setting.

  • The combination of Kexec and Kdump utilities provides modern crash dumping facilities and potential for faster bootup, bypassing the firmware on reboots. Kexec loads a new kernel from a running kernel, and Kdump can provide a memory dump of the previous kernel for debugging.

  • This release includes iscsi-initiator-utils, iSCSI daemon and utility programs that provide support for hardware using the iSCSI interface.

2.1.3. Cambiamenti a livello di sistema

  • X.org X11R7.0 is included in this release. The new modular architecture of R7.0 enables easier driver upgrades and simplifies development, opening the way for rapid improvement in Linux graphics.

  • The GCC 4.1 compiler is included, and the entire set of Fedora packages is built with this technology. This provides security and performance enhancements throughout the system.

  • The kernels for this release are based on Linux 2.6.16. Refer to the section on the kernel in these release notes for other details.

  • The PCMCIA framework used by laptop and mobile devices has changed. The older 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.

  • SELinux implementation has undergone a major change, with a switch to the SELinux reference policy (http://serefpolicy.sourceforge.net/). The SELinux reference policy can support binary policy modules. It is now possible to move SELinux policies into individual packages, making it easier for users to ship site-specific policy customizations when required. This version also adds support for Multi-Category Security (MCS), enabled by default, and Multi-Level Security (MCS). SELinux continues to offer support for TE (Type Enforcement), enabled by default, and RBAC (Role-Based Access Control). Refer to the section on SELinux in these release notes for other details and links to SELinux resources on the Fedora Project pages.

2.2. Piano di sviluppo

The proposed plans for the next release of Fedora are available at http://fedoraproject.org/wiki/RoadMap.

3. Legal Notice

Copyright (c) 2006 by Red Hat, Inc. and others. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0, available at http://www.opencontent.org/openpub/.

Garrett LeSage created the admonition graphics (note, tip, important, caution, and warning). Tommy Reynolds created the callout graphics. They all may be freely redistributed with documentation produced for the Fedora Project.

FEDORA, FEDORA PROJECT, and the Fedora Logo are trademarks of Red Hat, Inc., are registered or pending registration in the U.S. and other countries, and are used here under license to the Fedora Project.

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.

Documentation, as with software itself, may be subject to export control. Read about Fedora Project export controls at http://fedoraproject.org/wiki/Legal/Export.

4. Providing Feedback for Release Notes

[Nota] Feedback for Release Notes Only

This section concerns feedback on the release notes themselves. To provide feedback on Fedora software or other system elements, please refer to http://fedoraproject.org/wiki/BugsAndFeatureRequests.

Thanks for your interest in giving feedback for these release notes. If you feel these release notes could be improved in any way, you can provide your feedback directly to the beat writers. Here are several ways to do so, in order of preference:

A release note beat is an area of the release notes that is the responsibility of one or more content contributors to oversee. For more ifnormation about beats, refer to http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Beats.

Grazie (in anticipo) per i tuoi suggerimenti!

5. Note relative all'installazione

This section outlines those issues that are related to Anaconda (the Fedora Core installation program) and installing Fedora Core 5 in general.

[Nota] Downloading Large Files

If you intend to download the Fedora Core 5 DVD ISO image, keep in mind that not all file downloading tools can accommodate files larger than 2GB in size. wget 1.9.1-16 and above, curl and ncftpget do not have this limitation, and can successfully download files larger than 2GB. BitTorrent is another method for downloading large files. For information about obtaining and using the torrent file, refer to http://torrent.fedoraproject.org/.

6. Architecture Specific Notes

Questa sezione fornisce note che sono specifiche all'architettura hardware supportata da Fedora Core.

6.1. Specifiche PPC per Fedora

Questa sezione copre ogni informazione specifica che potresti aver bisogno di conoscere, su Fedora Core e la piattaforma hardware PPC.

6.1.1. Requisiti hardware PPC

6.1.1.1. Processor and Memory
  • Minimum CPU: PowerPC G3 / POWER4

  • Fedora Core 5 supports only the “New World” generation of Apple Power Macintosh, shipped from circa 1999 onward.

  • Fedora Core 5 also supports IBM eServer pSeries, IBM RS/6000, Genesi Pegasos II, and IBM Cell Broadband Engine machines.

  • Recommended for text-mode: 233 MHz G3 or better, 128MiB RAM.

  • Recommended for graphical: 400 MHz G3 or better, 256MiB RAM.

6.1.1.2. Requisiti di spazio su disco

The disk space requirements listed below represent the disk space taken up by Fedora Core 5 after installation is complete. However, additional disk space is required during installation to support the installation environment. This additional disk space corresponds to the size of /Fedora/base/stage2.img (on Installtion Disc 1) plus the size of the files in /var/lib/rpm on the installed system.

In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.

Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation.

6.1.2. The Apple keyboard

The Option key on Apple systems is equivalent to the Alt key on the PC. Where documentation and the installer refer to the Alt key, use the Option key. For some key combinations you may need to use the Option key in conjunction with the Fn key, such as Option-Fn-F3 to switch to virtual terminal tty3.

6.1.3. Note di installazione PPC

Fedora Core Installation Disc 1 is bootable on supported hardware. In addition, a bootable CD image appears in the images/ directory of this disc. These images will behave differently according to your system hardware:

  • Apple Macintosh

    The bootloader should automatically boot the appropriate 32-bit or 64-bit installer.

    The default gnome-power-manager package includes power management support, including sleep and backlight level management. Users with more complex requirements can use the apmud package in Fedora Extras. Following installation, you can install apmud with the following command:

    su -c 'yum install apmud' 
  • 64-bit IBM eServer pSeries (POWER4/POWER5)

    Dopo aver usato OpenFirmware per avviare il CD, il bootloader (yaboot) avvierà automaticamente l'installer a 64-bit.

  • 32-bit CHRP (IBM RS/6000 ed altri)

    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 starts, which does not work.

  • Genesi Pegasos II

    At the time of writing, firmware with full support for ISO9660 file systems is not yet released for the Pegasos. However, you can use the network boot image. At the OpenFirmware prompt, enter the command:

    boot cd: /images/netboot/ppc32.img  

    You must also configure OpenFirmware on the Pegasos manually to make the installed Fedora Core system bootable. To do this, set the boot-device and boot-file environment variables appropriately.

  • Avvio dalla rete

    You can find combined images containing the installer kernel and ramdisk in the images/netboot/ directory of the installation tree. These are intended for network booting with TFTP, but can be used in many ways.

    yaboot supports TFTP booting for IBM eServer pSeries and Apple Macintosh. The Fedora Project encourages the use of yaboot over the netboot images.

6.2. Specifiche x86 per Fedora

Questa sezione copre ogni informazione specifica che potresti aver bisogno di conoscere, su Fedora Core e la piattaforma hardware x86.

6.2.1. Requisiti hardware x86

In order to use specific features of Fedora Core 5 during or after installation, you may need to know details of other hardware components such as video and network cards.

6.2.1.1. Processor and Memory Requirements

The following CPU specifications are stated in terms of Intel processors. Other processors, such as those from AMD, Cyrix, and VIA that are compatible with and equivalent to the following Intel processors, may also be used with Fedora Core.

  • Minimum: Pentium-class — Fedora Core 5 is optimized for Pentium 4 CPUs, but also supports earlier CPUs such as Pentium, Pentium Pro, Pentium II, Pentium III, and compatible AMD and VIA processors. Fedora takes this approach because Pentium-class optimizations actually result in reduced performance for non-Pentium class processors. In addition, scheduling for Pentium 4 processors, which make up the bulk of today's processors, is sufficiently different to warrant this change.

  • Raccomandato per la modalità testo: 200 MHz Pentium-class o superiore

  • Raccomandato per la modalità grafica: 400 MHz Pentium II o superiore

  • Processori AMD64 (sia Athlon64 che Opteron)

  • Processori Intel con Intel® Extended Memory 64 Technology (Intel® EM64T)

  • Minimum RAM for text-mode: 128MiB

  • Minimum RAM for graphical: 192MiB

  • Recommended for graphical: 256MiB

6.2.1.2. Requisiti di spazio su disco

The disk space requirements listed below represent the disk space taken up by Fedora Core 5 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 Installation Disc 1 plus the size of the files in /var/lib/rpm on the installed system.

In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.

Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation.

6.3. Specifiche x86_64 per Fedora

Questa sezione copre ogni informazione specifica che potresti aver bisogno di conoscere, su Fedora Core e la piattaforma hardware x86_64.

6.3.1. Requisiti hardware x86_64

In order to use specific features of Fedora Core 5 during or after installation, you may need to know details of other hardware components such as video and network cards.

6.3.1.1. Requisiti di memoria

Questo elenco è per i sistemi a 64-bit x86_64:

  • Minimum RAM for text-mode: 128MiB

  • Minimum RAM for graphical: 256MiB

  • Recommended RAM for graphical: 512MiB

6.3.1.2. Requisiti di spazio su disco

The disk space requirements listed below represent the disk space taken up by Fedora Core 5 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 Installation Disc 1 plus the size of the files in /var/lib/rpm on the installed system.

In practical terms, additional space requirements may range from as little as 90 MiB for a minimal installation to as much as an additional 175 MiB for an "everything" installation. The complete packages can occupy over 9 GB of disk space.

Additional space is also required for any user data, and at least 5% free space should be maintained for proper system operation.

6.3.2. RPM Multiarch Support on x86_64

RPM supports parallel installation of multiple architectures of the same package. A default package listing such as rpm -qa might appear to include duplicate packages, since the architecture is not displayed. Instead, use the repoquery command, part of the yum-utils package in Fedora Extras, which displays architecture by default. To install yum-utils, run the following command:

su -c 'yum install yum-utils' 

To list all packages with their architecture using rpm, run the following command:

rpm -qa --queryformat "%{name}-%{version}-%{release}.%{arch}\n"  

7. Note sui pacchetti

The following sections contain information regarding software packages that have undergone significant changes for Fedora Core 5. For easier access, they are generally organized using the same groups that are shown in the installation system.

7.1. Kernel device, module loading, and hotplug changes

The hotplug and device handling subsystem has undergone significant changes in Fedora Core 5. The udev method now handles all module loading, both on system boot and for hotplugged devices. The hotplug package has been removed, as it is no longer needed.

Support for hotplug helpers via the /etc/hotplug, /etc/hotplug.d, and /etc/dev.d directories is deprecated, and may be removed in a future Fedora Core release. These helpers should be converted to udev rules. Please see http://www.reactivated.net/writing_udev_rules.html for examples.

7.2. Cambiamenti nella ricerca sul sistema

[Nota] mlocate Has Replaced slocate

The new mlocate package provides the implementations of /usr/bin/locate and /usr/bin/updatedb. Previous Fedora releases included the slocate versions of these programs.

  • The locate command should be completely compatible.

  • The configuration file /etc/updatedb.conf is compatible.

  • Syntax errors that slocate would not detect are now reported.

  • The DAILY_UPDATE variable is not supported.

  • The updatedb command is not compatible, and custom scripts that use updatedb may have to be updated.

7.3. Rimozione dell'utilità di configurazione del mouse

The system-config-mouse configuration utility has been dropped in this release because synaptic and three-button mouse configuration is handled automatically. Serial mice are no longer supported.

7.4. NetworkManager

Fedora systems use NetworkManager to automatically detect, select, and configure wired and wireless network connections. Wireless network devices may require third-party software or manual configuration to activate after the installation process completes. For this reason, Fedora Core 5 provides NetworkManager as an optional component.

Refer to http://fedoraproject.org/wiki/Tools/NetworkManager for more information on how to install and enable NetworkManager.

7.5. Dovecot

Fedora Core 5 includes a new version of the dovecot IMAP server software, which has has many changes in its configuration file. These changes are of particular importance to users upgrading from a previous release. Refer to http://wiki.dovecot.org/UpgradingDovecot for more information on the changes.

7.6. Kudzu

The kudzu utility, libkudzu library, and /etc/sysconfig/hwconf hardware listing are all deprecated, and will be removed in a future release of Fedora Core. Applications which need to probe for available hardware should be ported to use the HAL library. More information on HAL is available at http://freedesktop.org/wiki/Software/hal.

7.7. No automatic fstab editing for removable media

The fstab-sync facility has been removed. In Fedora Core , the fstab-sync program is removed in favor of desktop specific solutions for mounting removable media. Entries for hotplug devices or inserted media are no longer automatically added to the /etc/fstab file. Command-line users may migrate to gnome-mount, which provides similar functionality.

7.8. GnuCash

The PostgreSQL backend for GnuCash has been removed, as it is unmaintained upstream, does not support the full set of GnuCash features, and can lead to crashes. Users who use the PostgreSQL backend should load their data and save it as an XML file before upgrading GnuCash.

7.9. Mozilla

The Mozilla application suite is deprecated. It is shipped in Fedora Core 5 and applications can expect to build against mozilla-devel, however it will be removed in a future release of Fedora Core.

7.10. libstc++ preview

The libstdc++so7 package has been added. This package contains a preview of the GNU Standard C++ Library from libstdcxx_so_7-branch. It is considered experimental and unsupported. Do not build any production software against it, as its ABI and so-version will change in future upgrades. To build software using this library, invoke g++-libstdc++so_7 instead of g++.

7.11. LinuxThreads support removed

The LinuxThreads library is no longer available. LinuxThreads was deprecated in Fedora Core 4 and is no longer available in this release. The Native POSIX Threading Library (NPTL), which has been the default threading library since Red Hat Linux 9, has replaced LinuxThreads completely.

8. Kernel Linux

This section covers changes and important information regarding the kernel in Fedora Core 5.

8.1. Versione

Questa distribuzione è basata sulla serie 2.6 del kernel di Linux. Fedora Core può includere patches aggiuntive per miglioramenti, correzione di errori, o caratteristiche aggiuntive. Per questa ragione, il kernel di Fedora Core potrebbe non essere linea-per-linea equivalente al cosidetto vanilla kernel proveniente dal sito web di kernel.org:

http://www.kernel.org/

To obtain a list of these patches, download the source RPM package and run the following command against it:

rpm -qpl kernel-<version>.src.rpm

8.2. Changelog

To retrieve a log of changes to the package, run the following command:

rpm -q --changelog kernel-<version>

If you need a user friendly version of the changelog, refer to http://wiki.kernelnewbies.org/LinuxChanges. A short and full diff of the kernel is available from http://kernel.org/git. The Fedora version kernel is based on the Linus tree.

Customizations made for the Fedora version are available from http://cvs.fedora.redhat.com .

8.3. Tipi di Kernel

Fedora Core 5 includes the following kernel builds:

  • Native kernel, in both uni-processor and SMP (Symmetric Multi-Processor) varieties. SMP kernels provide support for multiple CPUs. Configured sources are available in the kernel-[smp-]devel-<version>.<arch>.rpm package.

  • Virtual kernel hypervisor for use with the Xen emulator package. Configured sources are available in the kernel-xen0-devel-<version>.<arch>.rpm package.

  • Virtual kernel guest for use with the Xen emulator package. Configured sources are available in the kernel-xenU-devel-<version>.<arch>.rpm package.

  • Kdump kernel for use with kexec/kdump capabilities. Configured sources are available in the kernel-kdump-devel-<version>.<arch>.rpm package.

You may install sources for all kernel flavors at the same time. The files are installed in the /usr/src/kernels/<version>-[xen0|xenU|kdump]-<arch>/ tree. Use the following command:

su -c 'yum install kernel-{xen0,xenU,kdump}-devel'

Select one or more of these flavors, separated by commas and no spaces, as appropriate. Enter the root password when prompted.

[Nota] x86_64 Default Kernel Provides SMP

There is no separate SMP kernel available for the x86_64 architecture in Fedora Core 5.

[Nota] PowerPC Kernel Support

There is no support for Xen or kdump for the PowerPC architecture in Fedora Core 5.

8.4. Reporting Bugs

Refer to http://kernel.org/pub/linux/docs/lkml/reporting-bugs.html for information on reporting bugs in the Linux kernel. You may also use http://bugzilla.redhat.com for reporting bugs which are specific to Fedora.

8.5. Seguire libri di testo generici

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 run the following command:

su -c 'ln -s /usr/src/kernels/kernel-<all-the-rest> /usr/src/linux'

Enter the root password when prompted.

8.6. Preparazione allo sviluppo del Kernel

Fedora Core 5 does not include the kernel-source package provided by older versions. Instead, configured sources are available, as described in this kernel flavors section.

[Nota] Instructions Refer to Current Kernel

To simplify the following directions, we have assumed that you want to configure the kernel sources to match your currently-running kernel. In the steps below, the expression <version> refers to the kernel version shown by the command: uname -r.

Users who require access to Fedora Core original kernel sources can find them in the kernel .src.rpm package. To create an exploded source tree from this file, perform the following steps:

[Attenzione] Do Not Build Packages as Super-user

Building packages as the superuser is inherently dangerous and is not required, even for the kernel. These instructions allow you to install the kernel source as a normal user. Many general information sites refer to /usr/src/linux in their kernel instructions. If you use these instructions, simply substitute ~/rpmbuild/BUILD/kernel-<version>/linux-<version>.

  1. Prepare a RPM package building environment in your home directory. Run the following commands:

    su -c 'yum install fedora-rpmdevtools'
    fedora-buildrpmtree

    Enter the root password when prompted.

  2. Obtain the kernel-<version>.src.rpm file from one of the following sources:

    • the SRPMS directory on the appropriate SRPMS CD iso image

    • the HTTP or FTP site where you got the kernel package

    • by running the following command:

      su -c 'yum install yum-utils'
      su -c 'yumdownloader --source kernel'

      Enter the root password when prompted.

  3. Install kernel-<version>.src.rpm using the command:

    rpm -Uvh kernel-<version>.src.rpm`

    This command writes the RPM contents into ${HOME}/rpmbuild/SOURCES and ${HOME}/rpmbuild/SPECS, where ${HOME} is your home directory.

    [Suggerimento] Space Required

    The full kernel building process may require several gigabytes of extra space on the file system containing your home directory.

  4. Prepare the kernel sources using the commands:

    cd ~/rpmbuild/SPECS
    rpmbuild -bp --target $(uname -m) kernel-2.6.spec

    The kernel source tree is located in the ${HOME}/rpmbuild/BUILD/kernel-<version>/ directory.

  5. The configurations for the specific kernels shipped in Fedora Core 5 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.

  6. Every kernel gets a name based on its version number. This is the value the uname -r command displays. The kernel name is defined by the first four lines of the kernel Makefile. The Makefile has been changed to generate a kernel with a different name from that of the running kernel. To be accepted by the running kernel, a module must be compiled for a kernel with the correct name. To do this, you must edit the kernel Makefile.

    For example, if the uname -r returns the string 2.6.15-1.1948_FC5, change the EXTRAVERSION definition from this:

    EXTRAVERSION = -prep

    a questo:

    EXTRAVERSION = -1.1948_FC5

    That is, substitute everything from the final dash onward.

  7. Run the following command:

    make oldconfig

    You may then proceed as usual.

8.7. Compilare solo i moduli del Kernel

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)

default:
    $(MAKE) -C $(KDIR) M=$(PWD) modules
      

Issue the make command to build the foo.ko module.

8.8. Dipendenze User Space nel Kernel

Fedora Core 5 has support for clustered storage through the Global File System (GFS). GFS requires special kernel modules that work in conjunction with some user-space utilities, such as management daemons. To remove such a kernel, perhaps after an update, use the su -c 'yum remove kernel-<version>' command instead. The yum command automatically removes dependent packages, if necessary.

[Nota] PowerPC does not support GFS

The GFS kernel modules are not built for the PowerPC architecture in Fedora Core 5.

9. Fedora Desktop

GNOME 2.14 (or a release candidate) and KDE 3.5.1 are included in Fedora Core 5. The following list includes notable changes to the desktop interface in this release.

  • gnome-power-manager

    • The GNOME Power Manager is a session daemon for the GNOME desktop environment that makes it easy to manage your laptop or desktop system. It takes advantage of HAL (which provides a hardware abstraction layer) and DBUS (Inter Process Communication software) written and maintained by Fedora Core developers.

  • gnome-screensaver

    • The GNOME Screensaver provides an integrated user interface to screensavers and the lock screen dialog.

  • Memory optimizations in the fontconfig and shared-mime-info packages. These now use shared memory-mapped caches for this data.

  • Starting with GNOME 2.12, the terminal option has been removed from the desktop context menu. The nautilus-open-terminal package in Fedora Extras provides a enhanced replacement for those who require it. You can install it with the following command.

    su -c 'yum install nautilus-open-terminal'
  • In Fedora Core 5, only a small assortment of screensavers is installed by default. Some users find certain screensavers unpleasant, and other screensavers may abruptly terminate the graphical interface. This tends to happen more often with OpenGL animated screensavers provided within the xscreensaver-gl-extras package, when used with poorly-supported video hardware. To install these extra screensavers, run the following command:

    su -c 'yum install xscreensaver-extras xscreensaver-gl-extras'

10. Strumenti del server

Questa sezione elenca i cambiamenti e le aggiunte alle varie GUI server e strumenti di configurazione del sistema in Fedora Core.

10.1. system-config-printer

10.1.1. Esplorazione SMB fuori dalla rete locale

You can now browse for Samba print shares across subnets. If you specify at least one WINS server in /etc/samba/smb.conf, the first address is used when browsing.

10.1.2. Supporto Kerberos per le stampanti SMB

The system-config-printer application supports Kerberos authentication when adding a new SMB printer. To add the printer, the user must possess a valid Kerberos ticket and launch the printer configuration tool. Select System>Administration>Printing from the main menu, or use the following command:

su -c 'system-config-printer' 

No username and password is stored in /etc/cups/printers.conf. Printing is still possible if the SMB print queue permits anonymous printing.

10.2. system-config-securitylevel

10.2.1. Aggiunte ai servizi con fiducia

Samba is now listed in the Trusted services list. To permit the firewall to pass SMB traffic, enable this option.

10.2.2. Insiemi di porte

When you define Other Ports in the system-config-securitylevel tool, you may now specify port ranges. For example, if you specify 6881-6999:tcp, the following line is added to /etc/sysconfig/iptables:

A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 6881:6999 -j ACCEPT 

11. File Servers

11.1. Informazioni generali

This section refers to file transfer and sharing servers. Refer to http://fedoraproject.org/wiki/Docs/Beats/WebServers and http://fedoraproject.org/wiki/Docs/Beats/Samba for information on HTTP (Web) file transfer and Samba (Windows) file sharing services.

11.2. Netatalk (Compatibilità Macintosh)

Fedora includes version 2 of Netatalk, a suite of software that enables Linux to interact with Macintosh systems using the AppleTalk network protocols.

[Attenzione] Use Caution When Upgrading

You may experience data loss when upgrading from Netatalk version 1 to version 2.

Version 2 of Netatalk stores file resource forks using a different method from the previous version, and may require a different file name encoding scheme. Please read the documentation and plan your migration before upgrading. Refer to the upgrade information available directly from the Netatalk site at http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html.

The documentation is also included in the netatalk package. Refer to either /usr/share/doc/netatalk-2.0.2/doc/htmldocs/upgrade.html or /usr/share/doc/netatalk-2.0.2/doc/Netatalk-Manual.pdf (numbered page 25, document page 33).

12. Web Servers

Questa sezione contiene informazioni sulle applicazioni Web.

12.1. httpd

Fedora Core now includes version 2.2 of the Apache HTTP Server. This release brings a number of improvements over the 2.0 series, including:

  • greatly improved caching modules (mod_cache, mod_disk_cache, mod_mem_cache)

  • a new structure for authentication and authorization support, replacing the security modules provided in previous versions

  • support for proxy load balancing (mod_proxy_balance)

  • large file support for 32-bit platforms (including support for serving files larger than 2GB)

  • new modules mod_dbd and mod_filter, which bring SQL database support and enhanced filtering

    [Importante] Upgrading and Security Modules

    If you upgrade from a previous version of httpd, update your server configuration to use the new authentication and authorization modules. Refer to the page listed below for more details.

The following changes have been made to the default httpd configuration:

  • The mod_cern_meta and mod_asis modules are no longer loaded by default.

  • The mod_ext_filter module is now loaded by default.

    [Importante] Third-party Modules

    Any third-party modules compiled for httpd 2.0 must be rebuilt for httpd 2.2.

For more information on upgrading existing installations, refer to http://httpd.apache.org/docs/2.2/upgrading.html.

12.2. php

La versione 5.1 di PHP è ora inclusa in Fedora Core. Questa versione porta un certo numero di migliorie rispetto a PHP 5.0, incluse:

  • migliorate prestazioni

  • aggiunta del modulo di astrazione database PDO

Sono stati aggiunti i seguenti moduli di estensione:

  • date, hash, and Reflection (built-in with the php package)

  • pdo and pdo_psqlite (in the php-pdo package)

  • pdo_mysql (in the php-mysql package)

  • pdo_pgsql (in the php-pgsql package)

  • pdo_odbc (in the php-odbc package)

  • xmlreader and xmlwriter (in the php-xml package)

I seguenti moduli di estensione non sono più compilati:

  • dbx

  • dio

  • yp

12.3. Il framework PEAR

The PEAR framework is now packaged in the php-pear package. Only the following PEAR components are included in Fedora Core:

  • Archive_Tar

  • Console_Getopt

  • XML_RPC

Additional components may be packaged in Fedora Extras.

13. Strumenti di sviluppo

Questa sezione riguarda vari strumenti di sviluppo.

13.1. Collezione di compilatori GCC

This release of Fedora has been built with GCC 4.1 as the system compiler, which is included with the distribution.

13.1.1. Avvisi

  • You need GDB 6.1 or newer to debug binaries, unless they are compiled using the -fno-var-tracking compilation option.

  • The -fwritable-strings option is no longer accepted.

  • English-language diagnostic messages now use Unicode quotes. If you cannot read this, set your LC_CTYPE environment variable to C or change your terminal emulator.

  • The specs file is no longer installed on most systems. Ordinary users will not notice, but developers who need to alter the file can use the -dumpspecs option to generate the file for editing.

13.1.2. Generazione del codice

  • L'ottimizzatore di codice SSA è ora incluso e porta con se una migliore costante propagazione, parziale eliminazione della ridondanza, load e store code motion, riduzione della forza, eliminazione del dead storage, miglior individuazione del codice irraggiungibile, e ricorsività delle code per cumulazione.

  • L'autovettorizazione è supportata. Questa tecnica ottiene più alte prestazioni per cicli repetitivi di codice, in alcune circostanze.

13.1.3. Estensione linguaggi

  • The new sentinel attribute causes the compiler to issue a warning if a function such as execl(char *path, const char *arg, ...), which requires a NULL list terminator, is missing the NULL.

  • The cast-as-lvalue, conditional-expression-as-lvalue, and compund-expression-as-lvalue extensions have been removed.

  • The #pragma pack() semantics are now closer to those used by other compilers.

  • Ricavare l'indirizzo di una variabile dichiarata con il modificatore register ora genera un errore invece di un avvertimento.

  • Arrays di tipi di elementi incompleti ora generano un errore. Ciò implica nessun trasferimento di referenza alle definizioni di struttura.

  • The basic compiler, without any optimization (-O0), has been measured as much as 25% faster in real-world code.

  • Libraries may now contain function-scope static variables in multi-threaded programs. Embedded developers can use the -fno-threadsafe-statics to turn off this feature, but ordinary users should never do this.

13.2. FORTRAN

  • Il front end allo GNU FORTRAN 77 è stato sostituito da un nuovo FORTRAN 90/95 recognizer.

13.3. Ambiente di sviluppo Eclipse

  • Eclipse 3.1M6 is compiled as a native application.

  • Il C Development Tool (CDT) è stato incluso.

14. Sicurezza

Questa sezione evidenzia varie questioni di sicurezza da Fedora Core.

A general introduction to the many proactive security features in Fedora, current status and policies is available at http://fedoraproject.org/wiki/Security.

14.1. Novità

14.1.1. PAM module Deprecation

Pam_stack is deprecated in this release. Linux-PAM 0.78 and later contains the include directive which obsoletes the pam_stack module. pam_stack module usage is logged with a deprecation warning. It might be removed in a future release. It must not be used in individual service configurations anymore. All packages in Fedora Core using PAM were modified so they do not use it.

[Suggerimento] Upgrading and PAM Stacks

When a system is upgraded from previous Fedora Core releases and the system admininstrator previously modified some service configurations, those modified configuration files are not replaced when new packages are installed. Instead, the new configuration files are created as .rpmnew files. Such service configurations must be fixed so the pam_stack module is not used. Refer to the .rpmnew files for the actual changes needed.

diff -u /etc/pam.d/foo /etc/pam.d/foo.rpmnew

The following example shows the /etc/pam.d/login configuration file in its original form using pam_stack, and then revised with the include directive.

#%PAM-1.0
auth       required     pam_securetty.so
auth       required     pam_stack.so service=system-auth
auth       required     pam_nologin.so
account    required     pam_stack.so service=system-auth
password   required     pam_stack.so service=system-auth
# pam_selinux.so close should be the first session rule
session    required     pam_selinux.so close
session    required     pam_stack.so service=system-auth
session    required     pam_loginuid.so
session    optional     pam_console.so
# pam_selinux.so open should be the last session rule
session    required     pam_selinux.so open
	
#%PAM-1.0
auth       required     pam_securetty.so
auth       include      system-auth
# no module should remain after 'include' if 'sufficient' might
# be used in the included configuration file
# pam_nologin moved to account phase - it's more appropriate there
# other modules might be moved before the system-auth 'include'
account    required     pam_nologin.so
account    include      system-auth
password   include      system-auth
# pam_selinux.so close should be the first session rule
session    required     pam_selinux.so close
session    include      system-auth
# the system-auth config doesn't contain sufficient modules
# in the session phase
session    required     pam_loginuid.so
session    optional     pam_console.so
# pam_selinux.so open should be the last session rule
session    required     pam_selinux.so open
	

14.1.2. Determinazione dei buffer overflow e riordino delle variabili

All of the software in Fedora Core and Extras software repository for this release is compiled using a security feature called fstack-protector. fstack-protector places a canary value on the stack of functions containing a local character array. Before returning from a protected function, the canary value is verified. If there was a buffer overflow, the canary will no longer match the expected value, aborting the program. The canary value is random each time the application is started, making remote exploitation very difficult. The fstack-protector feature does not protect against heap-based buffer overflows.

This is a security feature written by Red Hat developers, implementing the IBM ProPolice/SSP feature. For more information about ProPolice/SSP, refer to http://www.research.ibm.com/trl/projects/security/ssp/. This feature is available as part of the GCC 4.1 compiler used in Fedora Core 5.

The FORTIFY_SOURCE security feature for gcc and glibc introduced in Fedora Core 4 remains available. For more information about security features in Fedora, refer to http://fedoraproject.org/wiki/Security/Features.

14.2. SELinux

The new SELinux project pages have troubleshooting tips, explanations, and pointers to documentation and references. Some useful links include the following:

14.2.1. Multi Category Security (MCS)

MCS is a general-use implementation of the more stringent Multilevel Security (MLS). MCS is an enhancement to SELinux to allow users to label files with categories. Categories might include Company_Confidential, CEO_EYES_ONLY, or Sysadmin_Passwords. For more information about MCS, refer to http://james-morris.livejournal.com/5583.html, an article by the author.

14.2.2. Multilevel Security (MLS)

MLS is a specific Mandatory Access Control (MAC) scheme that labels processes and objects with special security levels. For example, an object such as a document file can have the security level of { Secret, ProjectMeta }, where Secret is the sensitivity level, and ProjectMeta is the category. For more information about MLS, refer to http://james-morris.livejournal.com/5020.html.

CategorySecurity

15. Java and java-gcj-compat

A free and open source Java environment is available within this Fedora Core release, called java-gcj-compat. java-gcj-compat includes a tool suite and execution environment that is capable of building and running many useful programs that are written in the Java programming language.

[Nota] Fedora Core Does Not Include Java

Java is a trademark of Sun Microsystems. java-gcj-compat is an entirely free software stack that is not Java, but may run Java software.

The java-gcj-compat infrastructure has three key components: a GNU Java runtime (libgcj), the Eclipse Java compiler (ecj), and a set of wrappers and links (java-gcj-compat) that present the runtime and compiler to the user in a manner similar to other Java environments.

The Java software packages included in this Fedora release use the new, integrated java-gcj-compat environment. These packages include OpenOffice.org Base, Eclipse, and Apache Tomcat.

Refer to the Java FAQ at http://www.fedoraproject.org/wiki/JavaFAQ for more information on the free Java environment in Fedora.

[Suggerimento] Include location and version information in bug reports

Quando crei una segnalazione d'errore, sii sicuro di includere l'output di questi comandi:

which java && java -version && which javac && javac -version

15.1. Gestire i pacchetti Java e Java-like

In addition to the java-gcj-compat free software stack, Fedora Core is designed to let you install multiple Java implementations and switch between them using the alternatives command line tool. However, every Java system you install must be packaged using the JPackage Project packaging guidelines to take advantage of alternatives.

Once installed properly, the root user should be able to switch between java and javac implementations using the alternatives command:

alternatives --config java alternatives --config javac

15.2. Fedora and the JPackage Java Packages

Fedora Core includes many packages derived from the JPackage Project, which provides a Java software repository. These packages have been modified in Fedora to remove proprietary software dependencies and to make use of GCJ's ahead-of-time compilation feature. Fedora users should use the Fedora repositories for updates to these packages, and may use the JPackage repository for packages not provided by Fedora.

Refer to the JPackage website at http://jpackage.org for more information on the project and the software that it provides.

[Avvertimento] Mixing Packages from Fedora and JPackage

Research package compatibility before you install software from both the Fedora and JPackage repositories on the same system. Incompatible packages may cause complex issues.

16. Samba (Windows Compatibility)

Fedora can now browse Windows shares, a feature known as SMB browsing. In releases prior to Fedora Core 5, the firewall prevented the proper function of SMB browsing. With the addition of the ip_conntrack_netbios_ns kernel module to the 2.6.14 kernel, and corresponding enhancements to system-config-securitylevel, the firewall now properly handles SMB broadcasts and permits network browsing.

17. Multimedia

Fedora Core include applicazioni per funzioni multimediali assortite, incluso ascolto, registrazione, ed editing. Pacchetti aggiuntivi sono disponibili attraverso il repositorio Fedora Extras.

17.1. Lettori multimediali

The default installation of Fedora Core includes Rhythmbox, Totem, and Helix Player for media playback. Many other programs are available in the Fedora Core and Fedora Extras repositories, including the popular XMMS package. Both GNOME and KDE have a selection of players that can be used with a variety of formats. Additional programs are available from third parties to handle other formats.

Fedora Core also takes full advantage of the Advanced Linux Sound Architecture (ALSA) sound system. 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 limitation disappears. For more information about ALSA, visit the project website at http://www.alsa-project.org/.

17.2. I formati Ogg e Xiph.Org Foundation

Fedora includes complete support for the Ogg media container format, and the Vorbis audio, Theora video, Speex audio, and FLAC lossless audio formats. These freely-distributable formats are not encumbered by patent or license restrictions. They provide powerful and flexible alternatives to more popular, restricted formats. The Fedora Project encourages the use of open source formats in place of restricted ones. For more information on these formats and how to use them, refer to the Xiph.Org Foundation's web site at http://www.xiph.org/.

17.3. MP3, DVD and Other Excluded Multimedia

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. Fedora also excludes several multimedia application programs due to patent or license restrictions, such as Flash Player and Real Player. For more on this subject, please refer to http://fedoraproject.org/wiki/ForbiddenItems.

17.4. Authoring e Masterizzazione di CD e DVD

Fedora Core and Extras include a variety of tools for easily mastering and burning CDs and DVDs. GNOME users can burn directly from the Nautilus file manager, or choose the gnomebaker or graveman packages from Fedora Extras, or the older xcdroast package from Fedora Core. KDE users can use the robust k3b package for these tasks. Console tools include cdrecord, readcd, mkisofs, and other typical Linux applications.

17.5. Screencasts

You can use Fedora to create and play back screencasts, which are recorded desktop sessions, using open technologies. Fedora Extras 5 includes istanbul, which creates screencasts using the Theora video format. These videos can be played back using one of several players included in Fedora Core. This is the preferred way to submit screencasts to the Fedora Project for either developer or end-user use. For a more comprehensive how-to, refer to http://fedoraproject.org/wiki/ScreenCasting.

17.6. Extended Support through Plugins

Most of the media players in Fedora Core and Fedora Extras support the use of plugins to add support for additional media formats and sound output systems. Some use powerful backends, like gstreamer, to handle media format support and sound output. Plugin packages for these backends and for individual applications are available in Fedora Core and Fedora Extras, and additional plugins may be available from third parties to add even greater capabilities.

18. Giochi ed intrattenimento

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). To install other games available from Fedora Core and Fedora Extras, select Applications>Add/Remove Software from the main desktop menu.

19. Networking

19.1. Major Kernel Changes 2.6.11 - 2.6.15

Refer to http://wiki.kernelnewbies.org/LinuxChanges for a list of major changes. Some of them are highlighted below.

19.1.1. Promozione indirizzo IPv4

Starting with version 2.6.12 of the kernel, a new feature has been added called named address promotion. This feature allows secondary IPv4 addresses to be promoted to primary addresses. Usually when the primary address is deleted, all secondary addresses are deleted as well. If you enable the new sysctl key net.ipv4.conf.all.promote_secondaries, or one of the interface specific variants, you can change this behavior to promote one of the secondary addresses to be the new primary address.

19.1.2. Indirizzo sorgente configurabile per gli errori ICMP

By default, when selecting the source address for ICMP error messages, the kernel uses the address of the interface on which the ICMP error is going to be sent. Kernel version 2.6.12 introduces the new sysctl key net.ipv4.icmp_errors_use_inbound_ifaddr. If you enable this option the kernel uses the address of the interface that received the original error-causing packet.

Suppose the kernel receives a packet on interface eth0 which generates an ICMP error, and the routing table causes the error message to be generated on interface eth1. If the new sysctl option is enabled, the ICMP error message indicates the source address as interface eth0, instead of the default eth1. This feature may ease network debugging in asynchronous routing setups.

19.1.3. LC-Trie Based Routing Lookup Algorithm

A new routing lookup algorithm called trie has been added. It is intended for large routing tables and shows a clear performance improvement over the original hash implementation, at the cost of increased memory consumption and complexity.

19.1.4. Pluggable Congestion Control Algorithm Infrastructure

TCP congestion control algorithms are now pluggable and thus modular. The legacy NewReno algorithm remains the default, and acts as the fallback algorithm. The following new congestion control algorithms have been added:

  • High Speed TCP congestion control

  • TCP Hybla congestion avoidance

  • H-TCP congestion control

  • Scalable TCP congestion control

All existing congestion control modules have been converted to this new infrastructure, and the BIC congestion control has received enhancements from BICTCP 1.1 to handle low latency links.

[Nota] Cose pertinenti l'algoritmo di controllo di congestione

The congestion control algorithm is socket specific, and may be changed via the socket option TCP_CONGESTION.

19.1.5. Evitare l'accodamento per la perdita di linea

When a network driver notices a carrier loss, such as when the cable is pulled out, the driver stops the queue in front of the driver. In the past, this stoppage caused the packets to be queued at the queueing discipline layer for an unbound period of time causing unexpected effects. In order to prevent this effect, the core networking stack now refuses to queue any packets for a device that is operationally down, that is, has its queue disabled.

19.1.6. Supporto protocollo DCCP

Kernel version 2.6.14-rc1 was the first version to receive support for the DCCP protocol. The implementation is still experimental, but is known to work. Developers have begun work to make userspace applications aware of this new protocol.

19.1.7. Wireless

A new HostAP driver appears in the kernel starting in 2.6.14-rc1, which allows the emulation of a wireless access point through software. Currently this driver only works for Intersil Prism2-based cards (PC Card/PCI/PLX). Support for wireless cards Intel(R) PRO/Wireless 2100 and 2200 has been added.

19.1.8. Miscellanea

  • Many TCP Segmentation Offloading (TSO) related fixes are included.

  • A new textsearch infrastructure has been added, and is usable with corresponding iptables and extended match.

  • Entrambe le interfacce multicast join IPv4 ed IPv6 visibili in userspace sono state ristrutturate e portate agli ultimi standards.

  • The SNMPv2 MIB counter ipInAddrErrors is supported for IPv4.

  • Sono state aggiunte nuove varie opzioni socket, proposte in Advanced API (RFC3542).

19.2. User Tools

The IPv4 address deletion algorithm did not take the prefix length into account up to kernel version 2.6.12. Since this has changed, the iproute2 tool now issues a warning if no prefix length is provided, to warn about possible unintended deletions:

ip addr list dev eth0 
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    inet 10.0.0.3/24 scope global eth0
	
su -c 'ip addr del 10.0.0.3 dev eth0' 
Warning: Executing wildcard deletion to stay compatible with old
      scripts. Explicitly specify the prefix length (10.0.0.3/32) to
      avoid this warning. This special behaviour is likely to disappear
      in further releases, fix your scripts!
      

Il metodo corretto di cancellare l'indirizzo evitando l'avvertimento è:

su -c 'ip addr del 10.0.0.3/24 dev eth0'

Previously, it was not possible to tell if an interface was down administratively or because no carrier was found, such as if a cable were unplugged. The new flag NO-CARRIER now appears as a link flag if the link is administratively up but no carrier can be found.

The ip command now supports a batch mode via the argument -batch, which works similar to the tc command to speed up batches of tasks.

20. Virtualization

Virtualization in Fedora Core is based on Xen. Xen 3.0 is integrated within Fedora Core 5 in the installer. Refer to http://fedoraproject.org/wiki/Tools/Xen for more information about Xen.

[Nota] No PowerPC Support

Xen is not supported on the PowerPC architecture in Fedora Core 5.

21. X Window System (Grafica)

Questa sezione contiene le informazioni relative all'implementazione del sistema X Window distribuito con Fedora.

21.1. xorg-x11

X.org X11 is an open source implementation of the X Window System. It provides the basic low-level functionality upon which full-fledged graphical user interfaces (GUIs) such as GNOME and KDE are designed. For more information about X.org, refer to http://xorg.freedesktop.org/wiki/.

You may use Applications > System Settings > Display or system-config-display to configure the settings. The configuration file for X.org is located in /etc/X11/xorg.conf.

X.org X11R7 is the first modular release of X.org, which, among several other benefits, promotes faster updates and helps programmers rapidly develop and release specific components. More information on the current status of the X.org modularization effort in Fedora is available at http://fedoraproject.org/wiki/Xorg/Modularization.

21.2. X.org X11R7 End-User Notes

[Attenzione] Installing Third Party Drivers

Before you install any third party drivers from any vendor, including ATI or nVidia, please read http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers.

The xorg-x11-server-Xorg package install scripts automatically remove the RgbPath line from the xorg.conf file if it is present. You may need to reconfigure your keyboard differently from what you are used to. You are encouraged to subscribe to the upstream xorg@freedesktop.org mailing list if you do need assistance reconfiguring your keyboard.

21.3. X.org X11R7 Developer Overview

The following list includes some of the more visible changes for developers in X11R7:

  • The entire buildsystem has changed from imake to the GNU autotools collection.

  • 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. Developers are strongly advised against hard-coding the new X11R7 default paths.

  • Every library has its own private source RPM package, which creates a runtime binary subpackage and a -devel subpackage.

21.4. X.org X11R7 Developer Notes

This section includes a summary of issues of note for developers and packagers, and suggestions on how to fix them where possible.

21.4.1. The /usr/X11R6/ Directory Hierarchy

X11R7 files install into /usr directly now, and no longer use the /usr/X11R6/ hierarchy. Applications that rely on files being present at fixed paths under /usr/X11R6/, either at compile time or run time, must be updated. They should now 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.

21.4.2. Imake

The imake utility is no longer used to build the X Window System, and is now officially deprecated. X11R7 includes imake, xmkmf, and other build utilities previously supplied by the X Window System. X.Org highly recommends, however, that people migrate from imake to use GNU autotools and pkg-config. Support for imake may be removed in a future X Window System release, so developers are strongly encouraged to transition away from it, and not use it for any new software projects.

21.4.3. The Systemwide app-defaults/ Directory

The system app-defaults/ directory for X resources is now %{_datadir}/X11/app-defaults, which expands to /usr/share/X11/app-defaults/ on Fedora Core 5 and for future Red Hat Enterprise Linux systems.

21.4.4. Correct Package Dependencies

Any software package that previously used BuildRequires: (XFree86-devel|xorg-x11-devel) to satisfy build dependencies must now individually list each library dependency. The preferred and recommended method is to use virtual build dependencies instead of hard coding the library package names of the xorg implementation. This means you should use BuildRequires: libXft-devel instead of 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 or safe way to state the dependency, then use the xorg-x11-devel form. If you use the virtual provides/requires mechanism, you will avoid inconvenience if the libraries move to another location in the future.

21.4.5. xft-config

Modular X now uses GNU autotools and pkg-config for its buildsystem configuration and execution. The xft-config utility has been deprecated for some time, and pkgconfig*.pc files have been provided for most of this time. Applications that previously used xft-config to obtain the Cflags or libs build options must now be updated to use pkg-config.

22. Database Servers

22.1. MySQL

Fedora now provides MySQL 5.0. For a list of the enhancements provided by this version, refer to http://dev.mysql.com/doc/refman/5.0/en/mysql-5-0-nutshell.html.

For more information on upgrading databases from previous releases of MySQL, refer to the MySQL web site at http://dev.mysql.com/doc/refman/5.0/en/upgrade.html.

22.2. PostgreSQL

This release of Fedora includes PostgreSQL 8.1. For more information on this new version, refer to http://www.postgresql.org/docs/whatsnew/.

[Importante] Database Upgrade Across Fedora Core Versions

Fedora Core 4 provided version 8.0 of PostgreSQL. If you upgrade an existing Fedora system with a PostgreSQL database, you must upgrade the database to access the data.

To upgrade a database from a previous version of PostgreSQL, follow the procedure described at http://www.postgresql.org/docs/8.1/interactive/install-upgrading.html.

23. Internazionalizzazione (i18n)

This section includes information related to the support of various languages under Fedora Core.

23.1. Input Methods

SCIM (Simple Common Input Method) has replaced IIIMF as the input method system for Asian and other languages in Fedora Core in this release. SCIM uses Ctrl-Space as the default trigger key to toggle on and off the input method, though it is easy to change the hotkey or add hotkeys with the SCIM setup configuration tool. When scim-anthy is active Japanese users can now use the Zenkaku_Hankaku key to toggle between Japanese and ASCII input.

23.1.1. Installation

SCIM should be installed and run by default for Asian language desktops. Otherwise the required packages can be installed using the language support section of the package manager or running:

su -c 'yum install <SCIM-IMEs>' 

where <SCIM-IMEs> should be replaced by one or more of the following:

  • Japanese: scim-anthy

    Korean: scim-hangul

    Simplified Chinese: scim-pinyin scim-tables-chinese

    Traditional Chinese: scim-chewing scim-tables-chinese

    Indian and other languages: scim-m17n m17n-db-<language>

You also need fonts for the language. The font packages are named fonts-<language>, where <language> is one of arabic, bengali, chinese, gujarati, hebrew, hindi, japanese, korean, punjabi, tamil.

If your desktop is not running in an Asian locale, to activate it in your user account, run these commands, then logout and login again to your desktop.

mkdir ~/.xinput.d 
ln -s /etc/X11/xinit/xinput.d/scim ~/.xinput.d/default

23.1.2. SCIM applet and toolbar

When SCIM is running, an applet icon appears in the notification area of the desktop panel. The icon is a grey keyboard icon when SCIM is inactive, and an Input Method Engine (IME) icon when it is acti