On Wednesday 28 March 2001 02:52, Norm Dresner wrote:
> I've tried to dual boot RTL 3.0 over Linux 2.2.18 and RTL 0.9 over 2.0.36.
>
> While I can boot both systems, I can't access (that is load) the modules in
> the "2nd" system. [In this context, the first system is the one whose LILO
> I've last run and the second system is the other.]
Well... You should probably describe all systems in a single lilo.conf file.
Put it on a shared, dedicated partition (ie one that you mount from all
systems), along with source code and whatnot.
You could probably even have the shared partition on a server and mount it
over LAN, just to avoid the risk of crashing when testing kernel code... (Or
just unmount it before you do anything dangerous.)
> I'm almost positive that reconfiguring both systems to compile into the
> kernel the various "common stuff" that I now have modular would probably
> get around this problem, but that's not the way I wanted to use it.
>
> When I boot the 2.2.18 I can mount the 2.0.36 but not conversely because
> 2.2.18 uses some fancy features.
ReiserFS or something?
//David
.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
`----------------------> http://www.linuxaudiodev.com/maia -'
.- David Olofson -------------------------------------------.
| Audio Hacker - Open Source Advocate - Singer - Songwriter |
`--------------------------------------> [EMAIL PROTECTED] -'
-- [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/
