Atemu

Yes. Low power draws add up. 5W here 10W there and you're already looking at >3€ per month.

Your home router probably has no clue where that is, so it goes to its upstream router and asks if they know, this process repeats until one figures it out and you get a route.

That's not how that works. The router merely sends the packet to the next directly connected router.

Let's take a simplified example:

If you were in the middle of bumfuck nowhere, USA and wanted to send a packet to Kyouto, Japan, your router would send the packet to another router it's connected to on the west coast*. From your router's perspective, that's it; it just sends it over and never "thinks" about that packet again.
The router on the west coast receives the packet, looks at the headers, sees that its supposed to go to Japan and sends it over a link to Hawaii.
The router in Hawaii again looks at the packet, sees that it's supposed to go to Japan and sends it over its link to Toukyou.
The router in Toukyou then sends it over its link to Kyouto and it'll be locally routed further to the exact host from there but you get the idea.

This is generally how IP routing works; always one hop to the next.

What I haven't explained is how your router knows that it can reach Kyouto via the west coast or how the west coast knows that it can reach Kyouto via Hawaii.
This is where routing protocols come in. You can look up how exactly these work in detail but what's important is their purpose: Build a "map" of the internet which you can look at to tell which way to send a packet at each intersection depending on its destination.

In operation, each router then simply looks at the one intersection it represents on the "map" and can then decide which way (link) to send each individual packet over.
The "map" (routing table) is continuously updated as conditions change.

Never at any point do routers establish a fixed route from one point to another or anything resembling a connection; the internet protocol is explicitly connectionless.

* in reality, there will be a few local routers between the gateway router sitting in your home and the big router that has a big link to the west coast

This isn't about copyright, it's about whether the software's purpose is to break DRM. Ninty argued that Yuzu's primary purpose is to enable copyright infringement which is forbidden under the DMCA; both infringement of course but also even just building tools to enable it. The latter is the critical (and IMHO insane) part.

Now, all of that is obviously BS but Ninty SLAPPed Yuzu to death, so it doesn't matter what's just or unjust; they win. God bless corporate America.

I am ashamed of GitLab.

Don't be. Gitlab has to comply with the law.

It's the law that's broken, not Gitlab.

It’s absolutely ridiculous they took it down even though Nintendo didn’t DMCA the Suyu project directly.

Um, no. If shitty corpo X (ab)uses the DMCA to send you a takedown notice for some project and you also host a fork of the same project, you must take down the fork too.

"You see, while this might be the exact same code, the name is totally different, so we don't have to take it down!" will not hold up in court.

Whether the DMCA request is valid or not is an entirely separate question. You must still comply or open yourself up to legal liabilities.

The process to object to the validity of the request is included in the screenshot.

Depends on how much of our needs would be covered. Not needing to work to survive is different from not needing to work to live a comfortable life which is again different from living a luxurious life.

Amen.

Could you upload the output of systemd-analyze plot?

I feel it was a direct reply to the comment above.

At no point did it mention livepatching.

Dinosaurs don’t want to give up their extended LTS kernels because upgrading is a hassle and often requires rebooting, occasionally to a bad state.

No, Dinosaurs want LTS because it's stable; it's in the name.

You can't have your proprietary shitware kernel module in any kernel other than the ABI it's made for. You can't run your proprietary legacy service heap of crap on newer kernels where the kernel APIs function slightly differently.

how can you bring your userbase forward so you don’t have to keep slapping security patches onto an ancient kernel?

That still has nothing to do with livepatching.

You probably could. Though I don't see the point in powering a home server over PoE.

A random SBC in the closet? WAP? Sure. Not a home server though.

.

10% worse efficiency > no refrigerator

Kernel livepatching is super niche and I don't see what it has to do with the topic at hand.