Gnome shenanigans.
The most hilarious part about how Anubis is implemented is that it triggers challenges for every request with a User-Agent containing “Mozilla”.
If you have JavaScript disabled, this “challenge” is just a wall. They might’ve stopped bots, but they’ve stopped me too.
“Meant to” and “do” are quite different.
I have, not once, ever had an issue caused by a update while the system was online. And if someone did, they could likely reboot to fix it.
I will stick to the online, instantaneous, and unobstructing updates.
I would like to see some real-world numbers and examples of problems that offline updates fix.
I’m excited for my cursor to not get trapped in a window anymore.
On Wayland at least, u can completely disable pointer constraints. Thus, a game window freezes, it doesn’t lock your cursor in it.
With X11, the only solutions I found were basically recompiling the X11 code. Thus, I deal with one game window making my cursor disappear and frozen inside itself, affecting all other Xwayland windows.
Annoying and ridiculous. Hopefully not long before wine-wayland matures enough to fix this.
Linus already has a backup. Its Greg Kroah-Hartman.
It can be done if you mess with the initramfs.
The kernel starts everything else by unpacking an archive containing a minimal environment to set stuff up for later. Such as loading needed kernel modules, decrypting your drive, etc. It then launches, by default, the /init program (mines a shell script).
That program is PID 1. If it dies, your kernel will panic.
After it finishes setup, it execs your actual /sbin/init. These means it dies, and that program (systemd, openrc, dinit, runit, etc) becomes PID 1. If an issue happens, both could fail to execute and the kernel will loop forever.