| 1 Mar 2023 |
 @kranzes:matrix.org | Yeah im really gonna enjoy these 4 or 5 hours haha 🙃 | 00:20:01 |
| @kranzes:matrix.org | * Yeah im really gonna enjoy these 4 or 5 hours of sleep haha 🙃 | 00:20:18 |
| 2 Mar 2023 |
|  @maxeaubrey:matrix.org changed their display name from maxine (they/them) to maxine. | 00:58:05 |
| 6 Mar 2023 |
 @elvishjerricco:matrix.org | alright back to the networkd branch... | 18:57:27 |
| @elvishjerricco:matrix.org | That's interesting... I see output from the openvpn command before I see systemd[1]: Starting openvpn.service... | 19:06:07 |
 @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
That's interesting... I see output from the openvpn command before I see systemd[1]: Starting openvpn.service... Is that in a NixOS test? I've noticed it too before in those and wondered if it had to do with the buffering the serial console grabber has (and it maybe interacting poorly with journald) | 19:14:41 |
| @elvishjerricco:matrix.org | yea it's a nixos test | 19:15:02 |
| @elvishjerricco:matrix.org | that could be the case | 19:15:15 |
| @elvishjerricco:matrix.org | this is all very nearly simultaneous | 19:15:22 |
| @elvishjerricco:matrix.org | Well, it appears I've got openvpn started and the ip address is set, but the server can't ping it.. | 20:21:31 |
| @elvishjerricco:matrix.org | * Well, it appears I've got openvpn started and the ip address is set, but the server can't ping it | 20:21:34 |
| @elvishjerricco:matrix.org | Oh. That might be because the non-systemd-initrd test is also failing to ping it... | 20:24:23 |
| @elvishjerricco:matrix.org | Derp. It's because I commented out the minimalboot stuff, which changed the DHCP lease ordering, so the numbers weren't hard coded right | 20:58:31 |
| @elvishjerricco:matrix.org | But, now that the test works, openvpn in initrd boots like 6 seconds faster for some reason | 20:58:51 |
| @elvishjerricco:matrix.org | Maybe because openvpn can start in parallel with nixos activation? | 20:59:13 |
| 7 Mar 2023 |
| @elvishjerricco:matrix.org | So in order to use networkctl, you need dbus, as far as I can tell. | 02:27:53 |
| @elvishjerricco:matrix.org | Ugh | 02:27:57 |
| @elvishjerricco:matrix.org | But NixOS supports two different dbus implementations so that makes it trickier to implement that | 02:34:23 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
But NixOS supports two different dbus implementations so that makes it trickier to implement that I mean, we could technically only support one for initrd, because it doesn't need to live past initrd, right? | 02:37:11 |
| @elvishjerricco:matrix.org | Possibly. Just feels a little disingenuous to tell the user they've replaced dbus with broker, but then not do that in initrd :P | 02:37:55 |
| @lily:lily.flowers | Yeah, that's fair | 02:38:42 |
| @elvishjerricco:matrix.org | it also just feels weird to have dbus in initrd at all | 02:39:00 |
| @elvishjerricco:matrix.org | I mean it'll be socket activated so the only cost will be size | 02:39:09 |
| @elvishjerricco:matrix.org | but still | 02:39:13 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
it also just feels weird to have dbus in initrd at all Yeah, it does a bit | 02:39:50 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
I mean it'll be socket activated so the only cost will be size I imagine broker is much smaller if you only want to support one, though... | 02:39:59 |
| @elvishjerricco:matrix.org | I imagine supporting either will be pretty minimal in terms of size | 02:40:22 |
| @elvishjerricco:matrix.org | Well... I removed the dbus-daemon binary from the initrd and networkctl still worked... The dbus.service failed, but networkctl didn't seem to care? | 03:06:42 |
| @elvishjerricco:matrix.org | wtf | 03:06:52 |
| @elvishjerricco:matrix.org | oh, just networkctl status worked; nothing else seemed to | 03:11:09 |
