On Sat, 23 Feb 2002 16:21:42 -0800 (PST)
Net Llama <[EMAIL PROTECTED]> wrote:

> I can't think of any good reason to be referencing a /mnt/ point in
> lilo.conf.  LILO cares only about where your kernel is, and where
> the / filesystem is.  Neither are traditionally placed under /mnt
>

I was learning lilo when I set things up under redhat, and then I
started adding more distros, and they were being mounted in redhat
under /mnt, so I just referenced them that way in lilo.conf. This is
working, but I guess it's an error. I have winme on hda1, libranet on
hda5, redhat on hda6 with /home on hda7, hda8 is swap, hda9 is elx
rc1, hda10 is elx rc 2, and I just installed Caldera 3..1 on hda11. I
booted to caldera using /mnt/hda11 in my lilo.conf, but have changed
it and elx on hda10 to  chainloaders, as seem below: 

other=/dev/hda10
        label=Elx_Linux-hda10

other=/dev/hda11
        label=Caldera-hda11

other=/dev/hda1
        optional
        label=Windows_ME

This works. Does it make more sense? When I boot caldera/elx this way,
lilo calls grub/lilo on hda11/hda10. (respectively).

I would change libranet but I'm not sure what I have for a boot loader
on hda5. 

Have I totally confused everyone? ;-)


> --- Ken Moffat <[EMAIL PROTECTED]> wrote:
> > 
> > The problem with the simple solution is the way lilo.conf is set
> > up refers to image=/mnt/hda5 or /mnt/hda? (whatever) except for
> > redhat, which is /boot/... RedHat is on /dev/hda6 (with it's /home
> > on/dev/hda7.) I'm currenly mostly using elx linux on /dev/hda10,
> > which would not be /mnt/hda10 when running /sbin/lilo from elx. 
> > 
> > It occurs to me that I'm using incorrect syntax in lilo.conf.
> > should I be using /dev instead of /mnt? But then what about the
> > image=/boot/... which will vary from dist to dist?
> > 
> > Thinking out loud...
> > 
> > RTFM....
> > 
> > Here is part of my Redhat lilo.conf;
> > 
> > image=/boot/vmlinuz-2.4.2-2
> >         label=RedHat_Linux
> >         read-only
> >         root=/dev/hda6
> >         append="hdb=ide-scsi hdc=ide-scsi"
> > 
> > image=/mnt/hda5/boot/vmlinuz
> >         label=Libranet_Linux
> >         read-only
> >         root=/dev/hda5
> >         append="hdb=ide-scsi hdc=ide-scsi"
> > 
> > [snip]
> > 
> > image=/mnt/hda10/boot/vmlinuz-2.4.13-1elx
> >         label=Elx_Linux_RC2
> >         read-only
> >         root=/dev/hda10
> >         append="hdb=ide-scsi hdc=ide-scsi"
> > 
> > 
> > 
> > On Sat, 23 Feb 2002 12:01:20 -0800 (PST)
> > Net Llama <[EMAIL PROTECTED]> wrote:
> > 
> > > --- Ken Moffat <[EMAIL PROTECTED]> wrote:
> > > > I have been using lilo, with my config file in my redhat7.1
> > > > install. I have been booting to redhat, modifying the
> > > > lilo.conf there to access changes in my setup (adding other
> > > > distros, etc) then running/sbin/lilo from there, making sure
> > > > to mount all effected partitions, then rebooting to access
> > > > other distros. My question is is this necessary? Can I have
> > > > lilo.conf in some neutral location which I can access and
> > > > modify from any other running distro, thereby eliminating the
> > > > need to boot redhat, then reboot?
> > > 
> > > Sure, see the lilo man page.  The -C switch lets you specify an
> > > alternate lilo.conf
> 
> =====
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Lonni J. Friedman                     [EMAIL PROTECTED]
> 
> Linux Step-by-step help:           http://netllama.ipfox.com
> 
>                                                  .
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Sports - Coverage of the 2002 Olympic Games
> http://sports.yahoo.com
> _______________________________________________
> Linux-users mailing list -
> http://linux-sxs.org/mailman/listinfo/linux-users
> Subscribe/Unsubscribe info, Archives,and Digests are located at the
> above URL.
> 


-- 
Ken Moffat
[EMAIL PROTECTED]
(remove _NO_SPAM_)!
_______________________________________________
Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users
Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.

Reply via email to