Date: Wed, 19 Apr 2000 17:20 -0400
From: bugzilla@redhat.com
Reply-To: redhat-watch-list@redhat.com
To: redhat-watch-list@redhat.com
Subject: [RHBA-2000:015-01] Installer updates for Red Hat Linux
6.2
Red Hat, Inc. Bug Fix Advisory
Synopsis: Installer updates for Red Hat Linux 6.2
Advisory ID: RHBA-2000:015-01
Issue date: 2000-04-19
Updated on: 2000-04-19
Product: Red Hat Linux
Keywords: anaconda installer
Cross references: N/A
1. Topic:
New anaconda boot disks and update disks are available which fix
several issues with the Red Hat Linux 6.2 installer.
2. Relevant releases/architectures:
Red Hat Linux 6.2 – i386
3. Problem description:
An anaconda boot disk and updates disk are now available which
includes the fixes from http://www.redhat.com/support/errata/RHBA-2000010-01.html,
as well as addressing the following problems:
1. Fixes problems with selecting the Microsoft Intellimouse ™
in the GUI installer.
2. Fixes problems when using more than one ethernet device and
static IPs.
4. Solution:
The updated bootdisk from bug fix http://www.redhat.com/support/errata/RHBA-2000010-01.html
is required to use this update disk.
The boot diskettes shipped with Red Hat Linux 6.2 Intel do not
support anaconda updates. Booting from CDROM will not allow the
updates disk to be used.
Follow the instructions in Red Hat Linux Installation Guide to
make a floppy boot disk from one of the following files located at
ftp://updates.redhat.com/6.2/images/i386:
bootnet-20000407.img
pcmcia-20000407.img
In addition, you will need to make a floppy disk from:
update-disk-20000419.img
A pointer to the online documentation is provided in the
References section of this advisory.
(Note: you only need one of the boot images; users installing
from CD will only need boot-20000407.img)
(Note: when creating the update disk image under a Linux-like
OS, do not specify the “bs=1440k” argument to dd since the update
disk image is not an entire floppy in length.)
When booting into the anaconda installation program, type “linux
updates” at the boot prompt, followed by any other installation
options which are required (such as “expert” or “text” or “ks”).
The installation process will prompt you to insert the updates disk
when it is required, and the install will then proceed as
normal.
5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla
for more info):
10456
10687
6. Obsoleted by:
N/A
7. Conflicts with:
N/A
8. RPMs required:
i386:
—–
ftp://updates.redhat.com/6.2/images/i386/boot-20000407.img
ftp://updates.redhat.com/6.2/images/i386/bootnet-20000407.img
ftp://updates.redhat.com/6.2/images/i386/pcmcia-20000407.img
ftp://updates.redhat.com/6.2/images/i386/update-disk-20000419.img
9. Verification:
MD5 sum Package Name
boot-20000407.img 535f6374811ddee3bd53f0cfdce4f36e bootnet-20000407.img a764dbba1c8f4129c609ff70777733c3 pcmcia-20000407.img a6254da754d1e2f9df9e0a4dc2df1fa4 update-disk-20000419.img 9a829c3b4517c1d00e117a7ab11134ba
These packages are GPG signed by Red Hat, Inc. for security. Our
key is available at: http://www.redhat.com/corp/contact.html.
You can verify each package with the following command:
rpm –checksig
If you only wish to verify that each package has not been
corrupted or tampered with, examine only the md5sum with the
following command:
rpm –checksig –nogpg
10. References: