firmware drivers
This sounds like you're talking about firmware blobs that the kernel drivers load, which are usually in a package called linux-firmware. It should be updated automatically, but I'll check in the morning with Fedora Silverblue.
Otherwise if you're talking about device firmware, than that's all fwupd, rpm-ostree has nothing to do with that.
Idk about the UK, but in Australia if you're only sending a small amount of data, some carriers offer IoT plans starting at ~$1/month. So maybe some carriers do the same in the UK?
If you're wondering what this is:
- Add a power quirk for Framework systems
It's to do with the fact that Framework laptops report themselves as discharging when they're actually fully charged, and BIOS updates aren't allowed when discharging.
But to answer your question, I've been using it with my Framework 13 AMD, and haven't had any issues. Fwupd is officially supported by Framework themselves, and is mentioned on the BIOS upgrade guides.
I've got one of the official Home Assistant SkyConnect dongles, and I just stick to the IKEA ZigBee stuff, most other ZigBee devices should work too though.
Pretty useless unless you use KDE, but I really like KDE's widgets.
Running Windows is officially supported by Apple, yes most guides use bootcamp to set it up, but you should be able to create an install drive like a normal PC and boot from it by holding Option/Alt as you press the power button. Mac's usually just use EFI like any modern PC under the hood.
Nah, bootcamp assistant is Apple's dual boot setup tool, it is a native install, but it has to be started from MacOS.
TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process
They don't even need to be the same process. I'm pretty sure that's just a common practice if something needs both protocols, but there's nothing stopping you from having a web server on TCP 443 and a VPN server on UDP 443. Ports are an abstraction brought by each protocol, they aren't in anyway related.
Probably because there's also permission to use the X11 socket.
Not exactly the same, but an electron beam puts a lot of noise in the image: https://youtu.be/Uf4Ux4SlyT4
Also I've heard the international space station gets a lot of dead pixels on their cameras from cosmic radiation.
The options that start with
HAVE_usually depend on the arch or compiler. I don't believe it's possible to enable manually without modifying the source itself.