Bug 124 - boot.img or supp.img fail to see installation directory on hard drive
boot.img or supp.img fail to see installation directory on hard drive
Product: Red Hat Linux
Classification: Retired
Component: aboot (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1998-11-18 14:09 EST by plu
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:
Last Closed: 1999-01-04 13:24:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description plu 1998-11-18 14:09:07 EST
8 GB drive partitioned as four 2 GB partitions in the order:
NTFS, FAT16, Linux, FAT16.  Installation source is on first
FAT16 partition under directory /redhat52.  When
floppy booting from current boot.img/supp.img combination,
error message indicates that source directory can't be
found.  This set-up worked fine with the RedHat 5.1
boot.img/supp.img combination (seems that boot.img is
exactly same for 5.1 and 5.2).  When going back to using the
5.1 boot.img/supp.img combination, the source directory
seems to be found, but an error indicating some comp 0 file
not being found is displayed.

Using "upgrade" option to bring 5.1 to 5.2.

Would be nice is the installation code had some kind of
"browse" capability to go thru the directory tree of a
source hard drive, rather than only a input text line.
Comment 1 Cristian Gafton 1998-11-18 21:22:59 EST
Matt, please take a look at the install code and see if there is
something worng with the installation from a hard drive partition
part. I've heard of problems about that from other sources too, so
there must be something true about it. Or if all those people are
doing something wrong, they are all mistaking in the same way, which
is odd.
Comment 2 Matt Wilson 1999-01-04 13:24:59 EST
Should be fixed in new images.  See


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