How do I get other installed OS's?

[rrfish72]

I have Kanotix, Knoppix, windowsxp, windows 98 installed on my computer. But I cannot get to the kanotix install because it is not one of the OS choices. How do I get it to be on the lilo boot screen? If I install kanotix again then I cannot get to the knoppix system? How do I get knoppix to be one of the grub choices if I do that? I would rather use grub.

[CrashedAgain]

I have Kanotix, Knoppix, windowsxp, windows 98 installed on my computer. But I cannot get to the kanotix install because it is not one of the OS choices. How do I get it to be on the lilo boot screen? If I install kanotix again then I cannot get to the knoppix system? How do I get knoppix to be one of the grub choices if I do that? I would rather use grub.
Here is my lilo.conf which boots seversl operating systems on different partitions. I had to manually enter all but the Knoppix on hda5 & windows. The lilo is actually generated from knoppix on hda5. It gives an error if hda1 & 8 are not mounted when lilo is run.
You should be able to do a similar manual entry for your kanotix wherever it is installed.
Sorry I know nothing of grub.



boot=/dev/hda
map=/boot/map
vga=normal
default="Linux(new)"
prompt
nowarn
timeout=100
menu-scheme=wb:bw:wb:bw
lba32

#boots knoppix on hda5 2.4 kernel
image=/boot/vmlinuz-2.4.26
label="Knoppix24"
root=/dev/hda5
initrd=/boot/initrd.img-2.4.26
append="lang=us apm=power-off ramdisk_size=100000 init=/etc/init nomce quiet nofstab wheelmouse alsa"
read-only

#boots knoppix on hda5 2.6 kernel
image=/boot/vmlinuz-2.6.6
label="Linux(new)"
root=/dev/hda5
initrd=/boot/initrd.img-2.6.6
append="lang=us apm=power-off ramdisk_size=100000 init=/etc/init nomce hdc=scsi nofstab wheelmouse alsa"
read-only

#boots mandrake 9.2 on hda8
image=/mnt/hda8/boot/vmlinuz
label="Linux(old)"
root=/dev/hda8
initrd=/mnt/hda8/boot/initrd.img
append="devfs=mount hdc=ide-scsi acpi=ht resume=/dev/hda6"
read-only

#boots windows
other=/dev/hda1
label="Windows"
table=/dev/hda

# boots a poormans install on hda1
image=/mnt/hda1/bootlinux/isolinux/linux24
label="backup"
initrd=/mnt/hda1/bootlinux/isolinux/minirt24.gz
append="home=scan myconfig=scan fromhd=/dev/hda1"

[jjmac]

Howdy rrfish72

>>
I have Kanotix, Knoppix, windowsxp, windows 98 installed
on my computer. But I cannot get to the kanotix
install because it is not one of the OS choices.
How do I get it to be on the lilo boot screen?
>>

You probably just need to add it to you lilo.conf,
then as root run "lilo" to update its' map file.

Insidently, the map file will likely be found
in the same directory as the one which houses the kernel.

With lilo, when you alter the lilo.conf file, as per a
kernel/OS addition, you need to have the directory
that holds the kernel mounted. So that lilo can map
its' location. This is a disk mapping, not a
mount mapping. So it dosen't matter where you mount the
directory. Usually this means that every install that
lilo will be dealing with needs to be mounted somewhere.
But thats not strickly true. If you use a sepeerate boot
directory, to house all your kernels, then that will
be the only one needed to be mounted. Other OSs' don't
require this. I guess the chain loader looks after this
somehow.

Not updating lilo is the most common thing thats
ever overlooked.


Hey Crashed, howdy ...

I noticed that you have some of your kernels assigned
to the "image" keyword using "/mnt" as part of its'
path. It dosent really matter, but you don't really
need to do that. As far as having them mounted to
update lilo, the root path is sufficient. That
is; you can mount them anywere. The mapping dosen't
involve the actual mount point, for the mapping,
if that makes sense :).
The mount point is just a fs abstaction, for our
benifit. It dosen't effect the actual "sector"
location on disk. Which is all lilo needs to know.

jm

[CrashedAgain]

Hey Crashed, howdy ...

I noticed that you have some of your kernels assigned
to the "image" keyword using "/mnt" as part of its'
path. It dosent really matter, but you don't really
need to do that. As far as having them mounted to
update lilo, the root path is sufficient. That
is; you can mount them anywere. The mapping dosen't
involve the actual mount point, for the mapping,
if that makes sense :).
The mount point is just a fs abstaction, for our
benifit. It dosen't effect the actual "sector"
location on disk. Which is all lilo needs to know.

jm

Right, it shouldn't matter...but it did. Or at least as I remember it seemed to. I had a bit of a time trying to get the Mandrake system to work, it seemed like it was trying to load the Knoppix kernel then mount /hda8 as root & use the Mandrake setups until I added the complete path to the image.

[jjmac]

That does sound strange. So many people seem to
have problems with Mandrake, so i guess it's not
to surprising.

It may have just been a symlink thing. That is,
two links with the same name.

Iv'e found using a common boot partition
simplifies things a lot, when it comes to updating
Lilo's map file. I use a 100 Mb partition, hdb1,
and mount it on /boot, just for the update. I leave
it unmounted normally. It's just a matter then of
remembering to directly copy the relevant system.map
files over to root's boot directory.

Just to make the module/symbol table detection
at boot go smoothly.

Not to worry though :)

jm