There are some strange things with dracut and jessie:
I updated from kernel 3.14 to 3.16 and get this:
root@somesystem:~# ls -la /boot/
total 124782
drwxr-xr-x 2 root root 10 Oct 1 19:41 .
drwxr-xr-x 21 root root 25 Oct 1 19:41 ..
-rw-r--r-- 1 root root 153354 Aug 9 05:20 config-3.14-2-amd64
-rw-r--r-- 1 root root 155429 Sep 20 17:58 config-3.16-2-amd64
-rw------- 1 root root 25622848 Sep 13 21:27 initramfs-3.14-2-amd64.img
-rw------- 1 root root 26193738 Oct 1 19:42 initrd.img-3.16-2-amd64
-rw-r--r-- 1 root root 2470383 Aug 9 05:20 System.map-3.14-2-amd64
-rw-r--r-- 1 root root 2664913 Sep 20 17:58 System.map-3.16-2-amd64
-rw-r--r-- 1 root root 2985856 Aug 9 05:12 vmlinuz-3.14-2-amd64
-rw-r--r-- 1 root root 3102192 Sep 20 17:47 vmlinuz-3.16-2-amd64
root@somesystem:~# ls -la /init*
lrwxrwxrwx 1 root root 29 Oct 1 19:41 /initrd.img ->
/boot/initrd.img-3.16-2-amd64
lrwxrwxrwx 1 root root 31 Sep 13 20:37 /initrd.img.old ->
boot/initramfs-3.14-2-amd64.img
The initrd is now initrd and not initram any more.
After changing the symlink from absolute to relative path and rebooting the
system I was running dracut.
dracut didn't need --force and made this:
root@somesystem:/# dracut
root@somesystem:/# ls -la /boot/
total 176019
drwxr-xr-x 2 root root 11 Oct 1 21:27 .
drwxr-xr-x 21 root root 25 Oct 1 21:26 ..
-rw-r--r-- 1 root root 153354 Aug 9 05:20 config-3.14-2-amd64
-rw-r--r-- 1 root root 155429 Sep 20 17:58 config-3.16-2-amd64
-rw------- 1 root root 25622848 Sep 13 21:27 initramfs-3.14-2-amd64.img
-rw------- 1 root root 26165201 Oct 1 21:28 initramfs-3.16-2-amd64.img
-rw------- 1 root root 26193738 Oct 1 19:42 initrd.img-3.16-2-amd64
-rw-r--r-- 1 root root 2470383 Aug 9 05:20 System.map-3.14-2-amd64
-rw-r--r-- 1 root root 2664913 Sep 20 17:58 System.map-3.16-2-amd64
-rw-r--r-- 1 root root 2985856 Aug 9 05:12 vmlinuz-3.14-2-amd64
-rw-r--r-- 1 root root 3102192 Sep 20 17:47 vmlinuz-3.16-2-amd64
Now I have:
initramfs-3.16-2-amd64.img
initrd.img-3.16-2-amd64
But I have still:
root@somesystem:/# ls -la /init*
lrwxrwxrwx 1 root root 28 Oct 1 21:26 /initrd.img ->
boot/initrd.img-3.16-2-amd64
lrwxrwxrwx 1 root root 31 Sep 13 20:37 /initrd.img.old ->
boot/initramfs-3.14-2-amd64.img
dracut uses different names on kernel updates and manual updates.
But the symlink is not updated and points to the wrong initrd.
I think dracut should always use the names of the old initram packages like the
kernel uses, too.
-------- Original Message --------
Subject: Re: Bug#763653: dracut make use of absolute path in soft link
"/initrd.ing" instead of relative (01-Okt-2014 23:11)
From: Thomas Lange <la...@informatik.uni-koeln.de>
To: debian....@zengel.org
> >>>>> On Wed, 01 Oct 2014 15:49:00 +0000, Grischa Zengel <debian.bug@zengel.
> org> said:
>
> > After update it looks like:
> > root@xenserver1:/# ls -la /srv/nfs/xen/asterisk.donner14.private/
> initrd.img*
> > lrwxrwxrwx 1 root root 28 Sep 28 19:13 /srv/nfs/xen/asterisk.donner14.
> private/initrd.img -> /boot/initrd.img-3.16-2-amd64
> >
> ^
> > lrwxrwxrwx 1 root root 28 Sep 28 14:44 /srv/nfs/xen/asterisk.donner14.
> private/initrd.img.old -> boot/initrd.img-3.14-2-amd64
>
> I also recognize that this symlink changes from wheezy to jessie. In
> wheezy this is a relative symlink, in jessie it's an absolute symlink.
>
> But I guess it's not dracut, that creates this symlink. I cannot find
> the code in dracut that creates this symlink.
>
> --
> regards Thomas
>
> To: "Grischa Zengel" <debian....@zengel.org>
>
> 763...@bugs.debian.org
>
> Cc:
To: la...@informatik.uni-koeln.de
debian....@zengel.org
763...@bugs.debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
