Do silo realy care which partition the kernel is on? I think the problem here is that you give silo a soft link that points to something which is not mounted yet.
Try 1/vmlinuz-2.2.17 or whatever your real kernel file name is relative to the /boot partition root Regards, /Karl ----------------------------------------------------------------------- Karl Hammar Aspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57 Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting ----------------------------------------------------------------------- From: "Thomas 'Balu' Walter" <[EMAIL PROTECTED]> Subject: Re: Unable to find /vmlinuz on an IPX Date: Fri, 25 Aug 2000 17:36:45 +0200 > +-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... > > Balu > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
