[pkg-cryptsetup-devel] Bug#961671: Bug#961671: Renaming crypttab mapping

[Guilhem Moulin]

Control: severity -1 minor

Hi Ed,

On Wed, 27 May 2020 at 10:17:36 -0600, Ed Schaller wrote:
> When I first encountered this long before the bug was submitted I
> found a easier/safer way.

README.initramfs §11 certainly has shortcomings and doesn't pretend to
cover all cases, but note that your solution doesn't cover all cases
either:

> dmsetup rename old_name new_name
> 
> update the initramfs
> 
> update-initramfs -uk all

The device might be identified by /dev/mapper/old_name rather than UUID
in /etc/fstab, /etc/initramfs-tools/conf.d/resume, kernel command line,
or other places, in which case the rename needs to be performed there
too.

> As far as the currently booted system goes, it already sees the new names,

/proc/mounts appears not to though, and that's we use to identify the
source device in our hook scripts.  So `update-initramfs -u` will
complain that it can't find the root device if /dev/mapper/old_name is
used directly as the root file system.  The current instructions are
more robust in that regard.

Cheers,
-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20200601/dd2c885a/attachment.sig>