| 14 Aug 2024 |
 SigmaSquadron | * Hi all. Is there a way to ensure a certain disk is processed first in a disko configuration? I have a detached-header LUKS setup that encrypts my internal disks and writes their headers to an USB device. Disko does encrypt both devices, but it processes the USB last, and it does so by deleting the headers and repartitioning. Is there a way to ensure it formats the USB before installing the headers?
Sorry, I was looking for the priority option.
| 21:20:49 |
| SigmaSquadron | So, the priority option doesn't seem to reorder disk partitioning, only the partition creation order. | 21:22:24 |
| SigmaSquadron | actually, it might not be a partitioning issue, just some disk weirdness: | 21:50:31 |
| SigmaSquadron | 
Download IMG_0596.png | 21:50:41 |
| SigmaSquadron | i'm using this disko configuration: | 21:55:12 |
| SigmaSquadron | Download partitioning.nix | 21:55:18 |
| SigmaSquadron | Something is up with udev; the disk ID isn't a link to /dev/sdb. Not a disko issue though.
| 22:20:47 |
| SigmaSquadron | * Something is up with udisks; the disk ID isn't a link to /dev/sdb. Not a disko issue though.
| 22:20:56 |
| 16 Aug 2024 |
|  @glaringweakness:nope.chat left the room. | 02:06:20 |
| 17 Aug 2024 |
|  ·☽•Nameless☆•777 · ± changed their profile picture. | 08:27:42 |
 pxc | oops, I'm in this channel and forgot it existed | 22:23:52 |
| pxc | is anyone here having success testing disko installation on using --test-vm on macOS? | 22:25:11 |
| 18 Aug 2024 |
| pxc | * is anyone here having success testing disko installation on using --vm-test on macOS? | 00:17:15 |
| pxc | ok so I guess what I want to happen is for when I run nixos-anywhere ... --vim-test on a Mac, I want it to build the VM on an aarch64-linux remote builder, but then run the final test (boot the thing and whatever) by running qemu directly on the Mac.
But right now that test lives inside the nixosConfiguration, as <machine>.system.build.installTest, which means of course that it is also aarch64-linux, so that final qemu invocation is still running under my aarch64-linux builder
which sucks because that doesn't have any working qemu accelerators other than tcg
| 00:26:46 |
| pxc | * ok so I guess what I want to happen is for when I run nixos-anywhere ... --vm-test on a Mac, I want it to build the VM on an aarch64-linux remote builder, but then run the final test (boot the thing and whatever) by running qemu directly on the Mac.
But right now that test lives inside the nixosConfiguration, as <machine>.system.build.installTest, which means of course that it is also aarch64-linux, so that final qemu invocation is still running under my aarch64-linux builder
which sucks because that doesn't have any working qemu accelerators other than tcg
| 00:26:53 |
| pxc | for now I'm doing my local testing a little more manually, with some customized install media that mounts the repo containing my NixOS config using a VirtFS share
if I can figure it out, though, would moving disko to use pkgs.nixosTest instead of make-test-python.nix as its entrypoint for NixOS vm-tests, and then modifying nixos-anywhere.sh to support running that test locally be an agreeable change?
| 17:00:19 |
| pxc | * for now I'm doing my local testing a little more manually, with some customized install media that mounts the repo containing my NixOS config using a VirtFS share and includes disko and nixos-anywhere on it
if I can figure it out, though, would moving disko to use pkgs.nixosTest instead of make-test-python.nix as its entrypoint for NixOS vm-tests, and then modifying nixos-anywhere.sh to support running that test locally be an agreeable change?
| 17:00:51 |
| pxc | * for now I'm doing my local testing a little more manually, with some customized install media that mounts the repo containing my NixOS config using a VirtFS share and includes disko and nixos-anywhere on it
if I can figure it out, though, would moving disko to use pkgs.nixosTest instead of make-test-python.nix as its entrypoint for NixOS vm-tests, and then modifying nixos-anywhere.sh to support running that test locally when it is used on macOS hosts be an agreeable change?
| 17:01:40 |
