| 15 Sep 2024 |
 colemickens | I found it a bit tricky to do this right, how can I better specify these partition start/ends that don't leave such awkward gaps: https://github.com/colemickens/nixcfg/blob/06d838e8abe1392433c3ddf08cff23da381f7cee/hosts/h96maxv58/base.nix#L80-L110 | 21:39:51 |
 lassulus | You can do start = 0. sgdisk will choose the next free block then | 21:51:07 |
| lassulus | Which is also the default | 21:51:16 |
| colemickens | the problem with start=0 is ordering | 22:02:24 |
| colemickens | esp with it hoisting ESP to be partition 1 | 22:05:37 |
| colemickens | well I don't know why ESP is being made first, maybe it's alpha sorted by default (since I'm using EF00 not EF02). anyway, I'll set priority. Now just looking for growpart. | 22:18:42 |
| colemickens | I keep doing it by hand and forgetting to set the part label and causing myself a lot of pain. | 22:18:59 |
| colemickens | oh I guess that's a system-level nixos option. hm | 22:34:51 |
| colemickens | I seriously love disko so much. I wish I could fund someone to make a non-VM install process, with lanzaboote, bootspec, etc. I don't think it's that outlandish. If one could compose images with cross-compiled systems without needing to involve qemu, that would just be "end-game". | 22:51:10 |
| colemickens | still, doing a native build, using disko, and then pivoting to a cross-built system is still such a nicer experience than sdcard or other things people do to get nixos on weird platforms. I'm excited to use it for ec2 image as well. | 22:52:21 |
| 16 Sep 2024 |
 arjan5 | colemickens Not sure if it's what you're looking for, but nixos-anywhere can install different-arch systems remotely, even for configs containing disko, lanzaboote, impermanence, etc. I have done this before. | 09:12:30 |
| lassulus | Lanzaboote needs interaction with the efi/bios to deploy your keys there. But I guess everything else could be done by the image builder | 12:43:32 |
