Bug 5833 - No bootdisk created during upgrade 6.0 to 6.1 results in non-bootable system
Summary: No bootdisk created during upgrade 6.0 to 6.1 results in non-bootable system
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL: http://pobox.com/~e.maryniak/
Depends On:
TreeView+ depends on / blocked
Reported: 1999-10-11 14:28 UTC by Eric Maryniak
Modified: 2015-01-07 23:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-10-11 15:39:17 UTC

Attachments (Terms of Use)

Description Eric Maryniak 1999-10-11 14:28:59 UTC
First of all: applaus for 6.1's easy, user-friendly install!
Imho, with some more finetuning and more PnP supported
devices detection a la Win98, and availibility of good
Office Suites like Applixware that can read Word and Excel
files, Linux will definitately conquer the user desktop.

Now the problem: my 6.0 system was dual-boot Win98 and
RedHat 6.0, the switch in a [multi] config.sys with Linux
booted by loadlin.exe. Reason: I have >1024 cylinders and
I cannot use Lilo well.
Now during the "automatic upgrade", the installer does
everything very ok, however it did not give me the
oppurtunity to make a boot disk (with the working kernel),
and just installed lilo in the mbr.
Hence I had a system that I, in principle, could not boot:
fortunately, after fdisk /mbr, and booting the older kernel
from 6.0, it still worked (with lots of boot errors), I got
a prompt and immediately copied the new /boot/vmlinuz-bla
kernel to my C: (/dos/linuximg on /dev/hdax).

I would recommend giving users an option to create a
bootdisk (which can come in handy, anyways) during the
installation... (you may want to give some hints as to
to use loadlin.exe)

(if i've missed this option in the upgrade selection
(clicked Ok too soon), i am terribly sorry)

Kind regards, Eric Maryniak

Comment 1 Jay Turner 1999-10-11 15:39:59 UTC
*** This bug has been marked as a duplicate of 5578 ***

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