Ben Logan wrote:
> On Mon, 04 Sep 2000 10:27:12 -0500, Bret Hughes said:
>
> > Ben Logan wrote:
> >
> > > Greetings,
> > >
> > > Awhile ago, I installed a new hard-disk in my computer (which already had win95
> > > on it), and put RH6.2 on the new disk. I didn't make a bootable linux
> > > partition though (I've been booting off floppy when I want to load linux).
> > >
> > > Windows crashed and has to be reinstalled, so while I'm reformatting anyway,
> > > I'm going to create a (roughly) 3M partition on the win95 disk and would like
> > > to install lilo and make linux bootable off that partition.
> > >
> > > How would I go about doing this?
> >
> > Ben I would install windows and then boot off the floppy.
> > edit /etc/lilo.conf to include the new windows image
> >
> > other=/dev/hda1
> > label=win98
> >
> > and check the linux boot partition stuff
> >
> > save it and run lilo -v
> >
> > That should do I I believe.
> >
> > Bret
> I'm still somewhat confused as to where linux is going to get the files it
> needs to boot. Don't I have to copy a boot image or something to hda1 in order
> for Linux to boot? Also, lilo only resides on the floppy disk...how do I put
> it on hda?
>
> Here's my /etc/lilo.conf file, maybe it will help:
> boot=/dev/hdc7
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> linear
> default=linux
>
> image=/boot/vmlinuz-2.2.14-5.0
> label=linux
> read-only
> root=/dev/hdc7
>
> other=/dev/hda1
> label=dos
>
> Thanks,
> Ben
It looks like to me that this is ready to go. lilo's default is to write to the master
boot record (mbr) this is where the hardware looks for instructions on where to find
the OS. I don't think that once a machine is booted lilo knows or cares where it
booted from. Thus running lilo -v will setup the mbr to run lilo with the two options
listed,
linux on hdc7
windows on hda1
BTW what is on hdb?
I don't think that lilo will have any problem booting from hdc but I don't really
know. A google search on lilo hdc find references to people doing just that.
If you are worried about screwing something up ust the test option first:
lilo -t -v
This will tell you what lilo is about to do but not actually do anything.
Lilo should be on the hard drive if not the problem is beyond my experience.
go ahead and try it with the -t -v option and post the results. perhaps someone with
more knowledge will jump in and tell us if I am over simplifying this.
Bret
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
