It “shines”? It’s the same thing.

Neat

Distrobox is not a feature of immutable distros. It runs just fine on Debian. As does flatpak.

Read again. You completely misunderstood.

Yeah, this is the “fun” of bazite. If you want to do the things it does well (desktopy things) it works well. But then things that are trivial in other distros are a pain. And the “solution” is to actually run one of those other distros in a container. It’s ridiculous.

Bazite is for people who want a computer to be like an iPhone near as I can tell.

Flatpak is simply a sandboxed application, similar to a Docker container. Its better to have natively installed applications over sandboxed if you are seeking the highest level of performance.

This is bullshit. Containers run natively on your system just like “native” [sic] applications.

I wouldn’t use arch for anything.

But even without , the arch way isn’t insane either: when something kernel-related breaks, boot with a live system on USB and fix it.

That is not a replacement for “arrow-key down during boot to select an older kernel”.

I have a server with a RAID card and the kernel at some point introduced a bug with the driver that prevented that server from booting. So I select the older kernel at boot, get the system up and running, mark that kernel as the default until the bug is fixed.

It’s not crazy, it doesn’t take long, you just need to know how the system works.

I know how the system works very well thankyouverymuch. But that’s an insane option when having multiple older kernels is so easy to do and common.

That’s… Insanity. Keeping at least one old kernel is amazingly useful if you run into issues with an update.

Different distros vary a bit here, and it will differ if you’re on a system using efi.

Sometimes /boot isn’t mounted by default (it’s not needed unless you’re updating a kernel). You may be seeing a symlink or placeholder there.

If you’re using efi there will probably be /boot/EFI or something where your kernel is stored.