You can't mix and match the version of lilo (the executable) and boot.b
(which is part of lilo).
So, instead of:
lilo -r /mnt/xyz
use:
chroot /mnt/xyz /sbin/lilo
-Tom
On Thu, 13 Sep 2001, Piet van Unen wrote:
> Date: Thu, 13 Sep 2001 16:27:34 +0200
> From: Piet van Unen <[EMAIL PROTECTED]>
> To: tom <[EMAIL PROTECTED]>
> Subject: [tomsrtbt] lilo -r on suse
>
> Dear Tom,
>
> I installed Tomsrtbt on hda3. On hda1 a suse 7.0 is running kernel 2.2.16. I
>installed lilo with a suse tool Yast1 and it boots hda1 correct.
> I added tomsrtbt to /etc/lilo.conf while running suse:
> ...
> #suse
> image = /boot/vmlinux
> root = /dev/hda1
> label= suse
> #tomsrtbt-1.7.361
> image =/hd3/zImage
> root =/dev/hda3
> label= tom
>
> I did :
> # mount /dev/hda3 /hd3
> # lilo
> Added suse*
> Kernel /hd3/zImage is to big
> #
>
> I suppose I have to compress this kernel. How can I do that?
>
> After that I tried to run lilo from diskette under tomsrtbt
> I did:
> # mkdir /tmp/hd1
> # mkdir /tmp/hd3
> # mount /dev/hda1 /tmp/hd1
> # mount /dev/hda3 /tmp/hd3
> #
> #lilo -r /tmp/hd1
> First bootsector doesn't have a valid LILO signature
> #
>
> Why this answer?
> I tried:
> #chroot /tmp/hd1 ls
> #
>
> No answer
> and:
>
> #chroot /tmp/hd1
> Segmentation fault
>
> What is wrong? Can you help me?
>
> --Piet
>
