This is awesome work, I’m happy to see systemd on musl getting more attention. Poor Khem was doing it all by himself for years.

Baby Mammoth - Another Day at the Orifice

Gotta have blue hair

San Diego

I don’t know if this is still the case, but IIRC browsers (chrome and Firefox) have their own sandboxing which is quite effective, but their efficacy is hindered by flatpak.

Early Knoppix live CDs have a special place in my heart

I’ve used silverblue on my gaming rig for over three years now. It has been a completely uneventful experience, so I really like it.

The only pain point I have is that compiling kernel modules is an utter disaster and it’s ridiculous that there is not a seamless mechanism for this yet. Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.

Was this written by AI?

Linux has dominated the router firmware market for a loooong time. Nearly all vendor firmware for consumer routers is Linux based.

Reminder to read the official git book. It’s free and it’s useful. My dudes, stop pretending to understand your tools and actually learn them.

This is amazing

Our current understanding having spoken to systemd developers is that we should be able to find a path that brings us much closer to upstream, if not entirely.

The only way the systemd developers will allow musl support upstream is if musl supports the glibc-isms that systemd uses.

They have been extremely clear that they will not carry patches for other libcs.