At the moment, i have an hd with:

hda1: xperience
hda2: fat32 partition
hda4: debian
hda5: knoppix ( something is really well configured )
hda6: linux swap.

Without knoppix, i was able to boot xp or debian without problems. Now i would like to add knoppix to the lilo menu, so i've added the line:

other=/dev/hda5
label="Knoppix"

to lilo.conf. But when i do lilo -v, it replies that it's not bootable ( but after i've installed knoppix, it worked - but no debian... )

Is there a way to do so?

Thx in adv.

p.s. my lilo.conf

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda4

append="hdd-ide-scsi"

default=Linux

image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img

image=/vmlinuz.old
label=LinuxOLD
read-only
optional

other=/dev/hda1
label="WinNT(hda1)"

well no the partition is not bootable, lilo is right, that is what lilo is for, making it bootable.... you nee da correct entry in lilo for it, not just an "other" entry. with a lilo.conf as bleak as that i'm suprised anyting boots.

i think i've cutted too much: here is the real lilo.conf

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81

#disk=/dev/sda
# bios=0x80

# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda4

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
# prompt
# single-key
# delay=100
# timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="hdd-ide-scsi"

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
label=Linux
read-only
initrd=/initrd.img
# restricted
# alias=1

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
other=/dev/hda1
label="WinNT(hda1)"

ok that looks a lot more sane. so you still need a REAL entry for the other distro. as far as the image= line goes though it DOES need to be an existing path where you are, so assumgin that your other distro is all just in that one parition then you need to mount it to somewhere, suh as /knoppix/ inside debian and then use THAT path to point to the image on the other distro. afaik what actually happens is that the physcial location of the file you point to is stored in teh boot loader so whtn you go to that boot loader it simply start directly execting the code at that specified address. once youinstall lilo you won't ever ned to mount /knoppix again (unless you want to change lilo)

Now i've inserted

image=/mnt/knoppix/vmlinuz
label=Knoppix
read-only
#initrd=/initrd.img

And it starts with the knoppix kernel ( it's a 2.4.19 instead of a 2.4.18 ), but i can't locate the initrd ( that is't in /mnt/knoppix/boot )

So in fact it starts debian with the 2.4.19 kernel.