Hi,
> Both filesystems and LVM have UUIDs. Does dm-crypt / LUKS have one too?
LUKS, of course, has UUID, plain dm-crypt of course not... :-)
bye,
--
piergiorgio
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
Hi,
> Indeed, it does. However, I could not find out how it does device
> naming? From what I understand, mdadm will only assemble devices
> using the name stored in the superblocks iff the homehost matches,
> so dracut either doesn't provide for this and requires the use of
> UUIDs to mount files
Hi,
> True. You'd have to update the superblock UUID right after creation
> of the filesystem. That doesn't sound like a robust strategy to
> making mdadm.conf optional.
it seems that, with "dracut", "mdadm.conf" is optional.
There is the kernel boot paramenter "rd_NO_MDADMCONF",
which forces "d
3 matches
Mail list logo
