Very Computer

My lilo.conf with which I've installed LILO is included below. I'm trying
to make /dev/hdb2 (linux) boot with a default  SCSIKERN image, stored in
/vmlinuz on that partition; and make /dev/hda3 (linux2) boot with a
custom-compiled kernel (also called /vmlinuz, but stored instead on the
root of  /dev/hda3.)

I've  correctly taken the steps to make each of the two '/vmlinuz' files
into bootable images but LILO still seems to  want to use the SAME
image regardless which partition is being booted. That image is,
namely, the particular /vmlinuz from whichever partition LILO was last
installed.

This seems to imply that "image=/vmlinuz" is actually a part of the
GLOBAL LILO configuration within a system....  can somebody set me
straight on this?

-------------------------------------------------

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
delay = 300
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hdb2
  label = linux
  append = " ncr5380=0x358,254,-1"
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda3
  label = linux2
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
  label = dos
  table = /dev/hda
# DOS bootable partition config ends

-------------------------------------------------

Sincerely,
        Dan M.

I may be wrong here, but inorder for LILO to boot another kernel,
that image must be available directly to lilo when it is installed/
updated. What I mean by this is that you'd have to have the other
drive mounted (say /mnt, for example), then use 'image = /mnt/vmlinuz'
as the other labeled image.  If this is way off, i apologize, but i think
this is how i managed to setup an option to boot from a kernel image
on a Linux-formatted floppy mounted on /mnt 'image=/mnt/vmlinuz'

--

Computer Science        Youngstown State University

Youngstown, OH:  All the *, crime & * of New York at half the cost!

: I may be wrong here, but inorder for LILO to boot another kernel,
: that image must be available directly to lilo when it is installed/
: updated. What I mean by this is that you'd have to have the other
: drive mounted (say /mnt, for example), then use 'image = /mnt/vmlinuz'
: as the other labeled image.  If this is way off, i apologize, but i think
: this is how i managed to setup an option to boot from a kernel image
: on a Linux-formatted floppy mounted on /mnt 'image=/mnt/vmlinuz'

   Lilo must be able to find the image you're trying to install before
you install lilo..  If lilo config's correctly, then all should be well.
While booting, I don't think it matters if the drive is mounted,
seeing as nothing is _mounted_ at the time.  Lilo just needs to know
where your kernel image is located on the drive so it knows where
to started executing code.  

   Back to the origonal message, if you want to boot multiple kernel
images, you must have multiple images in your lilo.conf file.  I'm not
on my Linux box right now to give you an example; perhaps someone
else can post one.  But with multiple images in lilo.conf, and all
kernels available to lilo when you install, everything should work
ok.  

--
Mark Smith                      |         ___ O    

KD6JTS                          |      |/\___/        
--------------------------------+---------------------
"Why won't Windows work on my Macintosh?"
        - The ultimate DFO error

: Can someone offer me a reason why it is that LILO always boots with the
: _same_ kernel image , no matter which linux partition I'm booting from?

[snip]

: This seems to imply that "image=/vmlinuz" is actually a part of the
: GLOBAL LILO configuration within a system....  can somebody set me
: straight on this?

I have been, in fact, set straight; my confusion was in thinking that the
dereference of '/vmlinuz' was done at boot- rather than install-time.

** sigh **  maybe we unix user '1-newbies' should stick to DOS
(no tomatoes, please) 'til Novell comes out with their commercial version
of Linux....

----                                                        ----
-    "I don't know exactly how 'Linux' should be pronounced.   -
-     I only know it should be pronounced more often."         -
----                                                        ----