InitramFS Generation with Paired Bluetooth Device Metadata

[tunix]

    > > > Would this also work for allowing bluetooth at LUKS decryption screen?

For that, I think you'd be better served by rpm-ostree initramfs --enable. And you'll likely also want to add --arg=--add --arg=bluetooth.

Unfortunetely that only includes files inside /etc but not /var/lib/bluetooth so you miss the paired device metadata.

Gotcha. Thanks for bringing this up. We currently don't expose /var to dracut but it could make sense to do so for use cases like this. Can you file a separate issue for this?

Originally posted by @jlebon in #1930 (comment)

As we discussed in above thread, currently it's possible for us to include bluetooth modules inside the generated initramfs image. Since it doesn't include files inside /var/lib/bluetooth, it's not possible to use bluetooth keyboards during LUKS decryption.

[cgwalters]

One complexity here is that inherently you end up with two copies of the data. And so anytime the bluetooth pairing is changed, the initramfs would need to be regenerated - even outside an OS update.