RAM-intensive processes optimally, 4GB of RAM is recommended. This ensures the system has the
same number of physical pages as was available on PowerPC machines with 512MB of RAM running
Red Hat Enterprise Linux 4.5 or earlier.
2.3. s390x Architectures
anaconda now supports both ports on CHPID for OSA Express3 cards. T he installer will prompt for
the port number in the initial stage of the installation. T he value provided for the port also affects
installed network interface startup script. When port 1 is selected, the value portno=1 is added to
OPTIONS parameter of ifcfg-eth* file.
Note
When installing under z/VM, you can add either PORT NO=0 (to use port 0) or PORT NO=1 (to
use port 1) to the CMS configuration file to avoid being prompted for the mode.
Installation on a machine with existing Linux or non-Linux filesystems on DASD block devices may
cause the installer to halt. If this happens, it is necessary to clear out all existing partitions on the
DASD devices you want to use and restart the installer.
2.4. ia64 Architecture
If your system only has 512MB of RAM, attempting to install Red Hat Enterprise Linux 5.3 may fail. T o
prevent this, perform a base installation first and install all other packages after the installation
finishes.
Using yum to install packages from the 32-bit Com patibility Layer disc may fail. If it does, it
is because the Red Hat package signing key was not imported into the RPM database. This happens
if you have not yet connected to Red Hat Network and obtained updates. T o import the key manually,
run the following command as root:
rpm --im port /etc/pki/rpm -gpg/RPM-GPG-KEY-redhat-release
Once the Red Hat GPG key is imported, you may now use yum to install packages from the 32-bit
Com patibility Layer disc.
Note that when installing from this disc, it is advisable to use yum instead of rpm to ensure that base
OS dependencies are addressed during installation.
3. Feature Updates
Block Device Encryption
Red Hat Enterprise Linux 5.3 includes support for block device encryption using the Linux
Unified Key Setup (LUKS) specification. Encrypting a device protects all data on a block device
against unauthorized access, even if the device has been physically removed from a system.
To access the contents of an encrypted device, a user must provide a passphrase or key as
authentication.
For information on setting up disk encryption, refer to Chapter 28 of the Red Hat Enterprise
Linux Installation Guide at: http://redhat.com/docs/
mac80211 802.11a/b/g WiFi protocol stack (mac80211)
The mac80211 stack (formerly known as the devicescape/d80211 stack) is now a supported
Comentarios a estos manuales