UnfortunateShort

Compared to Arch(-based): Accesing the latest packages. It’s not impossible, especially if you go for Debian testing repos, but it’s definitely extra work.

Compared to special-purpose distros (i.e. gaming, portable, high security/privacy, pen-testing): Whatever their special purpose is will usually be harder to achieve.

Compared to huge corpo distros (SUSE/Fedora and derivatives): Ease of more intricate setups and maybe some security testing.

Compared to Ubuntu: Paying a corporation to not withhold security patches from you.

Ingl, this sounds like exactly the thing I want. Immutability aside, this is how I use EndeavourOS right now, but more sophisticated.

I’m sold on it.

Ingl, the amount of dislikes made me grunt a little

In short: No. It’s getting better, but Flatpak is by no means secure. Think of it as a Windows .exe or .msi with some (not that hardened) rights management.

In addition, Flatpaks afe often community made and not even “signed” (which is not really a thing in Flatpak to begin with (yet) ((afaik))).

Something really secure would be a container, something really, really secure would be a VM, something really, really, really secure would be a separate machine. Flatpak is less secure than the least secure thing in this enumeration.

Well, I did preconfigure Endeavour a bit, but still, it runs just fine :D Being on KDE is a huge help, Windows users feel pretty much right at home.

Have you considered using pipx + poetry?

I threw my brother and my dad into EndeavourOS and Garuda respectively. So far, they are swimming. My brother even does almost all his gaming on Linux.

(Well OK, apart from my dad generally yelling at everything tech. I guess that’s where I got it from.)

I think you’re forgetting where Linux was the most successful by far: Servers and Android. Server guys do what they want, if you tell them they can only use software you allow them to, they will laugh at you and buy their data center elsewhere. Android has had locked bootloaders forever (I actually think even my very first phone had one).

So maybe development would have been harder? I mean, we don’t have looked bootloaders on desktop even today, not really locked at least, so it’s hard to tell. Linux’s main audience would not have cared I think.

It’s 2000 series, so they are supported by the new OSS driver, no?

I don’t really get the argument of Microsoft being cemented. I mean, firstly they are pretty much everywhere, so I can’t see how it’s getting worse. Secondly, the German state partly uses Linux, even outside of servers, which is already more than I expected. You can’t expect a state to “just switch” to anything. We are talking hundreds of thousands of users and computers here…

Isn’t there also some EU cloud thing going on?

Their new, open driver only supports 2000+ series, so I guess that also applies here.

This is more likely someone fucking up and not having a second pair of eyes look at the presumed problem than anything else.

It depends on the brand I guess. Some Canon Pixma did immediately worked with my distro, like literally zero setup required. However, it refuses duplexing. It just won’t do it. Not driverless and not with gutenprint, although it lists the specific model, not when setting it as the default, not when setting it per job.

Yet it works on Android no problem.

If I had to do encrypted btrfs RAID from scratch, I would probably:

1. Set up LUKS on both discs
2. Unlock both
3. Create a btrfs partition on one mapper
4. Add the other with btfs device add /path/to/mapper /path/to/btrfs/part
5. Balance with btrfs balance start -mconvert=raid1 -dconvert=raid1 /path/to/btrfs/part
6. Add LUKS’ to crypttab, btrfs partition to fstab and rebuild/configure bootloader as necessary

In that scenario, you would probably want to use a keyfile to unlock the other disc without rentering some password.

Now, that’s from the top of my head and seems kinda stupidly complicated to me. iirc btrfs has a stable feature to convert ext4 to btrfs. It shouldn’t matter whatever happens outside, so you could take your chances and just try that on your ext volume

(Edit: But to be absolutely clear: I would perform a backup first :D)

I think there are good kinds of fragmentation (choice and/or competition) and many bad kinds/causes of fragmentation (clinging to abandonware, reinventing the wheel, rejecting reasonable changes, “rewrite it in X-lang”, demanding complete control, style/design choices that don’t actually matter…)

That I can understand, however I want to piont out that this is an Nvidia problem entirely. Wayland works perfectly fine under 2/3 hardware vendors.

Luckily, they finally open-sourced their shit so going forward, this will probably change. But chances are only from the 2000 series on, so it might take an upgrade for many folks…

All I know is that there are VNC and RDP solutions for Plasma and VNC solutions for Wayland in general.

You can autostart anything on any distro by putting the command in a startup script.

I love how people are complaining about Wayland not being ready or being unstable (whatever that even means, because it’s a protocol), while it’s the default on both GNOME and Plasma now, which combined probably run on more than 50% of Linux desktops these days.

And not only that, but Cinnamon, Xfce and others want to follow, so very clearly people who know a fair bit about desktops seem to disagree with Wayland being “not ready”.

It does not and whatever distro you choose, it will not.

And yet I never do and it hardly ever does. And if it does, it’s more often than not application specific and fixed by loading a snapshot and updating again after a week or so, which is next to 0 effort.