Bug 2811 - hey.. no supplemental disk image file in 6.0 FTP distributions
hey.. no supplemental disk image file in 6.0 FTP distributions
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-14 02:14 EDT by dankeating
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-05-14 18:18:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dankeating 1999-05-14 02:14:51 EDT
I recently pulled down Linux Redhat 6.0 via FTP & burned a
cd from the files I made.. just as with 5.2.. I went into
dosutils & made a boot disk..and to my suprise there was no
supplemental image file to make a supplemental disk.. I
booted to the boot disk made from the 6.0 files & tried to
use that with the old supplimental disk from 5.2..no go..
	I then booted to the old 5.2 boot disk & used the 5.2
supplimental disk with the 6.0  CD I made.. THAT worked.. I
now have Redhat 6.0..
   You might want to add a suuplimental disk image file to
the ftp mirrors .. the site I downloaded from is funet.fi
Comment 1 David Lawrence 1999-05-14 18:18:59 EDT
6.0 does boot disks slightly different. Instead of using a separate
supp disk for ftp, hard drive, smb, installs, there is now a boot.img
and a bootnet.img. You will choose the one you need to install with
and use that one disk only.

boot.img = local cdrom, hard disk installs

bootnet.img = nfs, ftp, http, and smb installs.

Of course if you need pcmcia support for any of the different types
then you will need to make a disk with the pcmcia.img to load but this
is not necessary for most workstation installs.

Note You need to log in before you can comment on or make changes to this bug.