NixOS systemd | 618 Members | |
| NixOS ❤️ systemd | 173 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Mar 2025 | ||
after repart finishes, I see Changed plugged -> dead for each of the partitions in the systemd debug logging, and then immediately after I see Changed dead -> plugged for them | 09:23:12 | |
|
then I get a
And then I get
| 09:23:57 | |
*
then I get a
And then I get
| 09:24:15 | |
I feel like this can't possibly be right, because then imagine what happens with a normal stage 2 repart service. It would repartition, and immediately cancel all mount jobs depending on those partitions, stopping local-fs.target | 09:26:43 | |
| Is Dev/vda3 mounted at this point? | 09:27:35 | |
| no | 09:27:41 | |
| Maybe you only get these events for unmounted partitions | 09:27:59 | |
| well that would still be the case in stage 2 | 09:28:25 | |
| for any non-root partitions | 09:28:28 | |
| That would explain why it doesn mess with the root fs. But it would indeed screw things up for anything else in fstab | 09:28:34 | |
| I think I'm going to take my eyes off this problem for a bit and get some sleep. Arian Do you have any interest in taking a glance at my test config in the meantime? | 09:30:29 | |
| (it's using my fancy "installer-small" nixos test setup that makes installer tests way way more efficient) | 09:30:58 | |
| Yah send a link. I might have a look later | 09:32:01 | |
| Though I'm gonna do some touristic stuff with @flokli:matrix.org first | 09:32:13 | |
| Arian: https://github.com/ElvishJerricco/nixpkgs/commits/installer-small/ The last commit probably breaks all the other ones so if you're interested in the installer-small stuff check out the one before it. But the last one contains the repart test case | 09:37:23 | |
| * Arian: https://github.com/ElvishJerricco/nixpkgs/commits/installer-small/ The last commit probably breaks all the other ones so if you're interested in the installer-small stuff check out the ones before it. But the last one contains the repart test case | 09:37:34 | |
| 23 Mar 2025 | ||
| If I assign a non-existent slice to a service, will it be created with default values or return an error? | 02:42:45 | |
| I dont remember | 09:22:13 | |
| Try it out? | 09:22:20 | |
| soooo how long is scripted initrd going to be a thing? I have a truly annoying (semi-guaranteed to be racy) nixos test for scripted, and would love to get rid of it someday | 23:39:24 | |
| I have not made as much time as I usually do for nixos stuff since 24.11, so systemd by default in 25.05 is unlikely, again :( | 23:44:41 | |
| plus I've been sidetracked by a couple other nixos things like the ISO | 23:45:08 | |
| understandable yet sad | 23:45:13 | |
| no worries, I'm gonna figure this out one way or the other | 23:45:24 | |
| can you think of a good way to halt the boot process in scripted initrd until a condition is met? I have been trying
and it sure seems to stop the boot but you don't get output from the machine in case anything goes wrong... | 23:46:42 | |
| yea that's, uh... a good use case for systemd initrd :P | 23:48:41 | |
| random idle musing: what's the right way to express dependencies between services, that says service A needs to be running, but should also be restarted whenever service B starts or stops? Use case:
| 23:50:32 | |
| * random idle musing: what's the right way to express dependencies between services, that says service A needs to be running, but should also be restarted whenever service B starts or stops? Use case:
| 23:50:39 | |
| (B might get split into separate power state and import state units, but that's not really important for this question. I want to restart smartd around the disks either arriving or leaving | 23:52:17 | |
| * (B might get split into separate power state and import state units, but that's not really important for this question. I want to restart smartd around the disks either arriving or leaving) | 23:52:21 | |