[pkg-cryptsetup-devel] Bug#838001: Bug#838001: cryptsetup does not support ZFS

[Guilhem Moulin]

Control: severity -1 wishlist

On Mon, 19 Sep 2016 at 08:21:13 -0500, Richard Laager wrote:
> On 09/19/2016 07:21 AM, Guilhem Moulin wrote:
>> Interesting, worksforme™ both with gawk(1) and mawk(1).  Perhaps an
>> issue with TAB vs spaces?  Could you redirect the output of `zfs status
>> -P $pool` to a file and attach that file instead of copy-paste the
>> output?
> 
> I'm using mawk. File attached.

I see.  My bad, I thought the leading tabs were spaces.
 
>> Hmm, swapping /etc/fstab for /proc/self/mounts seems like a major
>> change, with potential undesired consequences.  Up to now the device
>> associated to a given mountpoint was the one found in fstab(5), which is
>> not necessarily the one currently mounted.
> 
> That's why I didn't do this originally. Changing to /proc/self/mounts is
> a simpler/clearer, but more significant/riskier code change.
> 
> If you want to maintain the semantics of "what is configured" rather
> than "what is mounted", then the only way to support ZFS is to call `zfs
> list`. That is how you find out "what is configured" in ZFS.

I'll wait for Jonas' opinion on bypassing /etc/fstab in a FS-specific
manner.  In the meantime I'm decreasing the severity to wishlist since
adding ‘initramfs’ to the 4th field of the crypttab(5) entry of each
underlying device is enough to provide root FS encryption for arbitrary
file systems (assuming the initrd can mount it).

-- 
Guilhem.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20160919/f0ae20af/attachment.sig>