On Mon, 2014-05-05 at 20:39 +0200, Karsten Merker wrote: > As can be seen above, the kernel package does not create symlinks in > /boot. It creates symlinks in /, but as it is possible (and sometimes even > necessary, e.g. with encrypted root) to have /boot on a seperate filesystem, > these are unusable in a boot script.
Hrm, I thought if /boot was separate the symlink would be made in /boot, so /vmlinuz of the boot device (whether that was / or /boot) was always valid. Seems like I was wrong -- I have two systems with separate /boot, and one has the symlinks in / the other in /boot (and I only looked at the second last time around). I think I must have some tweaks to /etc/kernel-img.conf (specifically to link_in_boot) which I'd forgotten about, sorry for that. This does make me wonder if f-k with your patch needs to be more careful about overwriting /boot/vmlinuz in case it is a symlink. Ian. -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399317426.19277.247.ca...@hastur.hellion.org.uk
