| 10 May 2026 |
 sudoforge | * and 3. you should probably set content.enrollRecovery = true; (doing this will require formatting your disk if you want disko to apply it, but you can also just manually add a recovery passphrase) | 22:23:01 |
 trumee | yes, i changed in disko. And doing a reinstall. | 22:26:48 |
| trumee | do i need boot.loader.systemd-boot.enable = true; for fido2 support? | 22:30:40 |
| sudoforge | uh, i've been using systemd-boot as my bootloader for far too long | 22:32:33 |
| sudoforge | so | 22:32:35 |
| sudoforge | i have no idea if grub (or whatever else you're using currently?) supports fido2 devices for unlocking encrypted volumes | 22:33:02 |
| trumee | ok, i will enable it. i am not using grub | 22:34:56 |
| sudoforge | you'll want to explicitly disable grub then | 22:35:07 |
| sudoforge | boot.loader.grub.enable = lib.mkForce false; | 22:35:21 |
| sudoforge | boot.loader.systemd-boot.enable = true; | 22:35:39 |
| sudoforge | also, you're well past the point that has anything to do with framework specifically (in fact, your initial question about which filesystem to use that would play well with hibernation wasn't framework-specific either), so i'm going to recommend / suggest that you move further generic-nix-and-nixos questions to #users:nixos.org | 22:49:18 |
| sudoforge | there is a much larger pool of people that can help you there | 22:49:37 |
| sudoforge | * i have no idea if grub (or whatever else you're using currently?) supports fido2 devices for unlocking encrypted volumes. i mean, it should just delegate to cryptsetup, so probably? | 22:55:09 |
| 11 May 2026 |
|  alanxoc3 joined the room. | 10:49:12 |
|  funzen joined the room. | 20:10:30 |
|  Kazucroco joined the room. | 21:34:48 |
| 12 May 2026 |
|  Awaiz Azam joined the room. | 00:20:55 |
|  define9293 joined the room. | 02:10:00 |
| 13 May 2026 |
|  snowflake joined the room. | 12:28:51 |
