Bug 5401 - mkbootdisk-1.2-2 and -3 fail to make bootable disk
mkbootdisk-1.2-2 and -3 fail to make bootable disk
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: mkbootdisk (Show other bugs)
6.0
All Linux
high Severity medium
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-09-27 14:08 EDT by Christopher Johnson
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-09 01:20:09 EST
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 Christopher Johnson 1999-09-27 14:08:55 EDT
The script uses devices specified with the following syntax:
device=/dev/fd0
       (ex: `basename $0` --device /dev/fd1 2.0.31)

But copies them as follows:
mkdir $MOUNTDIR/dev
cp -Pa $device $MOUNTDIR/dev
cp -Pa $rootdev $MOUNTDIR/dev

Resulting in fd0 and root device such as sda being one level
below where they belong.  e.g. $MOUNTDIR/dev/dev/fd0
This causes lilo running chrooted there to fail with a 'file
or directory not found' error.

Since this problem exists in base and updated RH 6.0 there
must be a lot of folks with floppies that won't boot when
they need them to.

The script can be fixed by replacing the above two copy
statements with the following:

cp -Pa $device $MOUNTDIR
cp -Pa $rootdev $MOUNTDIR
Comment 1 Christopher Johnson 1999-10-07 12:19:59 EDT
Fixed in mkbootdisk-1.2.2-1 in RH 6.1
Comment 2 Matt Wilson 2000-02-09 01:20:59 EST
Fixed in latest release.

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