feature in Red Hat Enterprise Linux 5.3. It enables the iwlwifi 4965GN wireless driver for
Intel® WiFi Link 4965 hardware which allows certain wireless devices to connect to any WiFi
network.
Although the mac80211 component is supported in Red Hat Enterprise Linux 5.3, the symbols
are not included in the symbol whitelist for the kernel.
Global File Syst em 2 (GFS2)
GFS2 is an incremental advancement of GFS. This update applies several significant
improvements that require a change to the on-disk file system format. GFS file systems can be
converted to GFS2 using the utility gfs2_convert, which updates the metadata of a GFS file
system accordingly.
In Red Hat Enterprise Linux 5.2, GFS2 was provided as a kernel module for evaluation
purposes. In Red Hat Enterprise Linux 5.3, GFS2 is now part of the kernel package. If the Red
Hat Enterprise Linux 5.2 GFS2 kernel modules have been installed they must be removed to
use GFS2 in Red Hat Enterprise Linux 5.3.
Improvements in Driver Disk Support
A driver disk, supplied by an OEM, is a single image file (* .img), containing potentially multiple
driver RPMs and kernel modules. These drivers are used during installation to support
hardware that otherwise would not be recognized. The RPMs are installed on the system and
placed into the initrd so that they are supported when the machine reboots.
With Red Hat Enterprise Linux 5.3, installation can automatically detect the presence of a driver
disk based on its file system label, and use the content of that disk during installation. T his
behavior is controlled by the installation command line option dlabel=on, which enables the
automatic search. All block devices with the file system label OEMDRV are examined and drivers
are loaded from these devices in the order in which they are encountered.
iSCSI Boot Firmware T able
Red Hat Enterprise Linux 5.3 now fully supports the iSCSI Boot Firmware Table (iBFT) which
allows for booting from iSCSI devices. This support required that iSCSI disks (nodes) are no
longer marked to start up automatically; the installed system will no longer automatically connect
and login to iSCSI disks when entering runlevel 3 or 5.
iSCSI is usually used for the root filesystem, in which case this change does does not make a
difference as the initrd will connect and login to the needed iSCSI disks even before the runlevel
is entered.
However if iSCSI disks need to be mounted on non root directories, for example /hom e or
/srv, then this change will impact you, since the installed system will no longer automatically
connect and login to iSCSI disks that are not used for the root filesystem.
Using iSCSI disks mounted on non root directories is still possible, but requires the use of one
of the following workarounds:
1. Install the system without use of iSCSI disks mounted on non root directories and later
configure the relevant disks and mount points manually
2. Boot the installed system into runlevel 1, and mark any iSCSI disks that are not used for
the root filesystem for automatic startup by using the following command once per disk:
iscsiadm -m node -T target-name -p ip:port -o update -n
Comentarios a estos manuales