 | NixOS + Framework | 233 Members |
| Discussing NixOS in the context of the Framework laptop | 53 Servers |
| NixOS + Framework | 233 Members |
| Discussing NixOS in the context of the Framework laptop | 53 Servers |
| Sender | Message | Time |
|---|---|---|
| 10 May 2026 | ||
 trumee | yes, that seems a good way forward | 15:59:01 |
 sudoforge | it's a rather strange way forward | 16:05:50 |
| sudoforge | but, yes, it should get you there | 16:06:13 |
| sudoforge | i'm not really sure how boot.resumeDevice is going to play with that | 16:06:48 |
| sudoforge | what you could do instead, is encrypt the entire disk (except your ESP partition if using systemd-boot) and within the unlocked container, set up your different filesystems | 16:07:42 |
| sudoforge | that's what i'd call far more typical on single-disk installations | 16:08:09 |
| trumee | why do you think this is strange? | 16:09:46 |
| sudoforge | well, what does it accomplish? | 16:10:35 |
| sudoforge | you increase complexity and gain, what? | 16:10:42 |
| sudoforge | well, and we should probably clarify: are you using a framework laptop with a single disk for your system, or are you using multiple disks? | 16:11:56 |
| trumee | yes, i have a single disk. | 16:12:07 |
| sudoforge | okay, yeah, i'm going to call it strange then | 16:12:22 |
| trumee | My goal is to use Yubikey to decrypt the disk. | 16:12:24 |
| sudoforge | you can just do that, directly, on the single luks container that is your entire disk (sans your ESP partition if using systemd-boot) | 16:12:50 |
| sudoforge | i do this on my FW13 | 16:13:07 |
| trumee | i was using ZFS encryption instead of using Luks. | 16:13:19 |
| sudoforge | no, you're using luks for your keyfile and then using that for zfs | 16:13:53 |
| sudoforge | based on: https://discourse.nixos.org/t/yubikey-fido2-and-boot-initrd-systemd/60051/18?u=trumee | 16:14:10 |
| sudoforge | anyway, what i've described is far simpler | 16:15:09 |
| sudoforge | you are welcome to continue doing what you're doing, of course | 16:15:21 |
| sudoforge | this is what a single luks container containing various partitions (which in this case all happen to be btrfs, but could be a disparate | 16:16:31 |
| sudoforge | * this is what a single luks container containing various partitions (which in this case all happen to be btrfs, but could be a disparate | 16:16:34 |
| trumee | that is more accurate, my goal was to use native zfs encryption when i set the system up. | 16:16:52 |
| sudoforge | * this is what a single luks container containing various partitions looks like (which in this case all happen to be btrfs, but could be a disparate | 16:16:54 |
| sudoforge | * this is what a single luks container containing various partitions looks like (which in this case all happen to be btrfs, but could be a disparate | 16:17:33 |
| trumee | this is what i have currently, | 16:18:38 |
| sudoforge | do you see and understand the difference? | 16:20:41 |
 Albert Larsan | I have something even more complex (ignore p3 and p4, an old dual boot) | 16:24:37 |
| sudoforge | well ignoring partitions 3 and 4, we have basically the same core setup: a single luks container that contains our filesystems | 16:25:31 |
| sudoforge | this is really more telling, i guess: | 16:26:23 |