poki

It's definitely a hidden gem. Enjoy!

ZSH through the excellent ZSH Quickstart Kit.

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.

Interesting!

So, I guess that at least one of the following 'transitions' is 'blameworthy':

• Silverblue -> uBlue Silverblue
• uBlue Silverblue -> Bluefin-DX
• Bluefin-DX -> secureblue

I guess I'll pass out on it for now. Thank you though!

Yeah I noticed that line as well. But, I'm a bit pessimistic that it will not be solved. Btw, what's the image you're on?

I’d like to know if it works for you now. I only ran the commands from the post and everything worked ootb

Aight. Let's give it a go:

Terminal interaction

Well..., for some reason it didn't work. FWIW, I'm on the bluefin-dx-main-userns-hardened image as provided by secureblue.

Thank you for the response!

Current mode: enforcing

This is pretty interesting. If I recall correctly, installing Nix onto Silverblue came with the caveat that SELinux' enforcing mode had to be turned off. But, your terminal output tells another story. I wonder what's up.

FWIW, I had lost interest in installing Nix on Fedora Silverblue for this very reason. However, I might have to revisit my stance on this. Once again, thank you (for reinvigorating my interest in Nix)!

Unfortunate. However, one bad move doesn't justify dismissing systemd altogether.

Do I wish for s6 and dinit to be competitive with systemd? Absolutely. Do I wish for systemd what PipeWire has been for PulseAudio? Yes, please. Do I wish that distros/DEs would be less reliant on systemd? Hell yeah! (Can I please have an rpm-based distro without systemd?)

But, unfortunately, at least for now, systemd is the most robust and (somehow) most polished init we got. And I'm actually grateful for that.

Until now I used distrobox but I always wondered which distro/ package manager to use. What’s your experience with it?

The answers found below this post resonate with my own experiences.

I do have a question: When you run the sestatus command in the terminal, what string/description is found corresponding to "Current mode"?

That makes a lot more sense. Thank you for clarifying!