I think the other takeaway here is that it was found in a section marked "unsafe". At the very least, that's a useful tool for the Devs to isolate potential problem areas. Comparing that to a pure C codebase where the problem could be anywhere.

Is this not the equivalent of asking someone on the street to pay for a fence for your property so you don't have to look at them?

They made an init system called systemd, and it worked way better than anything prior.

Then they realised that to have a functional and maintainable system, you need a bunch of other system level tooling to be in and around about the same layer as the unit system (time sync, base network, disk mounting, etc.). All of these other things got spun off as daemon projects, for example "systemd-timesyncd". And all got good and consistent command line tooling that made things relatively convenient.

The downside is now power-users saw systems taking over their computer and "violating the Unix philosophy". I would argue that at some level, it doesn't. They've made a suite of relatively independent tools all part of the same group with the purpose of managing the system. It gets things running, it gets users logged in and out, it tells you what when wrong, and it will restart things if it can. System management, do one thing and do it well.

I think the fact is that managing a modern system in a way that "just works" is complicated challenge. Many people either haven't run Ubuntu 9, and done a software update, or have repressed a lot of those memories.

Is it perfect: no. Is it the best model we have so far: I would say so.

We have similar kinda of boxes in Australia, usually they are monitoring stations for the energy infrastructure provider. Can be cellular or long range radio links.

Start using and efistub and never worry about boot loaders again!

You need to get little bud a new shirts every few months with an extra spiderman pointing each time!

If you execute a parent, you end up with living or zombie children that you need to find and put down.

"Aircons don't work without power, or for people with no access to power"

we were hacked.

How?

The remote code execution step of our toolchain was used to run remote code.

Linux has native AMD drivers, no need for anything extra!

Easy. Pico Henry. Not sure why chemists are so concerned with such a small amount of magnetism though...

Also a good spot for sunglasses!

I think you might be underestimating uptake. Google suggests upwards of 50% usage. Also I'm fairly certain that a lot of residential infrastructure has been slowly moving to IPv6 in Australia at least. Not an overnight process, but it's happening. Over here we have a lot of newer mobile plans offering IPv6 as well.

I think a big holdback is that a lot of larger corporations will still use IPv4/NAT setups at the top level, even if all of the hardware in the network supports it. "If it's not broke don't fix it." The result is huge amounts of daily traffic coming from these institutions being IPv4 by default, with all devices in WiFi, etc, being lumped into the same group.

Not sure about mpv, but I use a gstreamer pipeline to tender cameras to the raw KMS terminal display. It works much more reliably (I.e. Predictable loading times and no stutter) compared to loading a DE first. Noting that it was on a low power RPI.

They're using FPGAs.

Puppy Linux might be an option if that project is still going.

The people here talking about a display server (x11/Wayland) are missing your point I think. If you put a display server on this "box" then it will become a normal server, not a headless one. At that point, you may as well run a full VM and have the output go wherever you want, etc. I'm not sure what the equivalent is in the docker world, but I'm pretty sure that's not what you're asking for.

Is it possible for you to get SSH running on this "server"? If so, you may be able to set it up with an SSH client on the host PC (the laptop?) that is full screen on the CRT/HDMI output?

Maybe I'm misunderstanding as well though. Any headless server I've used in Linux will still give you a TTY on the display. Do you not get that? Someone else mentioned Getty, which is likely the service that is managing that. You should be able to configure Getty to give you a specific tty (e.g. tty9) on a specific output, then configure it either to autologin or to run a script on that tty.

The reality is that a bootloader will seemingly always be needed to account for difficult BIOS' and legacy setups (I'm looking at you, dual-booted Ubuntu 20.04).

Time to move to AV1!

It's true, that's how it's said down here! Usually by fans more so than just generally.