| 12 Apr 2022 |
@elvishjerricco:matrix.org | I had the qemu-vm module configured to port forward the guest's port 22 to the hosts 2222, so I just did nc -l 22 on the guest and nc localhost 2222 on the host, and they're communicating without issue | 12:20:41 |
@elvishjerricco:matrix.org | * I had the qemu-vm module configured to port forward the guest's port 22 to the host's 2222, so I just did nc -l 22 on the guest and nc localhost 2222 on the host, and they're communicating without issue | 12:20:48 |
@elvishjerricco:matrix.org | So I guess SSH would probably work? | 12:21:05 |
@elvishjerricco:matrix.org | But yea I'm going to have to get rid of some of these default systemd orderings | 12:21:32 |
@elvishjerricco:matrix.org | What happens if I.... | 12:23:55 |
| * @elvishjerricco:matrix.org eyes DefaultDependencies=no | 12:24:01 |
| @janne.hess:helsinki-systems.de invited lassulus. | 17:32:51 |
| @janne.hess:helsinki-systems.de invited Dennis. | 17:33:10 |
@arianvp:matrix.org | You want to start networkd earlier? | 17:33:31 |
@janne.hess:helsinki-systems.de | In reply to @arianvp:matrix.org You want to start networkd earlier? Makes sense for iscsi and friends | 17:33:43 |
@janne.hess:helsinki-systems.de | Ah and for unlock via ssh of course | 17:33:48 |
| lassulus joined the room. | 17:33:49 |
@arianvp:matrix.org | networkd alreayd starts quite early | 17:34:39 |
@elvishjerricco:matrix.org | Yea I think unlocking disks via ssh is the most common use I've heard of people using networking in initrd for | 17:34:48 |
@arianvp:matrix.org | iscsi and friends should be pulled in by remote-fs.target which runs after networkd | 17:34:54 |
@arianvp:matrix.org | if not there's something wrong with your fstab | 17:35:00 |
@elvishjerricco:matrix.org | I think it has default dependencies so local-fs has to be reached first | 17:35:10 |
@arianvp:matrix.org | networkd has no Defaultdependencies | 17:35:18 |
@elvishjerricco:matrix.org | Oh? I must've missed that | 17:35:31 |
@arianvp:matrix.org | DefaultDependencies=no
# systemd-udevd.service can be dropped once tuntap is moved to netlink
After=systemd-networkd.socket systemd-udevd.service network-pre.target systemd-sysusers.service systemd-sysctl.service
Before=network.target multi-user.target shutdown.targe
| 17:35:37 |
@elvishjerricco:matrix.org | Either way, it doesn't seem to be started before my disk unlock prompt | 17:36:03 |
@arianvp:matrix.org | if your disk does not mark that it needs network that makes sense | 17:36:23 |
@arianvp:matrix.org | https://www.freedesktop.org/software/systemd/man/bootup.html see the part about remote-fs.target | 17:37:17 |
@elvishjerricco:matrix.org | But if it doesn't have default dependencies it shouldn't have any reason to wait for the disk | 17:37:25 |
@elvishjerricco:matrix.org | (On mobile right now; can check better in a minute) | 17:37:41 |
@arianvp:matrix.org | but it pulls in systemd-sysusers.target which pulls in Wants=local-fs-pre.target | 17:39:04 |
@arianvp:matrix.org | and a local-fs.target | 17:39:20 |
@arianvp:matrix.org | Before=local-fs.target* | 17:39:23 |
@arianvp:matrix.org | so it waits for the rootfs to be mounted so it can create the systemd-networkd user? | 17:39:41 |
@arianvp:matrix.org | (makes sense in my head) | 17:39:55 |