So I took the plunge and installed Fedora Silverblue because of all that immutable buzz. And it’s the most frustrating change I have made in almost 20 years of my distrohopping.

After installing Silverblue I configured it as usual. I installed necessary flatpaks, played with toolbox and distrobox, installed codecs, configured my bluetooth keyboard and other stuff in /etc and /var. Applied some useful tweaks I found on the web and… well… everything works. Nothing to do anymore. No issues. Nothing breaks, no dependency hell, everything runs smooth. I have nothing to tweak, tinker or configure anymore. So frustrating.

Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking. Booooring.

I don’t have to distrohop anymore. If I want other distros I can just install them in distrobox. Other versions of apps? Something from AUR perhaps…? No problem. What’s the point of distrohopping now? Other DEs? I just rebase my system to other images with almost any DE or WM I want without losing data or messing everything up (damn you, UBlue!).

I don’t even have to reinstall the damn thing cause every time I update the system or rebase it to another image it’s like reinstalling it.

Silverblue killed distrohopping for me. Really frustrating.

  • Ricky Rigatoni
    link
    fedilink
    165 days ago

    Congratulations. You have completed Linux. Please prepare a usb installer for Haiku to move on to the next step of your jouney.

  • @kronarbob
    link
    316 days ago

    What an horror ! What are you gonna do ? Use your working system ? That’s sad…

  • Lung
    link
    517 days ago

    I’m honestly so trolled, I hate change & hate the idea that something might be better than my existing Arch install. I hate that security, reliability, and flexibility are improved. I cope by reminding myself that I’m very low on disk space right now, for the needed extra partitions

    • @barsquid
      link
      87 days ago

      If you have a spare homelab machine Fedora does an immutable build called IoT (they branded it wrong it’s just a barebones install appropriate for servers also).

  • @[email protected]
    link
    fedilink
    85 days ago

    After beginning to wrap my head around atomic immutable OSes, I can’t believe they’re not the standard for most servers. i can’t believe Debian doesn’t have an official atomic and immutable version yet, seems exactly like the kind of stability they aim for

  • @[email protected]
    link
    fedilink
    English
    257 days ago

    I’m a bit behind on these immutable distros and have a small question. People keep saying you can just switch to another image if you want to switch desktop environments. But how does this solve the problem of the config files of the various DEs (GTK rc files or other theme stuff) messing with each other in the home directory? Because this was always a pain in the ass in normal distros

    • @Pfifel
      link
      187 days ago

      Switching DEs is not recommended by devs so I assume the configs are still conflicting. Home dir doesn’t get affected by an image rebase most likely.

      • @hessnake
        link
        77 days ago

        I’ve switched between Plasma, Cosmic, Sway, and Hyprland without any conflicts. For the Plasma 5->6 transition it did change my config in a way that broke Plasma 5 when I rolled back, so problems are possible.

        Basically your mileage may vary.

    • @[email protected]
      link
      fedilink
      117 days ago

      But how does this solve the problem of the config files of the various DEs (GTK rc files or other theme stuff) messing with each other in the home directory?

      It does not. Your dotfiles will be a bit wrecked when you rebase. See: https://universal-blue.discourse.group/t/why-is-rebasing-between-desktop-environments-bad/690/4 It’ll also cause random issues like: https://discussion.fedoraproject.org/t/flatpak-apps-crashing-after-rebasing-from-silverblue-to-kinoite/83623/2

      It’s mostly plasma fighting gnome, though. I haven’t seen any conflicts with say, sway.

    • @[email protected]
      link
      fedilink
      25 days ago

      yeah, home directory is mutable, but you can simply create another user, the /etc is also mutable(the system do a diff of it every update) but you can see every file that changed there(compared with the remote image) using ostree, or create another deploy where you discart your /etc, so, if you discart your /etc, and create another user, you have fresh install, without needing to reinstall using a pendrive etc

    • @barsquid
      link
      77 days ago

      Your files are a mutable part, they stick around for rebase and rollback. (I believe /etc also.) If it’s only files in a home directory you could try a different DE by making a new user. But yeah I don’t think it has a built-in solution for something like that.

    • @iopq
      link
      26 days ago

      I guess you just have to use home manager on NixOS

  • @warmaster
    link
    English
    116 days ago

    You need to install a rootkit ASAP.

  • @[email protected]
    link
    fedilink
    English
    157 days ago

    I really love Fedora Kinoite. Like you said, everything just works. It’s fantastically boring

  • @[email protected]
    link
    fedilink
    116 days ago

    Two days ago my Mint system got borked by a kernel update. I booted from the grub menu with the prior kernel, and rolled back with Timeshift. Pretty painless. You don’t need Atomic/immutable distros for that sort of reliability.

    I’m playing with kinoite in a VM, though.

    • @[email protected]
      cake
      link
      fedilink
      36 days ago

      Depends what you break. Sure kernels are easy to fix like you mention, but what if you bork your display manager?

      • @[email protected]
        link
        fedilink
        55 days ago

        Can’t you run timeshift from a live usb? Never tried, but i believe its possible. Obviously more time consuming and bothersome, but possible.

        • @[email protected]
          cake
          link
          fedilink
          15 days ago

          I actually don’t know whether timeshift can just run easily from a live USB, but I don’t see why not.

          But of course that also requires you to have installed and set up timeshift before (which is obviously a good idea)

          It’s quite a different deal when the whole operating system it built around a timeshift-like concept.

  • @[email protected]
    link
    fedilink
    English
    16
    edit-2
    7 days ago

    Love the irony, but this is painting a little too good a picture

    Every update is just… meh. Smooth, new, fresh system not affected by my stupid tweaking and breaking

    Most times yes, but major updates usually cause some trouble, like from 39 to 40, you couldn’t do it without uninstalling the codecs for Firefox. Firefox that is installed by default as an RPM, because the Flatpak Firefox doesn’t yet have 100% compatibility with all the features that work with the RPM, so as a user you’re pretty much led to get yourself stuck in this hole, not too difficult to fix in the end, but still a pain to find out and fix.

    Everything else is 100% true! And I think it will be always hard to beat as an implementation of immutability (second place only to NixOS imo), A/B partitioning doesn’t hold a candle to OSTree

    • @[email protected]
      link
      fedilink
      15 days ago

      you couldn’t do it without uninstalling the codecs for Firefox

      what happened is rpm-fusion was lagging behind the official fedora repos, so, you could have just waited, or enabled the automatic update and forget about it

      • @[email protected]
        link
        fedilink
        English
        15 days ago

        Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have “fixed” the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can’t accept the PR

        • @[email protected]
          link
          fedilink
          25 days ago

          oh, i never had that issue, only the rpm-fusion lag, never thought that the codecs needed a different approach

    • @laughterlaughter
      link
      26 days ago

      What does rebasing mean in this context? I try to google it, but all I get is git rebase.

      Any articles about it that are worth reading? Or if you can explain, that would be neat. Thanks!

      • @olafurp
        link
        56 days ago

        It’s a command provided by the OS to distrotop between ublue distros. You can basically hop between silverblue, Kionite and Bazzite with a single command.

          • @[email protected]
            link
            fedilink
            45 days ago

            ostree based distros*, the default fedora don’t use ostree so you can’t rebase, bazzite is not fedora but they also use ostree, so you rebase there

            • @laughterlaughter
              link
              2
              edit-2
              4 days ago

              I have so much to learn. Last time I was tracking distros and having fun with distro hopping was with Slackware 7, I think.

              What is ostree? What is bazzite? Time to google stuff.

      • @[email protected]
        link
        fedilink
        36 days ago

        Its the same :D

        Rebasing refers to an OSTree remote which is like a git repo, but with binaries and producing bootable systems. There are some differences there.

        The idea is: there is a remote that has the exact wanted configuration, your system mirrors it. All the package manager does is similar to git pull.

        If you rebase, you switch the upstream remote, and your system gets the diffs, downloads them.

        The cool thing is, that these updates are atomic, so you stay on the current system and the rebased one is only set as the system you boot in after a reboot. You can still sudo ostree admin pin 0 before rebasing, and your current system will be saved forever to switch back to.

        Note that /etc is writable so you might still accumulate duplicate or redundant configs.

        gitlab.com/fedora/ostree/sig/-/issues