Kwozyman

Haha, had no idea, I don’t watch the stock market

Unfortunately a lot of people do. So many people care they made him the richest person in the world. I always hated obscenely rich people, but there’s something special with Musk, he manages to add insult to injury.

A high level explanation

Be that as it may, it’s still an incredibly short sighted decision to use a centralized service that is under 3rd party control for real security sensitive applications.

They don’t care at all. What they do care is sowing polarization and distrust between western citizens. Russia benefits most when we (the West) are divided on various social issues, which leads to distrust of authorities, election of extremists in office and eventually weak and corrupt states and governments that are easily controlled or countered by Russia.

It’s people who know they will be irrelevant because they spent decades producing shit software

So the Linux kernel is shit software now? Just because it’s not written in the newest programming language? Kind of a hot take.

This article reads like a press release from SUSE.

Russia Today comes to mind

Sure, but for Russia it’s the actual doctrine: https://en.wikipedia.org/wiki/Russian_military_deception

you’re a rock star

I don’t know if this works in docker (usually there is 1:1 equivalency between the two), but with podman you can do something like:

podman stop --filter name=foo

man podman-stop tells us:

   --filter, -f=filter
       Filter what containers are going to be stopped.  Multiple filters can be given with multiple uses of the --filter flag.  Filters with the same  key  work
       inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.

If you do a rollback, I assume your data remains? I assume you might need to reinstall apps which were not in the original? Or does it keep apps, data and settings across a restore?

In CoreOS (Silverblue), /etc, /var and /home (which is in fact a symlink towards /var/home) are regular writable partitions, so your data, configs and personal files are not touched by the upgrade/rollback procedure.

All the packages (and their dependencies) you’ve installed extra are also upgraded/rolledback when you do a system upgrade.

The immutable part (again, only speaking about Silverblue, I don’t know about others) refers to the inability to make changes online (i.e. without rebooting), but you can eventually change whatever file you want. The way it works is you would make your changes in a copy of the current filesystem and at boot simply mount and use the copy. If something goes wrong, you just mount the original at next boot and you have rolled back.

You make a lot of good points, but I have to disagree on the “don’t let the user see or touch anything”. That’s very much not the way immutable distros behave (and I speak mostly about Fedora Silverblue here, I don’t have experience with other immutable systems): you can touch and change anything and often times you have mechanisms put in place by the distro developers to do exactly that. It’s just that the way you make changes is very different from classical distros, that’s all, but you can definitely customize and change whatever you want. I feel the comparison between immutable distros and Apple is really far off: Apple actively prevents users from making changes, while immutable Linux is the opposite – while there may be some technical limitations, the devs try to empower the user as much as possible.

Maybe I don’t understand the question, but what prevents you from adapting your Ansible playbooks to Fedora Silverblue? I assume for Debian at some point you have a “install packages” section which you should rewrite to use rpm-ostree or flatpak instead of apt-get; your dotfiles section should remain the same etc etc.

In the FTPD logs, do you see the initrd file being pulled? Could it be a mismatch between the kernel and initrd you’re serving?

Well, I don’t know how fair they play now, but for sure that wasn’t always the case.