Remember, I'm not talking about two different RT-Linux versions over the
same base Linux system. I've got two very Linux versions. I've set up the
systems as follows;
New: RT-Linux v3 over RH 6.2 with 2.2.18
Old: RT-Linux 0.9 over RH 5.2 with 2.0.36.
The differences between the two systems manifest themselves as follows:
1. I tried to create a common swap partition. But the new system
(RH 6.2/2.2.18) put a signature into the swap partition that's not
recognized by the old (RH5.2/2.0.26) system and consequently it has no swap
space. That's not fatal but ... Of course I could repartition the new HD
and create separate swap partitions for the two systems.
2. The new system's root partition [the only partition on that HD]
isn't recognized by the old system and I can't mount the new root drive onto
the old system at any mount point. That's not fatal either, but ... The
old system's fdisk shows that the partition on the new disk is "Linux
Native" but mount simply complains:
wrong fs type, bad option, bad superblock ...
The problem is probably 'bad superblock."
Also, it seems that when I run lilo in the new system its module-info and
System.map files are used to create the "boot record" (?in the mbr?) which
are wrong for the old system. It's impossible to modprobe or insmod certain
modules in the old system because that. [There is NO per-image option in
lilo.conf for either System.map or module-info.] Since one of the modules
that I can't us is for the NIC, it cripples the old system.
Here's (the relevant portions of) my lilo.conf from the new system which --
I think -- has exactly what you've suggested:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
default=rtlinux
image=/boot/RTzImage
label=rtlinux
initrd=/boot/initrd-2.2.14-5.0.img
read-only
root=/dev/hdc1
image=/boot/vmlinuz-2.0.36-0.7
label=oldrtlinux
root=/dev/hdb1
initrd=/boot/initrd-2.0.36-0.7.img
read-only
other=/dev/hda1
label=dos
Note that the files 'initrd-2.0.36-0.7.img' and 'vmlinuz-2.0.36-0.7' have
been copied from the old system's /boot into the /boot for the new system.
BTW: I get the same results if I boot the old system from its own boot
disk.
It's beginning to look like setting both systems up as /dev/hdb and
physically swapping HD's is going to be the only way to make this work.
Since I still have to support programs that use the old system, I'm open to
all suggestions.
Norm
> -----Original Message-----
> From: Dmitri A. Sergatskov [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 23, 2001 12:06 PM
> To: Dresner, Norman A.
> Cc: 'RTLinux'
> Subject: RE: [rtl] Problems Dual Booting (RT)Linux
>
> 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/
