Btrfs snapshots + Snapper have been (somewhat) pioneered by openSUSE Tumbleweed. Yet, they see value in developing openSUSE Aeon (i.e. their attempt at an ‘immutable’ distro); otherwise they wouldn’t be putting resources into it.

Hence, Btrfs snapshots is (at best) only able to fulfil some aspects we’ve come to expect from ‘immutable’ distros. But there’s more to it than that.

One of the most simple (and, yet, perhaps most defining) feature that ‘immutable’ distros come with is atomic updates; i.e. updates either occur or not, there’s no in-between messed up state caused by energy outage or whatsoever.

There’s a lot more to it than that. To mention a few more:

• reproducibility
• declariative system management
• (some) prevention of cruft accumulation, bit rot and configuration drift
• better security related to read-only part of OS
• a lot less undefined/hidden/unknown state

Not all ‘immutable’ distros possess these qualities. Nor are they aspired by all of them. Hence, lumping them up together is actually a blatant oversight that’s been committed way too frequently.

Regardless, if you’re interested, consider trying out Fedora Atomic^[1], NixOS or openSUSE Aeon for yourself and see what it’s all about.

1. Either through Fedora’s own images or the ones provided by uBlue.

We’d rather like to see that anyways 😜.

Maybe I’m already running in XWayland somehow?

That’s definitely possible. Within Firefox, what does about:support reveal on this matter?

FWIW, I just noticed this thread

Unfortunately, I don’t own any device with Nvidia. Hence, I don’t think I’ll be able to help out. However, wayblue’s maintainers are pretty active. Therefore, consider opening an issue on its GitHub page and perhaps they’ll be able to help out.

I apologize for not being of much help here. Wish ya good luck, though!

Happy cake day btw!

Glad to be of help!

And thank you for reporting back!

Enjoy 😊!

It has been my pleasure!

It used to be called Sericea. However, the obscure names started to become very unwieldy. Therefore, they chose to preserve the naming for earlier established and recognized names (i.e. Silverblue and Kinoite) while Sericea became Sway Atomic instead.

It’s found here. It’s called sericea-nvidia. For this image, please refer to the installation guide found here if you’re interested.

Consider reporting back on how it goes 😉.

Ideally I would use an existing atomic distro with both Sway and Nvidia drivers

Consider taking a look at uBlue’s base image with Sway and built-in Nvidia drivers or wayblue’s image with Sway and built-in Nvidia drivers.

It’s a 12.5 inch device:

Star Labs’ StarLite

Linux support should be excellent.

Though, unfortunately, Star Labs’ reputation regarding communicating delivery times for their products leaves a lot to desire.

Still, it’s worth a look if you’re not particularly in a hurry.

Consider pulling those through https://www.virustotal.com/

Depends entirely on what they do on their device.

If it’s your average user, it should be sufficient for them to know that new software should exclusively be installed through the provided software manager.

Else, they should check if all their software needs are provided by Linux. And also think about which distro would be best for those specific needs. With Distrobox (and Nix) this isn’t as much as an issue as it used to be. But, there’s still software out there (like Davinci Resolve and Waydroid) that doesn’t like to play nice with all hardware and distro combinations.

Perhaps most importantly, ensure it’s a distro with sane defaults for a new user. This doesn’t necessarily mean that everyone should just use Linux Mint. However, it’s better if the chosen distro makes sense for the user.

It has been my pleasure!

and joined their discord in preparation.

That will definitely help out a lot. Well thought!

Welcome on board 😉.

I’m not the one you asked your question, but I think I understood what they meant.

First of all, technically MicroOS is the non-desktop version of openSUSE’s take on an atomic/immutable distro. The desktop variants are referred to as Aeon (for GNOME) and Kalpa (for KDE).

Secondly, while Aeon/Kalpa definitely is to openSUSE what Silverblue/Kinoite is to Fedora, there’s a clear difference in vision and maturity.

Vision

