[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#795139: Softlink target path for /initrd.img is different from /vmlinuz



On Tue, 2016-02-16 at 20:40 -0800, Martin Michlmayr wrote:
> reassign 795139 linux
> thanks
> 
> * Anders Andersson <pipatron@gmail.com> [2015-08-11 00:05]:
> > This is a bug so minor, that I am embarassed to report it. It has, however,
> > bugged me for some time now. After a fresh install of debian jessie, the
> > softlinks from /initrd.img and /vmlinuz points to different locations:
> > 
> > lrwxrwxrwx   1 root root   31 Aug 10 22:20 initrd.img ->
> > /boot/initrd.img-3.16.0-4-amd64
> > lrwxrwxrwx   1 root root   27 Aug 10 22:20 vmlinuz ->
> > boot/vmlinuz-3.16.0-4-amd64
> > 
> > Notice how one is to "/boot" (absolute path) and one is to "boot" (relative
> > path).
> 
> I believe this is because one is generated by the kernel and one by
> initramfs-tools.  I'm reassiging the bug to the kernel so someone
> can comment.
[...]

Both symlinks are created by the kernel postinst scripts.  I'm
intending to move that functionality to linux-base, at which point I'll
rewrite it completely because the current code is unsalvageable.

Ben.

-- 
Ben Hutchings
Lowery's Law:
             If it jams, force it. If it breaks, it needed replacing anyway.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: