Yeah the docs are a bit misleading but they are mostly for complete linux newbies. Its basically saying that to scare away any newbies from relying on ntfs because ntfs on linux has quite a few issues (in general, not exclusive to Bazzite) and might break unexpectedly since it is reverse-engineered so it is not perfect.

Bazzite does support NTFS. I use Bazzite on one of my devices with ntfs partitions and I haven’t had any problems so far. Unless you mean installing Bazzite on the ntfs partition which yeah I guess it doesn’t but Im not sure if any other disro has support for it.

But fair enough, immutable distros have a read-only system so making certain changes might be difficult and the usual commands might not apply. They are not impossible though, just require different commands since you have to layer those changes on top of the system. I have been able to make pretty much any changes to my Bazzite system that I would do on an ordinary distro.

Bazzite also has a really nice community that will help you with any issues and you can also ask for help in Fedora Silverblue/Kionite communities since Bazzite is just an image of Fedora (Kionite).

Bazzite does support ntfs. I have ntfs partitions on my system and they work perfectly fine in Bazzite.

Woah that MR actually got merged damn. Couldn’t believe it when I saw this, I thought the title was a clickbait or something until I checked and it was for real.

Yeah the whole situation really sucks. Im a big fan of both marcan and linux so its just sad how it all ended. But Im hopeful the R4L project will be successful despite these setbacks. Some of the first rust drivers are really close to landing and I think once that happens, the dust will mostly settle as hopefully most of the things around rust would have been figured out by then. Even this situation led to some improvements like the R4L policy (and also brought the issue to greater public scrutiny). Though the drama probably won’t end there, especially if rust starts making in to the core kernel (thus start being required for building the kernel). That is probably going to be the final obstacle; if rust makes it to the core kernel code, I think the R4L project will have succeeded.

tl;dr Run sudo apt install --install-recommends linux-generic-hwe-24.04 in the terminal to get the latest kernel version available (v6.11.x)

Linux Mint uses whatever kernel the latest Ubuntu LTS (24.04) is using which happens to be v6.8.x. Ubuntu LTS and thus Linux Mint will by default remain on this kernel version for two years after its release i.e. until the release of the next major version of Ubuntu LTS. This is for stability (hence the LTS moniker - Long Term Stable). You do get security updates and fixes in point releases of the kernel.

So yes kernel versions are tied to your Linux Mint version. But Ubuntu also offers newer kernel versions, however those will be less stable so are not recommended unless you have some hardware that doesn’t work with your current kernel version. Just run sudo apt install --install-recommends linux-generic-hwe-24.04 in the terminal which will install v6.11.x. This will also install newer versions of drivers (mesa) and other related stuff. Note that this kernel version is not fixed, you will get updated to a newer major kernel version every 6 months.

*And if you have an Nvidia GPU, you would also want to install the Nvidia driver for the newer kernel. I think Mint provides an app for that (drivers or something).

I wonder when Ubuntu will make the shift. They are the only ones left on AppArmor at this point (tbf they have been maintaining it alone anyways).

really nice video, covers the whole spectrum of things

You are just being silly, there is no way its going to “seriously damage the entire Linux project”. There is nothing too technical about the whole R4L drama (esp. the recent one), its mostly political opposition to Rust from some C folks. We have seen this before in Linux (Wayland/X11, systemd/sysv, etc.).

its flatpak run org.mozilla.firefox