| 28 Jan 2023 |
 @elvishjerricco:matrix.org | swap file or device? And I'm assuming systemd initrd? | 19:35:14 |
 @lily:lily.flowers | Device and yes | 19:35:25 |
| @elvishjerricco:matrix.org | ah, LV, not file | 19:35:26 |
| @elvishjerricco:matrix.org | cool | 19:35:32 |
| @elvishjerricco:matrix.org | so then maybe a swap file thing... | 19:35:44 |
| @lily:lily.flowers | I'll also take a look at the issue later. I'm busy atm but I thought I would confirm that it does work for me | 19:38:22 |
| @elvishjerricco:matrix.org | thanks | 19:38:34 |
| @elvishjerricco:matrix.org | Hm, this is actually going to be kind of hard to write a nixos test for, because we probably can't realistically know the resume_offset= value at eval time | 21:24:46 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Hm, this is actually going to be kind of hard to write a nixos test for, because we probably can't realistically know the resume_offset= value at eval time Could you make it so the initrd put the value in /sys/power/resume_offset before systemd does the resume handling? That way it's not on kernel cmdline and so not needed at eval time but you'd have to generate the initrd from within the VM then. Unless someone knows a clever trick to make it easier | 22:19:36 |
| @elvishjerricco:matrix.org | It'd have to be a little different than that | 22:20:47 |
| @elvishjerricco:matrix.org | because the file system containing the swap file isn't actually mounted | 22:20:59 |
| @elvishjerricco:matrix.org | so we can't ask btrfs where its offset is in initrd | 22:21:07 |
| @elvishjerricco:matrix.org | we'd have to save it somewhere that initrd can read it from | 22:21:23 |
| @lily:lily.flowers | I did not mean auto-magicking the value from initrd. I mean in a VM figure out the offset and build a new initrd with the number baked in | 22:22:16 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
we'd have to save it somewhere that initrd can read it from But doing this could work too | 22:22:25 |
| @elvishjerricco:matrix.org | In reply to @lily:lily.flowers
I did not mean auto-magicking the value from initrd. I mean in a VM figure out the offset and build a new initrd with the number baked in Oh, well that would require IFD to read the output of the VM into a Nix expression | 22:23:01 |
| @lily:lily.flowers | In reply to @lily:lily.flowers
I did not mean auto-magicking the value from initrd. I mean in a VM figure out the offset and build a new initrd with the number baked in (A multi-stage test I suppose? Like the installer tests but less extreme) | 22:23:26 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
Oh, well that would require IFD to read the output of the VM into a Nix expression Why? | 22:23:31 |
| @elvishjerricco:matrix.org | builtins.readFile (runCommand "foo" {} "echo hi > $out") is technically IFD. Or, rather, the same basic internal mechanism | 22:24:06 |
| @lily:lily.flowers | Nix doesn't need it. But your idea of saving it on another disk is better | 22:24:14 |
| @elvishjerricco:matrix.org | oh wait | 22:24:23 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
builtins.readFile (runCommand "foo" {} "echo hi > $out") is technically IFD. Or, rather, the same basic internal mechanism Nix doesn't need the number in what I was offering | 22:24:28 |
| @elvishjerricco:matrix.org | oh, you mean like build a whole new initrd in the vm | 22:24:39 |
| @elvishjerricco:matrix.org | not build it as a nix expression | 22:24:46 |
| @lily:lily.flowers | Yes | 22:24:48 |
| @elvishjerricco:matrix.org | neat | 22:24:48 |
| @elvishjerricco:matrix.org | I think saving it somewhere the initrd can read it would be easier though | 22:24:58 |
| @lily:lily.flowers | I'm sorry for being a tad unclear 😅 | 22:25:00 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
I think saving it somewhere the initrd can read it would be easier though It would yes. I like that idea better | 22:25:13 |
| @lily:lily.flowers | * It would, yes. I like that idea better | 22:25:28 |
