Replying to @noahm@lemmy.world
Yes, distros make different choices about the systems they want to use. That’s the way distro work. If you don’t like it, choose a different flavor of ubuntu or a different distro altogether. Nobody’s being forced to do anything they don’t want here. What’s the alternative? Everybody just does everything exact the way some armchair developers or Arch cultists have decided is the best way for them? No thanks.
Replying to @mycodesucks@lemmy.world
That’s not what the articles says or implies at all. The article only refers to another article with a click bait headline. The article article summarizes Canonical stance like this:
And to be clear, including a tool or default workflow is MILES away from patronizingly forcing it on to users. It’s just the way that most distros that aren’t Linux From Scratch work.
Replying to @SuspiciousCarrot78@aussie.zone
The idea is to have the server safely shutdown BEFORE it loses power, so that BIOS setting wouldn’t mean anything. The server does not loose power while it it running, so it will never “restore last state after AC loss”. The idea is that you can run a low power device (the raspberry pi) for which you don’t care if power is cut abruptly and that can talk to both the UPS and the wake-on-lan of the server directly over ethernet. It being local means those WOL are much more likely to work than trying to send them from outside your network when you’re remote. It’s a lot simpler to set this up once than it is to recover a server with a corrupted file system due to power loss or lose access to your server for weeks because a thunderstorm knocked out power for 30min at the beginning of a long trip. That pi can also take care of other always on services like a pi-hole, home assistant, etc.
According to the article it was royalty free and published open standards, but they do not make any claim to this being an FOSS system.