| 18 Aug 2024 |
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 |