Okay I have figured it out.
It was something "hidden" in the udev rules, and a mistake on my part.
LFS doesn't seem to follow the "everything into /usr/bin", and so they
were moving "lvm" into /usr/sbin (a separate folder).
Inspecting the udev rules led me to notice that it was calling
"/usr
Nevermind, that log was apparently from shutdown and not boot.
The issues I'm experiencing were actually because ifupdown was still being
used for network-online.target. I've disabled that and now everything
properly waits for systemd-networkd.
On Thu, Aug 28, 2025 at 12:15 PM Sanjay Vasandani
w
I'm having an issue where systemd-networkd fails with "Could not set
hostname" on initial startup/boot, but succeeds if I manually restart it
after with `systemctl`.
>From `journalctl -u systemd-networkd`:
```
Aug 28 11:34:17 ruyi systemd[1]: Stopping systemd-networkd.service -
Network Configurati
Hi !
Indeed I'm 100% aware that this is not the "ideal setup", I'm simply
curious as to why it isn't working right. I'd like to get my small
init to work well with lvm/udev/systemd.
As per your advice, I added -vvv to vgchange and does seem to confirm
your idea that it is waiting for the cookie.
