No.

(Que conste que lo intenté)

  • 3 Posts
  • 99 Comments
Joined 5 months ago
cake
Cake day: April 9th, 2026

help-circle










  • lambisio@feddit.cltoTechnology@lemmy.mlProton announces widespread outages
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    16
    ·
    10 days ago

    I don’t know qhat bot farm you get that many upvotes from but you really need to do more research.

    That was one guy (their CEO) expressing his personal support for one thing Trump did. Proton released a statement claiming that their company as a whole does not support any political stance or affiliation.

    The first part was a statement that was backed by the board (this after the CEO guy doubled down on supporting Trump when questioned).

    The second part almost merits no explainer: saying you are “neutral” on politics is the same as saying you favour those why already have the power - the oligarchs and those who maintain the status quo.








  • 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.



  • 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.