Actually, I figured out it is just that: I must have misunderstood the point when thinking that LILO boots an OS from the partition mentioned. No one ever mentioned that in manuals and how-to's. However, when I copied vmlinuz.suse and System.map of suse to the boot partition of the mandrake it finally worked. I first tried to configure lilo to boot the suse as other OS in order not to copy anything as proposed on the mailing list, but it generated a mistake in Mandrake Control Center - Boot and lilo did not recognize it. I tried to edit the lilo.conf file manually, but the choice "SUSE" didn't even appear in the boot menu due to the same mistake in LILO. So I gave it up and did the copy. Thanks for the help. I knew there is a way to do it nd it is rather simple, too, but how would I suppose that the lilo does not grab everything from the root partition I configured it. Chavdar
civileme wrote: > Chavdar Videff wrote: > >> Hi >> I tried and installed two different distributions of linux on the >> same machine in order to compare them, etc. >> The first one was a Mandrake 8.1 and I use its lilo to boot all other >> OS. Everything was OK and worked smoothly. >> However, I installed a SuSE 7.0 and during the installation process >> everything worked fine. >> When I rebooted, the SuSE started to behave strangely. Modprobe could >> not find the eth0 for instance. I was not able to mount vfat >> partitions. I could not even makeconfig in order to recompile the >> kernel (I thought something got wrong with the NIC driver). >> This was at work. >> At home I tried the same combination with the same result. >> Then I changed the things on my machine at home. I installed SuSE 6.3 >> to be the first linux and as the second I tried a Mandrake 8.0 that I >> had installed successfully some months before. It did not work. I >> suspected that something is wrong and installed as the only linux the >> said SuSE 7.0 on another machine. It was just perfectly ok. >> Then at work I booted the SuSE 7.0 via the boot floppy disk and it >> worked fine, modeprobed everything, the network was fine, etc. >> When I booted the Mandrake it initialized and then it had an error >> with the X server that was totally unexpected and hardly recoverable. >> What's wrong? >> Is it the LILO that messes up things? >> Is it the swap partition that is read by both OS? >> Is it possible to have two linuxes on a single machine at all? >> How can I avoid booting any linux via a floppy boot disk which I find >> inconvenient? >> >> Thanks >> Chavdar >> >> >> >> >> ------------------------------------------------------------------------ >> >> Want to buy your Pack or Services from MandrakeSoft? Go to >> http://www.mandrakestore.com >> > Your problem is the lilo configuration. > > In that configuration there is a line that says > > initrd= > > for each boot > > It is normally set to /boot/initrd.img which IS A LINK > > Now suppose you have a /boot and you install mandrake 8.2 (example) > > In the boot are files like > > vmlinuz (link) => vmlinuz-2.4.18-6mdk > initrd.img (link)=>initrd-2.4.18-6mdk.img > > When you install (for example) 8.1 using the same LILO and /boot > > You want LILO to boot > vmlinuz-2.4.8-26mdk > and use initrd > initrd-2.4.8-26mdk.img > > Most likely, unless you changed these lines in LILO, you are using a > Mandrake kernel and initrd to boot SuSE and that works except that > there is no match between /lib/modules in the SuSE install and the > mandrake ckernel you booted. > > So it takes a little editing--use MandrakeControl Center=>Boot > configuration and you can change the lines for image and initrd (in > fact they're both drop-down lists. > > Civileme > > > > >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
