Bug#917261: linux-image-4.19.0-1-amd64: /dev/mapper symlink for dm-crypt volume containing / not created on system startup

[Celejar]

On Wed, 26 Dec 2018 15:39:19 +0000
Ben Hutchings <ben at decadent.org.uk> wrote:

> On Tue, Dec 25, 2018 at 09:58:33PM -0500, Celejar wrote:
> > On Tue, 25 Dec 2018 20:52:46 +0000
> > Ben Hutchings <ben at decadent.org.uk> wrote:
> > 
> > > Control: reassign -1 udev 240-1
> > > Control: forcemerge 917124 -1
> > > 
> > > This seems to be a bug in udev, not the kernel.  You will only have
> > > noticed it once you rebooted for the kernel upgrade.
> > 
> > Nope - in my system's current state, when rebooting into 4.19 there's
> > no /dev/mapper symlink, but when rebooting into 4.18 there is. I've
> > gone back and forth several times, and the behavior is consistent.
> > There's clearly something that 4.19 is doing differently from 4.18. [I
> > guess it might still be a udev bug, which is being exposed by some
> > change in 4.19.]
> 
> This is probably because the initramfs for 4.18 contains the old
> version of udev.

Okay, I think I understand. So if I were to update the 4.18 initramfs
(with update-initramfs -k 4.18-nnn) now, I would expect to see the same
problem with that kernel?

Celejar