gofast
12-13-2000, 02:19 AM
Help me someone Im losing my mind. I have slack happily installed on hda3. So I go and buy a nice new drive, 30 gig, and decide to try other installations. BUT:
If I use lilo, it boots new installations using the kernel on my slack distro. If I install lilo on the boot sectors of the hdc partitions and use the "other" command in the MBR lilo, it passes it and then I get as far as LI.
Lastly, if I go into the distro on hdc1 and just ignore my slack distro, trying to put a simple lilo file on my MBR that boots to the hdc, I STILL only get LI. I have tried running it with -L to no avail. It is a recent lilo version that gets past 1024.
The conf files are simple, boot=/dev/hda (in the case of trying to write it to the MBR), image=kernel name, root=/dev/hdc1, read-only.
The frigging conf file I use in my slack distro is the same - except root=/dev/hda3, and there is a second entry that has the other distro in it, like the one above.....
ANY help wold be great!
If I use lilo, it boots new installations using the kernel on my slack distro. If I install lilo on the boot sectors of the hdc partitions and use the "other" command in the MBR lilo, it passes it and then I get as far as LI.
Lastly, if I go into the distro on hdc1 and just ignore my slack distro, trying to put a simple lilo file on my MBR that boots to the hdc, I STILL only get LI. I have tried running it with -L to no avail. It is a recent lilo version that gets past 1024.
The conf files are simple, boot=/dev/hda (in the case of trying to write it to the MBR), image=kernel name, root=/dev/hdc1, read-only.
The frigging conf file I use in my slack distro is the same - except root=/dev/hda3, and there is a second entry that has the other distro in it, like the one above.....
ANY help wold be great!