Thank you for providing that video!

I hadn’t seen it before, and I can definitely understand why its content is disturbing.

Granted, as I’m unable to understand the context beyond what AP themselves have provided, I’ll (for the sake of the argument) accept this as Palestinians celebrating an attack on the US.

Then, my initial intention was to dissect the argument and explain why I can’t agree with your extrapolation^[1]. However, to my surprise, your extrapolation might not be as far-fetched as I initially thought 😅. But, this ultimately depends on what you mean precisely. So, please allow me to ask further clarifications:

• With “Israel would simply not exist on the map today.”, what do you mean exactly? Like, what would come in its place? What would become of the Israeli people?
• With “And the Palestinians would be openly celebrating over the dead bodies of Israeli people.”, do you mean something similar like we see on the footage? Or something more grandiose? (And perhaps more sinister?)

they’ve been apparently working on its replacement for quite some time, so the “news” of its retirement actually comes because of the discovery of its replacement and the chatter around it.

Are you referring to the combination of Agama, Ansible and Cockpit?

Thanks for posting.

It has been my pleasure!

I was worried that it might have been forgotten about

The XZ utils supply chain attack has actually made the community more wary of blobs. Some projects were even prompted to come clean on this matter.

Fedora has also recently made a push towards reproducible builds. In the lwn.net article that discussed that push, one of Fedora’s spokespeople explicitly said that it would help combat supply chain attacks.

So, all in all, I can confidently say that it did leave a mark on the Linux landscape. Hopefully, this specific attack vector will not be as viable in the foreseeable future.

But if Palestine had the kind of military backing Israel does, Israel would simply not exist on the map today. And the Palestinians would be openly celebrating over the dead bodies of Israeli people.

What is this based on? Like, could you (by any means) back up this claim?

Please correct me if I’m wrong, but my understanding is that we didn’t get any alternative in return. Right?

The following has been prepared with help from an LLM. The content is basically mine; it only helped me with wording/phrasing etc. Sometimes, my RSI-like pains come up and I can’t be bothered to do otherwise. Thank you for your understanding:

I saw wireguard tools, isn’t that a kernel module?

The WireGuard implementation has two parts - the kernel module (built into the Linux kernel) and the userspace tools package. This sysext only provides the userspace tools (wg and wg-quick commands), not the kernel module itself.

Although this looks interesting, I have trouble understanding the pro’s and cons vs something like flatpak or containers.

Sysexts fill a critical gap in the Fedora Atomic ecosystem that neither Flatpak nor containers adequately address.

While traditional distros let you install packages natively, Fedora Atomic’s direct alternative to this (i.e. layering) comes with significant drawbacks - updates take longer, require reboots that disrupt workflow, and can sometimes block future updates entirely. This has been a persistent pain point for users.

Flatpaks technically support CLI tools but rarely package them, and containers are impractical for things like shells (imagine running fish or zsh in a container to use on your host). Similarly, applications like Steam or certain browsers sometimes need deeper system integration than Flatpak provides - which is why projects like Bazzite and SecureBlue install them (read: Steam and Chromium-derivative respectively) natively.

The CLI situation has been particularly frustrating, even for Universal Blue, which has driven much of Fedora Atomic’s ever-growing adoption. Their exploration of various solutions (eventually landing on Homebrew) demonstrates how challenging this problem has been.

Sysexts offer an elegant alternative - they provide system-wide integration without breaking immutability or requiring reboots. You intuitively know when to use a sysext versus Flatpak or containers - they’re not competing but complementing each other.

They aren’t a silver bullet (we’ll still need layering for kernel modules, etc.), but for many tools, sysexts provide the solution the immutable OS ecosystem has been waiting for.