Wouldn’t it be more efficient in that case to have some sort of remote* suspend+resume? Saves you the hassle of the bootup and shutdown procedure, when suspend saves most of the relevant energy.

[*] where “remote” can be “hook a tripwire from your room to the keyboard”, at least for the wakeup

If they cared they should have finished sooner

Eh, the only kind of server that I think you absolutely need full networking (address, iptables, routing, maybe even DNS) to be “meaningful” would be a database replica. Anything else, there is full use to partial network configuration: anything small enough that lets in a network connection someone else can use to diagnose (eg.: you can have a server that can spin up a meaningful session with only address and netmask, not routing).

That said, I’ve never seen a server, with or without systemd, set to wait for all possible network interfaces that are present to be fully configured… would me emotional murder with something like wireguard that by necessity has a depends on another interface’s routing. Usually with just lo plus any one available interface, it tends to suffice.

clean shutdown

on systemd

https://feddit.cl/post/13051330

Don’t mask or disable the systemd service.

Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.

That’s absolutely systemd’s fault. In any Linux system the only network interface that can (more or less) always trusted to be available and complete a full initialization sequence is lo Absolutely nothing else.

(The worse if you happen to have a WiFi that autoconnects but does it across the same SSID to different endpoints, but that one is wpa_supplicant’s fault if I’m not mistaken. Systemd just makes it worse)

Not onl that but they usually remove the init script as well, so unless you go for archives you no longer have a sane mechanism for starting and stopping the service.

Fortunately Debian has a orphaned-init-scripts package that can help alleviate that pain, as you can also use those scripts (or even better, openrc scripts) as skeletons to replace systemd service units.

What, not any of the other stuff?

Like the same locking wait message, but on startup because of wifi

2026

complaining about em-dashes

You are completely ignorant about where do AIs even get their data from, yes?

A free knowledge cookie for you:

The em-dash is the language standard sign in Español for dialogue tags. Literally.

You don’t need a knife to make a knife, and things like OCR are different from AI (or from “AI”).

FUCK IT THEY GOT PAPERLESS-NGX TOOO???

Fedis, what’s the best alternative?