Fedora Atomic is a very ambitious project; everything points toward it being Fedora’s take on NixOS. But, unlike NixOS, it couldn’t start from scratch nor did they intend to. Instead, it’s the process of evolving their existing products into something special. As such, it has been over two years since Fedora has even explicitly stated that they intend for Fedora Atomic to become the default eventually (without saying anything about sunsetting the old). While, AFAIK, openSUSE has yet to make similar statements regarding Aeon/Kalpa.

Maturity

Everything points towards Fedora Atomic being more mature than openSUSE MicroOS; work on the project has started earlier, Fedora Atomic is almost done with their transition (from image-based) to OCI while I don’t recall openSUSE mention anything regarding their transition (from ‘snapshots’) to image-based since they mentioned it briefly last year. Furthermore, Bazzite (based on Fedora Atomic) has become the face of Gaming Linux while openSUSE’ MicroOS fails to deliver on anything but Aeon. Which, to be fair, is absolutely fine. But not everyone is fan of GNOME.

So, use Tumbleweed if:

• You prefer the traditional model
• You like YaST
• You like the rolling release model and not being tied to GNOME

Use Aeon if:

• You like GNOME and an atomic distro on a rolling release distro
• You prefer the opinionated, hands off, little to no customization path that openSUSE has currently chosen for its Aeon
• You like a containerized future

Use Fedora Atomic if:

• You want an atomic distro, but don’t like any of the decisions made for Aeon; i.e.
  • prefer to use KDE, Budgie or Sway (or any other desktop environment through uBlue)
  • aren’t that big of a fan of container workloads
  • prefer having the choice of installing native packages
• Prefer atomic on top of a point release distro

Finally, regarding containers specifically; let’s say you want to install package X.

• On Tumbleweed, you just do sudo zypper install X and you’re done with it.
• On Aeon, if it’s available as a Flatpak, you do flatpak install X. If there’s no Flatpak of it, you install it within a container that you access through Distrobox. Within the container, use the package manager corresponding to the container. Technically, while inside the container, the environment is very similar to Tumbleweed. So, say you got a Tumbleweed container, then you can continue using sudo zypper install X.
• On Fedora Atomic, you can layer onto the system through rpm-ostree install X; this is very close to how installing packages work on Tumbleweed. And, you can continue using both Flatpak and Distrobox; like how it’s done on Aeon. Note that Tumbleweed also allows access to Flatpak and Distrobox. So, Aeon is most restricted as it can’t install packages onto the base system. Btw, Fedora Atomic accomplishes this through layers that can also be peeled off later on (through uninstalling for example). With this, the base system actually isn’t affected, but the end user doesn’t notice it.

First of all, if you’ll be using Bazzite, then become familiar with its documentation. Other sources may not necessarily translate that well to Bazzite due to Fedora, Atomic, OCI and SELinux (to name a few). Though, some other sources may benefit you as long as it doesn’t contradict with Bazzite’s own documentation.

so, what are your tips and tricks for a new linux user?

Bazzite is on Fedora Atomic’s model, hence you should become familiar with the built-in rollback mechanism. Furthermore, it’s possible to keep deployments around. Therefore, if anything, consider utilizing this on your first deployment; just in case.

Pinning said deployment is possible with the sudo ostree admin pin <insert number> command after installation. The number can be deduced through the rpm-ostree status command. The first deployment’s corresponding number is 0 and for each deployment found below you just have to increase the number by one to find its corresponding number. So, the 4th deployment corresponds to the number 3. Btw, you can pin multiple deployments. So there’s no opportunity cost involved. Finally, you can unpin a deployment with -u. So sudo ostree admin pin -u <insert number>

as a final question, what got you into using linux over windows or mac?

I was never a mac user in the first place. As for Windows, a hardware failure was causing more issue on it than on Linux. So that was the direct cause. But the reason I got interested into Linux initially and what has kept my interest are privacy and freedom respectively.

Solutions found on either of these wikis may work perfectly fine on other distros, but it’s not a guarantee. ‘Seasoned’ users should be able to distinguish this.