On Tue, Mar 16, 2004 at 09:59:14PM +0100, Sven Luther wrote: > Also, Colin said he would have a look at this this evening, so we will > know tomorrow about it.
OK, I built kernel-patch-2.4.25-powerpc without your postinst hack. (Incidentally, this is just how it builds by default. If you want to have a postinst hack, it *must* be in the source package or in a build-dependency, not just a local change on your system, otherwise people won't be able to rebuild it correctly. It would be very embarrassing if a kernel security update broke d-i!) It seems to install successfully: [EMAIL PROTECTED]:/tmp# dpkg -i kernel-image-2.4.25-powerpc-pmac_2.4.25-2_powerpc.deb kernel-modules-2.4.25-powerpc_2.4.25-2_powerpc.deb Selecting previously deselected package kernel-image-2.4.25-powerpc-pmac. (Reading database ... 8747 files and directories currently installed.) Unpacking kernel-image-2.4.25-powerpc-pmac (from kernel-image-2.4.25-powerpc-pmac_2.4.25-2_powerpc.deb) ... Selecting previously deselected package kernel-modules-2.4.25-powerpc. Unpacking kernel-modules-2.4.25-powerpc (from kernel-modules-2.4.25-powerpc_2.4.25-2_powerpc.deb) ... Setting up kernel-modules-2.4.25-powerpc (2.4.25-2) ... Setting up kernel-image-2.4.25-powerpc-pmac (2.4.25-2) ... depmod: *** Unresolved symbols in /lib/modules/2.4.25-powerpc/kernel/drivers/sound/kahlua.o /boot/vmlinux does not exist. Installing from scratch, eh? Or maybe you don't want a symbolic link here. Hmm? Lets See. [EMAIL PROTECTED]:/tmp# ls -l /boot/vmlinux lrwxrwxrwx 1 root root 22 Mar 17 09:11 /boot/vmlinux -> vmlinux-2.4.25-powerpc Can you clarify the problem with leaving the symlink code in? I don't seem to be seeing it. If I can reproduce it then I stand more chance of fixing it. This image puts the symlink in /boot/vmlinux. I think just /vmlinux would be better, since that's what kernel-package does by default so it'll be more compatible with people's locally-built kernels: my locally-built kernels have been using /vmlinux without me giving any special directions. However, if it stays as /boot/vmlinux then yaboot-installer needs to be told about it. > I think maybe it would be more interesting to fix yaboot-installer > instead so it doesn't rely on the symlink being present, but fall back > to using the real kernel in case the symlink is missing, this would > add more robustness to the whole process. I'm not keen on that idea. The resulting system wouldn't be upgradeable as smoothly if its yaboot.conf hardcoded the kernel-image version rather than using the symlink, which would be an unexpected kick in the teeth for people doing kernel security updates. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
