Red Hat ENTERPRISE 5.3 RELEASE NOTES Guia de Instalação descarregar pdf (Página 14)

must reboot after completing the upgrade. You should then boot the system using the updated

Virtualized kernel.

The hypervisors of Red Hat Enterprise Linux 5 and 5.2 are not ABI-compatible. If you do not boot the

system after upgrading using the updated Virtualized kernel, the upgraded Virtualization RPMs will

not match the running kernel.

When upgrading to Red Hat Enterprise Linux 5.1 or later from Red Hat Enterprise Linux 4.6, gcc4

may cause the upgrade to fail. As such, you should manually remove the gcc4 package before

upgrading.

The firstboot language plugin has been removed, as it does not properly and completely

reconfigure the system when a new language is selected.

When provisioning guests during installation, the RHN tools for guests option will not be available.

When this occurs, the system will require an additional entitlement, separate from the entitlement

used by dom 0.

To prevent the consumption of additional entitlements for guests, install the rhn-

virtualization-comm on package manually before attempting to register the system to Red Hat

Network.

Installing Red Hat Enterprise Linux 5.3 on a system with multiple network interfaces and manually

specified IPv6 addresses may result in a partially incorrect networking setup. When this occurs, your

IPv6 settings will not be visible on the installed system.

To work around this, set NET WORKING_IPV6 to yes in /etc/sysconfig/network. Then, restart

your network connection using the command service network restart.

If your system has yum -rhn-plugin-0.5.2-5.el5_1.2 (or an earlier version) installed, you will

be unable to upgrade to Red Hat Enterprise Linux 5.3 through yum update. To work around this,

upgrade your yum -rhn-plugin to the latest version (using yum update yum-rhn-plugin)

before running yum update.

Previously, anaconda could not access more than 8 SmartArray controllers. In this update, this

issue has been resolved.

A driver disk, supplied by an OEM, is a single image file (*.img), containing potentially multiple driver

packages and kernel modules. These drivers are used during installation to support hardware that

otherwise would not be recognized by Red Hat Enterprise Linux 5. Once the driver packages and

kernel modules are installed on the system, they are placed in the initial RAM disk (initrd) so that

they are loaded when the system boots.

With this release, installation can automatically detect a driver disk (based on its file system label),

thereby using 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. dlabel=on is

the default setting for this release.

All block devices with the file system label OEMDRV are examined and drivers are loaded from these

devices in the order by which they are detected.

Existing encrypted block devices that contain vfat file systems will appear as type foreign in the

partitioning interface; as such, these devices will not be mounted automatically during system boot.

To ensure that such devices are mounted automatically, add an appropriate entry for them to

/etc/fstab. For details on how to do so, refer to m an fstab.

2.2. PowerPC Architectures

The minimum RAM required to install Red Hat Enterprise Linux 5.2 is 1GB; the recommended RAM is

2GB. If a machine has less than 1GB RAM, the installation process may hang.

Further, PowerPC-based machines that have only 1GB of RAM experience significant performance

issues under certain RAM-intensive workloads. For a Red Hat Enterprise Linux 5.2 system to perform

2. Installation-Related Notes

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 208 209

Comentários a estes Manuais

Sem comentários

Red Hat ENTERPRISE 5.3 RELEASE NOTES Guia de Instalação Página 14

Comentários a estes Manuais

Manuais e produtos relacionados com Telefones Red Hat ENTERPRISE 5.3 RELEASE NOTES