Put your /boot under 1GB and put everything needed to boot all your OSes inside /boot, including all boot sectors from other OSes AND silo.conf (put a symlink /etc/silo.conf -> /boot/silo.conf). The reason is that silo reads its conf file at runtime (meaning that you don't need to re-run silo when you change silo.conf, but also meaning you must keep it under 1GB, hence the need to put it under /boot).
After you do that, don't point silo.conf to a symlink to the kernel, but to the kernel proper, so that you don't confuse silo (maybe a symlink to the kernel works if both are on the same partition and it's a relative symlink, but I haven't tried that). so if your /boot is sdX and your kernel is in /boot/vmlinux-2.2.17, put image=X/vmlinux-2.2.17 Regards, Leo On Fri, 25 Aug 2000, Thomas 'Balu' Walter wrote: > +-Ben Collins-([EMAIL PROTECTED])-[25.08.00 16:46]: > > On Fri, Aug 25, 2000 at 03:52:45PM +0200, Thomas 'Balu' Walter wrote: > > > > > > Which does not give me an error (/boot is sda1, / is sda2). > > > > > > > Do not put /boot on a seperate partition. It confuses silo. Either that or > > put this as the image in silo.conf > > > > image=2/vmlinuz > > That did not work. Is there another way to get silo running ? > > I need that as explained before to get a partition below the 1G-Border > where I can leave the different kernels of the different systems. > > IMHO Silo won't install a kernel if it is below this border, so doing > one /-partition for Debian will not work, because the LFS-/ would not be > below that...