| 20 Mar 2025 |
 Arian | Not sure | 10:02:19 |
 @elvishjerricco:matrix.org | the sysfs thing? That only works for sysfs nodes that actually represent devices, which is only a subset of sysfs | 10:14:27 |
| Arian | Ah | 10:18:47 |
| Arian | Then just order it later like https://man7.org/linux/man-pages/man8/systemd-sysctl.service.8.html | 10:19:42 |
| Arian | Surprised there isn't a systemd-sysfs | 10:19:50 |
| Arian | I guess best we can do is load after systemd-modules-load | 10:20:14 |
| @elvishjerricco:matrix.org | hm, currently tmpfiles and modules-load are unordered against each other | 10:23:51 |
 gdamjan | but even if you load a module, the sysfs knobs are not guaranteed to be available immediately right? modules initialize asynchronously | 13:29:29 |
|  @derrg:matrix.org joined the room. | 17:33:52 |
| Arian | Should the Systemd team be on nixos.org/community | 18:34:34 |
| 21 Mar 2025 |
|  mrdev023 joined the room. | 13:51:10 |
| 22 Mar 2025 |
| @elvishjerricco:matrix.org | I am finding some extremely broken behavior with systemd-repart running during boot when the device is already partitioned but needs modification (e.g. grow a partition). It seems that when it runs and repartitions, it causes the device units to stop and start. This causes fsck and mount units to be stopped, all the way up to initrd-fs.target, causing initrd-find-nixos-closure.service to be stopped. Then initrd-parse-etc.service starts and that starts initrd-fs.target again, but initrd-find-nixos-closure.service is still stopped, so it never happens and the system fails to boot | 09:10:18 |
| Arian | Wut | 09:12:19 |
| @elvishjerricco:matrix.org | now, all those units being stopped is a "job canceled", so they don't need to have already been started for this chain reaction to occur | 09:12:43 |
| @elvishjerricco:matrix.org | * now, all those units being stopped is a "job canceled" scenario, so they don't need to have already been started for this chain reaction to occur | 09:12:49 |
