

Is it for the kernel or for the kernel documentation?


Is it for the kernel or for the kernel documentation?


Yeah, a closed source browser for Linux that interacts with an account-based search engine that promises not to sell your data doesn’t have any appeal to me. (And yes, I am a Kagi user as well.)
Why? Why is everybody renaming their project after years of building up reputation?


What I really want is NixOS, but with the Debian package repository.


Is this relevant when using built-in zstd compression on ZFS?
For Linux? Not at all. For PC related tech? Well, I find it entertaining, but I don’t find their content useful anymore.
It’s a jet for his company though, right?


Does this provide any advantage when you have enough fan/rgb headers on the mainboard already?


I think you need to look out for “OVMF”.
Alpine Linux is an independent, non-commercial, general purpose Linux distribution designed for power users who appreciate security, simplicity and resource efficiency.
https://www.alpinelinux.org/about/
It’s also around for 20 years already, so long before Docker was a thing. But setting it up as a desktop OS would be a bit of work, I agree.
I assume Alpine Linux is very limited in terms of power usage, at least out of the box.
I’m currently in the process to switching over to it.


Turn your laptop around and look for a sticker with a model number. Go to your vendor’s support website, search for the model number and check their BIOS/UEFI downloads. Usually it’s a file you put on a USB stick, then you boot into BIOS/UEFI (press F12 or DEL ob boot, check manual if in doubt), select BIOS/UEFI update and select the file on the USB stick.
It’s the same for desktop components. There are very few vendors/models that get BIOS/UEFI updates via Windows Update (or fwupd under Linux).

(Edit: Fixed image)


Honestly, don’t use hobby distros unless it’s just for testing purposes. They will fail you in the end, always.
That being said, if you want to check out another hobby distro, PikaOS is pretty fucking cool: https://wiki.pika-os.com/


https://docs.docker.com/engine/containers/run/#runtime-privilege-and-linux-capabilities
The --privileged flag gives all capabilities to the container. When the operator executes docker run --privileged, Docker enables access to all devices on the host, and reconfigures AppArmor or SELinux to allow the container nearly all the same access to the host as processes running outside containers on the host.
A manual
--device /dev/drishould not be necessary. I’ll make sure to test it nevertheless.


A strictly confined Snap by the original software authors? For sure. The available Snap on Snapcraft.io is by Canonical though, but that’d be fine as well, if I can not get my own solution to work. I’m just a bit puzzled that apparmor on Debian apparently simply doesn’t allow for strictly confined Snaps.


https://docs.docker.com/engine/containers/run/#runtime-privilege-and-linux-capabilities
The --privileged flag gives all capabilities to the container. When the operator executes docker run --privileged, Docker enables access to all devices on the host, and reconfigures AppArmor or SELinux to allow the container nearly all the same access to the host as processes running outside containers on the host.
A manual --device /dev/dri should not be necessary. I’ll make sure to test it nevertheless.


Thanks for the input, but I will probably never not want to use Steam and I’ve accepted non-free firmware blobs a long time ago. All I want is to use a simple sandbox like I use for many other applications (mostly as Docker containers).
Shouldn’t it have these distro maintainers thinking of quickly merging security fixes into their stable branches?