이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 9. Installation and Booting
Installation on IBM System z with a network device in IPv6-only mode is now possible
Previously, when an IPv6-only network device was activated during initialization on IBM System z, a segmentation fault occurred and installation failed. The installer now handles these devices correctly, and no segmentation fault occurs, allowing installation to proceed. (BZ#1329171)
Adding a new EFI boot entry on a multipath device no longer fails
Previously, the
efibootmgr
utility was run multiple times for each device in multipath, which led to duplicate boot entries and possible failure. With this update, a new EFI boot entry is added only once for the whole multipath device. (BZ#1346725)
The size of the output buffer in efibootmgr
has been increased
Previously, the output of the
efibootmgr
utility was sometimes truncated. The size of the output buffer has been increased, and now efibootmgr
can show more detailed information. (BZ#1347283)
The gateway
installation boot option now handles IPv6
addresses
Previously, the
gateway
boot option in the installation system supported only IPv4
addresses. With this update, it is possible to configure an IPv6
gateway, using the gateway
boot option, during installation. (BZ#1177984)
Thin provisioning can be successfully configured during installation
Due to changes in the way the LVM tools are packaged, the installation system raised an error while configuring thin provisioning. With this update, the installation environment is able to use these tools correctly, and thin provisioning can now be configured successfully. (BZ#1350296)
ifdown
on a loopback device now works properly
In Red Hat Enterprise Linux version 6.7 and 6.8, executing the
ifdown
command on a local loopback device failed to remove the device. A patch has been applied, and the removal of an existing loopback device using ifdown
now succeeds. (BZ#1311811)
Scripts in initscripts handle static IPv6 address assignment more robustly
Previously, scripts in the initscripts package sometimes failed to correctly assign static IPv6 addresses if a Router Advertisement (RA) was received during system initialization. This bug has been fixed, and now the statically assigned address is correctly applied in the described situation. (BZ#1086388)
Decompression of initrd larger than 32 MB no longer fails in GRUB on SGI UV100/UV1000 hardware
Previously, decompressing the
initrd
image in the GRUB
boot loader could fail on SGI UV100 and UV1000 servers in cases where the image was loaded from a TFTP
server and was larger than 32 MB. GRUB
has been updated, and the initrd
will now decompress successfully. (BZ#1124862)
The ifup-aliases
script now sends gratuitous ARP updates when adding new IP addresses
When moving one or more IP aliases from one server to another, associated IP addresses may be unreachable for some time, depending on the Address Resolution Protocol (ARP) time-out value that is configured in the upstream router. This bug has been addressed in the initscripts package, and
ifup-aliases
now updates other systems on the network significantly faster in this situation. (BZ#1320366)
The initscripts package now handles LVM2 correctly
Previously, due to a bug, the initscripts package sometimes caused errors during boot on systems with using version 2 of the Logical Volume Manager device mapper (LVM2). With this update, this bug is fixed, and systems with LVM2 now boot correctly. (BZ#1331684)
The netconsole
utility now launches correctly
Previously, if
nameserver
address lines were not present in the /etc/resolv.conf
file, launching netconsole
sometimes resulted in an error and netconsole
did not start. The initscripts package has been updated, and netconsole
now starts correctly in this situation. (BZ#1278519)
The service network stop
command no longer attempts to stop services which are already stopped
Previously, when a tunnel interface was present, the
service network stop
command incorrectly attempted to stop services which had been stopped already, displaying an error message. With this update, this bug is fixed, and the service network stop
command now only stops running services. (BZ#1315018)
The dhclient
command no longer incorrectly uses localhost
when hostname
is not set
The
dhclient
command incorrectly sent localhost
to the DHCP server as the host name when the hostname
variable was not set. This has been fixed, and dhclient
no longer sends an incorrect host name in these situations. (BZ#1350602)