Post #3548723

Somebody please ELI5 to me why Ubuntu's systemd refuses to boot a system if ANY network interface is not currently connected to a network, with an UNLIMITED timeout. It's not (just) that I still have to remember to systemctl mask systemd-networkd-online-wait. I want to know what the hell was this idea about in the FIRST place--and why, after *years* of this idiocy, is it still in place? Who wanted this? And why? What "problem" was it meant to solve? Who wants their system to NOT BOOT?