bug#70826: luks-device-mapping-with-options breaks bootloader

2024-08-11 Thread Tadhg McDonald-Jensen
2024 at 6:33 PM Tadhg McDonald-Jensen wrote: > I have attached a config I just did `sudo guix system reconfigure` > and confirmed it was missing the `insmod luks` in /boot/grub/grub.cfg > > Sorry for the delay, > Tadhg McD-J > > On 2024-07-23 2:19 p.m., Tomas Volf wrote: &

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-08-11 Thread Tadhg McDonald-Jensen
I have attached a config I just did `sudo guix system reconfigure` and confirmed it was missing the `insmod luks` in /boot/grub/grub.cfg Sorry for the delay, Tadhg McD-J On 2024-07-23 2:19 p.m., Tomas Volf wrote: > On 2024-05-25 10:30:49 -0400, Tadhg McDonald-Jensen wrote: >> That unfo

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-05-25 Thread Tadhg McDonald-Jensen
tially but it didn't work on my previous attempt so I abandoned trying to submit a patch, but this version does do the trick even if it seems inelegant. On 2024-05-25 5:47 a.m., Ludovic Courtès wrote: Hi, Tadhg McDonald-Jensen skribis: using the `luks-device-mapping-with-options` mapp

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-05-13 Thread Tadhg McDonald-Jensen
using the `luks-device-mapping-with-options` mapped device type defined in (gnu system mapped-devices) causes grub or other bootloaders to not properly attempt to mount the encrypted drive. This is caused by the commit 39a9404 which identifies luks mapped devices by checking if the type is equal to