How big is your root partition going to be? If the partition is over a certain
size, lilo will not work. You should run lilo, and look at any messages. I had
to use a smaller partition for /boot, and this was the first partition on my
/dev/hdc. I pointed the boot flag to /dev/hda. I needed to have this
because of Windows not wanting to install onto anything other than /dev/hda1.
After doing this, lilo worked fine, and it booted OK.
On Mon, 03 Apr 2000, you wrote:
> I've used SC and it is a very useful program. To get it to work with Lilo make
> sure that you had Lilo installed in the first sector of the root partition.
> Then all you have to do is point SC to that partition for booting Linux. The
> only problem I had was figuring out which Ext2 partition was the root for
> linux. Simple solution, try them one at a time till one boots, heheh.
>
> Rusty Carruth wrote:
> >
> > >
> > > The problem is that system commander does not see a valid
> >
> > Wait a sec - how exactly are you planning to boot - using system
> > commander or lilo?
> >
> > > bootable, MBR record for linux. If I could get it to boot LILO
> > > I would be fine, but I can not even get it to boot LILO (except
> > > from the boot diskette)
> >
> > in the installs I've done, (and some of them got PRETTY strange - i had
> > a system set up one time where I could boot from one boot loader to another
> > all day long - I had NT's boot loader, OS/2's boot loader, and LILO all
> > inter-linked - yeah, don't try this at home ;-) ...
> >
> > Ok, lets start that again. In the installs I've done, I either use
> > the 'dumber' boot loaders from 'normal' os's and let them point to
> > lilo on the linux root partition on /dev/hda, OR I install lilo on
> > the MBR and let IT be the first thing to see life, then let it know
> > that my boot images are on a different drive. I don't recall ANY
> > boot loaders other than LILO being able to do that (but now someone
> > will correct me ;-)
> >
> > So, do you reeally NEED system commander as the MBR boot loader?
> >
> > if not, boot linux from your floppy, set up lilo.conf sorta like I suggested
> > last message, run lilo (make sure it was happy), and reboot... LILO
> > should now be your MBR boot loader and be able to find your bootable
> > image over on /dev/hdc.
> >
> > OR, if you absolutely MUST use SC, either install it somewhere other than
> > the MBR and let lilo boot to it as the second stage boot loader, OR
> > install LILO on /dev/hdc and tell SC to boot there (assuming it CAN), OR
> > make a small partition on /dev/hda, put lilo there (pointing to your /dev/hdc
> > linux partition), and tell SC to boot THAT.
> >
> > If none of those work, then I'm fresh out of ideas! A SC guru
> > will have to take over...
> >
> > rusty
> >
> > _______________________________________________
> > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
> > > The problem is that system commander does not see a valid
> >
> > Wait a sec - how exactly are you planning to boot - using system
> > commander or lilo?
> >
> > > bootable, MBR record for linux. If I could get it to boot LILO
> > > I would be fine, but I can not even get it to boot LILO (except
> > > from the boot diskette)
> >
> > in the installs I've done, (and some of them got PRETTY strange - i had
> > a system set up one time where I could boot from one boot loader to another
> > all day long - I had NT's boot loader, OS/2's boot loader, and LILO all
> > inter-linked - yeah, don't try this at home ;-) ...
> >
> > Ok, lets start that again. In the installs I've done, I either use
> > the 'dumber' boot loaders from 'normal' os's and let them point to
> > lilo on the linux root partition on /dev/hda, OR I install lilo on
> > the MBR and let IT be the first thing to see life, then let it know
> > that my boot images are on a different drive. I don't recall ANY
> > boot loaders other than LILO being able to do that (but now someone
> > will correct me ;-)
> >
> > So, do you reeally NEED system commander as the MBR boot loader?
> >
> > if not, boot linux from your floppy, set up lilo.conf sorta like I suggested
> > last message, run lilo (make sure it was happy), and reboot... LILO
> > should now be your MBR boot loader and be able to find your bootable
> > image over on /dev/hdc.
> >
> > OR, if you absolutely MUST use SC, either install it somewhere other than
> > the MBR and let lilo boot to it as the second stage boot loader, OR
> > install LILO on /dev/hdc and tell SC to boot there (assuming it CAN), OR
> > make a small partition on /dev/hda, put lilo there (pointing to your /dev/hdc
> > linux partition), and tell SC to boot THAT.
> >
> > If none of those work, then I'm fresh out of ideas! A SC guru
> > will have to take over...
> >
> > rusty
> >
> > _______________________________________________
> > Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> _______________________________________________
> Plug-discuss mailing list - Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
--
Rick Rosinski
http://www.rickrosinski.com
rick@rickrosinski.com
(text/plain)