> > It turned out, that /boot/initrd.img.old was pointing to 2.6.30-2 > > instead of -1 (embarrassing). So this problem is solved and unrelated. > > The -1 kernel now boots with the new image fine. So the remaining > > problem might be unrelated to cryptsetup. > > ok cool, thus closing. > > initramfs-tools is not messing with symlinks. better use grub > it does not use symlinks. > thanks for the report.
Well, I was the one who messed with the symlinks. I hope I haven't lost all my credibility with this stupid mistake. However the real and remaining problem is a initramfs for 2.6.30-2 that doesn't boot (wasn't stated properly in my previous email). The old initramfs for -2 (initrd.img-2.6.30-2-powerpc.bak) boots as well as both -1 images. I guess a new subject would be: "initramfs-tools: Boot with 2.6.30-2-powerpc hangs before break=mount." Should I file a new bug report for this or should I reopen this bug report? –Adam
signature.asc
Description: PGP signature
