On Fri, 23 Mar 2001, Dresner, Norman A. wrote:
>
> Yes, I'm convinced that the "crosstalk" comes from using the module-info for
> the new system for the old one too. Unfortunately there is no lilo.conf
> option to change the module-info file on a per-image basis. (Nor the
> System.map either).
>
> There are -- as I see it now -- two options:
>
> 1) make the module-info agree for the two OS versions -- this may be
.....
>
> 2) copy system map and module info files for both systems into the
....
>
> Actually, there might be a third option: hacking up the loader and lilo to
....
So what is wrong with having two separate boot directories? Your lilo
conf would look similar to:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux-new
image=/boot/vmlinuz-2.2.17-14
label=linux-new
initrd=/boot/initrd-2.2.17-14.img
read-only
root=/dev/hdc1
image=/old/boot/vmlinuz-2.0.36
label=linux-old
initrd=/old/boot/initrd-2.0.36.img
read-only
root=/dev/hdb1
And you mount /dev/hdb1 as /old (for the new system).
Similar, you can make a lilo.conf for the old system where /dev/hdc1
(root of the new system) mounted as /new....
>
> Norman Dresner
Sincerely,
Dmitri.
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/