One can load either of them, I just do'nt know grub. With lilo, one would basicly get to a linux prompt using the rescue disk, mount your linux partition, change to the correct spot, chroot configure and run lilo. I think grub would be like wize. regards, Willem
On Thu, 7 Feb 2002, Steve Cohen wrote: > Is it possible (or desirable) to similarly load GRUB instead of LILO? > > Willem van der Walt wrote: > > > I would suggest you go into rescue mode and try to get lilo installed on > > the boot sector from there. > > regards, Willem > > > > On Thu, 7 Feb 2002, Steve Cohen wrote: > > > > > >>Aargh! I am in upgrade hell. > >>I tried to upgrade a system that was running 7.0 to 7.2. It is a dual > >>boot system with Win 98 running in the other partition. The hard drive > >>was partitioned originally using Partition Magic. > >> > >>OK. I started the upgrade and I didn't think it through clearly enough. > >> When it asked me what kind of loader I wanted to use, I thought I > >>should just continue using Partition Magic, so I selected "do not > >>install a boot loader". I followed the advice and upgraded to an ext3 > >>file system. I chose all my upgrade packages and the system upgraded > >>itself. Smoothly, it looked like. I made a floppy and was done. > >> > >>Of course, it didn't work. Partition Magic didn't know doodly squat > >>about my new ext3 file system and hung when I tried to boot it. Win 98 > >>still worked. Ah I thought, I would boot off the floppy. But that > >>failed, said it failed to boot, so was useless. > >> > >>So I got rid of Partition Magic. Uninstalled both it and its companion, > >>Boot Magic. I thought I would go back into the upgrade and try the new > >>GRUB loader. So I rebooted to the CDROM once again, went through the > >>upgrade rigamarole, added a couple of packages, but when it was all > >>done, it said I hadn't changed the kernel, therefore it wouldn't write > >>the boot image to disk!! Even though I'd changed the loader. Tried > >>GRUB, LILO, no matter what I did after this point, it would not write > >>the boot image. I even went in and installed the debug kernel thinking > >>it would see this as a kernel change and write the boot image out. Nope. > >> > >>So I'm stuck here with what is probably a perfectly good Linux partition > >>that cannot load because the installer refuses to write the boot image, > >>and cannot generate a good boot floppy! (Oh yeah, I tried writing it > >>out again to another floppy with the same results). > >> > >>This is REALLY annoying. Is there something I can do in the upgrade > >>process to FORCE it to write the boot image? > >> > >> > >> > >>_______________________________________________ > >>Redhat-list mailing list > >>[EMAIL PROTECTED] > >>https://listman.redhat.com/mailman/listinfo/redhat-list > >> > >> > > > > > > > > _______________________________________________ > > Redhat-list mailing list > > [EMAIL PROTECTED] > > https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > > > > _______________________________________________ > Redhat-list mailing list > [EMAIL PROTECTED] > https://listman.redhat.com/mailman/listinfo/redhat-list > _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
