| 14 Aug 2024 |
 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 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 |
|  preisi joined the room. | 21:48:15 |
| 19 Aug 2024 |
| preisi | (Hopefully) quick question: How does disko handle changes to the disk-configuration of a running system? From my understanding, the partitioning/formatting is only done when actually executing disko (which shouldn't be done automatically by e.g., nixos-rebuild). But is the generated filesystem config stable enough for it to handle it? (It's using /disk/by-partuuid as far as I understood so it should be okay?)
Or are there any destructive (inter)actions by/through disko that I need to be aware of for productive usage? :) | 09:37:03 |
|  tmarkov joined the room. | 20:19:21 |
| tmarkov | Hi! I'm using disko for partitioning, with btrfs subvolumes on luks. Now I manually created a new subvoume, and added it to the disko config. But after rebuilding, it wasn't added to fstab for some reason, and doesn't get mounted. Is there some catch that I could be missing there? | 20:33:24 |
 lassulus | hard to say without the config, but in theory it should get mounted if you add it there | 20:42:03 |
| 20 Aug 2024 |
 matthewcroughan | lassulus: https://github.com/nix-community/disko/pull/740 | 09:22:31 |
| matthewcroughan | dunno how this was missed | 09:22:33 |
| matthewcroughan | just nobody using it I guess | 09:22:56 |
| lassulus | the format is called f2fs-tools? | 09:23:08 |
| matthewcroughan | oops | 09:23:47 |
| matthewcroughan | it passed the vm test though | 09:24:02 |
| matthewcroughan | wtf | 09:24:04 |
| matthewcroughan | how is that possible | 09:24:22 |
