Hi,
we use our own kernel rpms. Installing them on a SLES10 SP1 system after AY finished works fine, it also works when selecting them for a SuSE 10.1 installation with AY (using the SLES10 SP1 installer (kernel/initrd)).
But when installing a SLES10 SP1 system and trying to select our own kernel rpm as kernel package in AY, the generation of lilo.conf fails. It ends up like
image = nts/instsys/boot/vmlinuz-2.6.16-12suse-bio-smp label = SLES_10_SP1 initrd = nts/instsys/boot/initrd-2.6.16-12suse-bio-smp
In y2log I find: 2008-02-12 12:34:37 <1> 141.84.1.24(3834) [YCP] Bootloader.ycp:590 section SLES_10_SP1: converting old kernel parameter from /boot/vmlinuz to nts/instsys/boot/vmlinuz-2.6.16-12suse-bio-smp 2008-02-12 12:34:37 <1> 141.84.1.24(3834) [YCP] Bootloader.ycp:590 section SLES_10_SP1: converting old initrd parameter from /boot/initrd to nts/instsys/boot/initrd-2.6.16-12suse-bio-smp
Uwe, do you have any idea what could go wrong here?
cu, Frank
Frank Steiner wrote
Uwe, do you have any idea what could go wrong here?
Ok, got it. There is some new code in BootLoader.ycp compared to 10.1 to replace symlinks in lilo.conf. I've no idea why this makes sense, why not leave "image=/boot/vmlinuz" in lilo.conf instead of replacing it with "image=/boot/vmlinuz-bla-blu" etc.?
Anyway, the code fails when the link in /boot is absolute, although the comment states that "readlink -m" should solve this. Our kernel.rpm creates
lrwxrwxrwx 1 root root 35 Feb 12 13:07 vmlinuz -> /boot/vmlinuz-2.6.16-12suse-bio-smp
But since /boot points to /mounts/instsys/boot, readlink -m returns this:
inst-sys:~ # readlink -m /mnt/boot/vmlinuz /mounts/instsys/boot/vmlinuz-2.6.16-12suse-bio-smp
I will change our kernel.rpm to use relative links, but I guess the code in Bootloader.ycp should be debugged :-)
cu, Frank
autoinstall@lists.opensuse.org
-
Frank Steiner