Very Computer

I just upgraded to RedHat 6.1 on a system which I have set up for dual
boot of OS-9 and Linux.  All apparently went well until I decided to
boot OS-9...at which point I found that os9 was no longer recognized as
something I could boot.

Investigation shows that the upgrade changed the lilo.conf file (making
a backup, for which I am grateful), which I can understand, but the
changed version didn't include the alternatives that I had in the then-
current lilo.conf file.  This seems somewhat rude, and while it will be
trivial to set things back the way they were, I'd think that the upgrade
code should be smart enough to keep the other alternatives from the
lilo.conf file.

I'll nudge Red Hat about this, but figured I should post here so that
people won't find themselves unpleasantly surprised.

    James Jones

Opinions herein are those of the author, and not necessarily those of
any organization.

Yeah. This is why I tend to upgrade between versions of distributions
manually these days, rather than using the installer programs. It
takes more time, but your configuration doesn't get shot in the head.
I can't remember offhand how much Debian automates the upgrade of
lilo.conf files, but it certainly has it marked as a configuration
file and therefore explicitly asks you to examine the differences
between the two files and decide which one to keep (or indeed how to
merge the old and the new versions).

--

Trinity College, Cambridge, and Computer Science       [riva.ucam.org]
"Logic is about * a dead horse." - Computer Science lecturer

Quote:>I just upgraded to RedHat 6.1 on a system which I have set up for dual
>boot of OS-9 and Linux.  All apparently went well until I decided to
>boot OS-9...at which point I found that os9 was no longer recognized as
>something I could boot.

>Investigation shows that the upgrade changed the lilo.conf file (making
>a backup, for which I am grateful), which I can understand, but the
>changed version didn't include the alternatives that I had in the then-
>current lilo.conf file.  This seems somewhat rude, and while it will be
>trivial to set things back the way they were, I'd think that the upgrade
>code should be smart enough to keep the other alternatives from the
>lilo.conf file.

Maybe yes, but in my case it did recognize the other OS correctly and
I was given a choice of which OS to boot as default. Still creating a new
lilo.conf though that did not contain my 'append=' that I need to
recognize my cdrom.

OS-9 ???

--
Hal B

--
            Linux helps those who help themselves