Re: Slink, Redhat, Windows boot from lilo?
ktb wrote:
>
> Brad wrote:
> >
> > On Sun, Dec 05, 1999 at 04:57:12PM -0600, ktb wrote:
> > >
> > > Brad wrote:
> > > >
> > > > On Sun, Dec 05, 1999 at 11:46:46AM -0600, ktb wrote:
> > [[[SNIP]]]
> > > > >
> > > > > As it is I can boot to all three os's but the kernel I have compiled for
> > > > > Slink is 2.0.36. When I boot from lilo into Slink at this point it
> > > > > doesn't boot my custom kernel, which is not surprising since lilo.conf
> > > > > says "image=/boot/vmlinuz-2.2.5-15." I changed that line to read,
> > > > > "image=/boot/vmlinuz-2.0.36" but then I get an error when I run
> > > > > /sbin/lilo that that file doesn't exist. So what do I do here? Do I
> > > > > copy my Slink kernel to /usr/src on the Redhat side?
> > > >
> > > > Try mounting the slink partition (e.g. as /mnt/slink) and changing the
> > > > slink image line to something like "image=/mnt/slink/boot/vmlinuz-2.0.36"
> > > >
> > > > I've never tried this myself, but it should work. Even if it doesn't
> > > > work, it won't hurt anything to try.
> > >
> > > Well I tried adding that line and it didn't work. When I boot into
> > > Slink off the HD it set me up with the Redhat kernel, not my custom
> > > Slink kernel. This is the error I got when I ran lilo after the change
> > > in /etc/lilo.conf:
> > >
> > > Added redhat *
> > > Added 95
> > > open /mnt/slink/boot/vmlinuz-2.0.36 No such file or directory.
> >
> > Did you remember to mount the slink partition under /mnt/slink (i.e.
> > "mkdir /mnt/slink; mount -t ext2 /dev/hdb3 /mnt/slink")? Can you look in
> > there and find the proper path for the kernal image file?
> >
>
> Ok I already changed the mbr back to windows default and reran lilo from
> Slink and now I boot directly into Slink on startup. I'm not entirely
> sure what your getting at here but I've reversed this and did,
> "mkdir /mnt/redhat; mount -t ext2 /dev/hdb1 /mnt/redhat"
> After cding to /mnt/redhat I found directory /boot and inside is
> "vmlinux-2.2.5-15." So if I get you correctly you are saying to put the
> following in my lilo.conf,
>
> image=/mnt/redhat/boot/vmlinuz-2.2.5-15
> lable=redhat
> root=/dev/hdb1
>
> Now to make this all work after running lilo do I have to put something
> like the following line in my /etc/fstab?
>
> /dev/hdb1 /mnt/redhat ext2 defaults,errors=remount-ro 0 1
>
> Thanks,
> kent
Ok I found that if I mount /mnt/redhat and run /sbin/lilo while mounted
to /dev/hdb1 I get the error message that the lable for Redhat is too
long so I made a directory /mnt/rh still get the error,
xyf:/mnt/rh# /sbin/lilo
Added slink *
Label "vmlinuz-2.2.5-15" is too long
I noticed there was a "vmlinuz" link to "vmlinuz-2.2.5-15" so I changed
the line in lilo.conf to read "image=/mnt/rh/boot/vmlinuz"
and got the following error,
xyf:/mnt/rh/boot# /sbin/lilo
Added slink *
Added vmlinuz
Syntax error near line 50 in file /etc/lilo.conf
Arg.
Thanks,
kent
Reply to:
- References:
- Slink, Redhat, Windows boot from lilo?
- From: ktb <xyf@inebraska.com>
- Re: Slink, Redhat, Windows boot from lilo?
- From: Brad <lists@anomie.dhis.net>
- Re: Slink, Redhat, Windows boot from lilo?
- From: ktb <xyf@inetnebr.com>
- Re: Slink, Redhat, Windows boot from lilo?
- From: Brad <lists@anomie.dhis.net>
- Re: Slink, Redhat, Windows boot from lilo?
- From: ktb <xyf@inetnebr.com>