mainline kernel initrd symlink bug

[Daniel J Blueman]

On 5 November 2013 06:57, Andy Whitcroft <apw at canonical.com> wrote:
> On Tue, Nov 05, 2013 at 06:35:18AM +0800, Daniel J Blueman wrote:
>> There's an issue with the mainline kernels using an absolute path in
>> the /initrd.img symlink they create, breaking certain setups, eg PXE
>> booting:
>>
>> # ls -l /
>> initrd.img -> /boot/initrd.img-3.12.0-031200-generic
>> initrd.img.old -> boot/initrd.img-3.11.0-12-generic
>> vmlinuz -> boot/vmlinuz-3.12.0-031200-generic
>> vmlinuz.old -> boot/vmlinuz-3.11.0-12-generic
>>
>> When the TFTP server derefs the initrd.img symlink from the directory
>> the rootfs it is in, it fails to find the initrd.
>>
>> How can I address this issue?
>
> I am somewhat supprised that those links are actually built in a different
> way.  It is not as if those files are even part of the package afterall.
> They are made during install by the postinst.  I assume they are installed
> in a different way as a result of your manually doing the install, that
> might affect it.  You could experiment with hand installing an official
> package the exact same way you do those and see if it also suffers.
> That might make it an apt-get against dpkg difference.

It turns out that this is also an issue for the distro kernels as well
as mainline (since they have the same scripts), so I analysed and
logged it at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248053
.
-- 
Daniel J Blueman