Guenther_Amanita 🍄

What “profile bio”? I’m doing biology all the time?

  • 0 Posts
  • 9 Comments
Joined 9 months ago
cake
Cake day: May 18th, 2024

help-circle

  • You did everything right. Boot into the image that works, and then apply rpm-ostree rollback. This reverses the broken image and the working one, so you’ll boot into this one the next time you boot up until you change something in the order, e.g. by updating.

    In the meantime, wait a day or so and then update again.

    On what channel are you on? bazzite:latest or bazzite:stable?



  • Here’s my perspective. I’m exactly that kind of guy you mean.

    As soon as someone mentions “immutable distro”, I get triggered and start shilling for Bazzite et al.

    Why you might ask? Because I like using it, and because the guys behind it are chill dudes with a great vision and a lot of know-how.

    I’m just a normal guy without IT skills. I can’t code myself, I can’t review someone’s else code, I can’t do anything.

    But I wish I could.

    The only thing I am able to is making it more well known.
    If someone asks “What distro do you recommend for gaming?”, I’ll say “Bazzite”.

    Someone else might say “Arch”, and another one “Tumbleweed”. Everyone likes their own thing, and everyone shills for something else :)

    I really wish your theory was real, then I could make some $$$, but everything here is FOSS. The devs are just as broke as I am…



  • Usually only as long as I play games. After that, I shut it off. Why?

    • I run Bazzite, which updates itself in the background, but needs a restart to complete
    • It boots in seconds, because modern hard drives are crazy fast
    • The standby-LED is annoying when I sleep

    My laptop is usually on for a week, but I restart it from time to time, for the same reasons, and because devices need some sleep too! 😴


    • You can still apply updates live, e.g. on Bazzite (Fedora Atomic) with the --apply-live tag (or however it’s spelled).
    • The root partition isn’t read only per se, but you have to change the upstream image itself instead of the one booted right now. You can use the uBlue-Builder for example to make your own custom Bazzite spin just for you if you want.
    • Both aren’t inherently secure or insecure. It’s harder to brick your system, yeah, for sure, but you can still fuck up some partitions or get malware. It’s just better because everything is transparently identifiable (ostree works like git), saved (fallback images), containerised and reproducible.
    • And you can still install system software, e.g. by layering it via rpm-ostree. Or use rootful containers in Distrobox and keep using apt or Pacman in there.

  • “Cloud native” means in this context, that the images are being built centrally by “the cloud” (in this case, it’s GitHub actions, but could be replaced by something else) and then the identical copies of the OS are distributed downstream.

    Contrary to traditional package manager based distros, this is more efficient and reliable.

    At least that’s the mission from what I know, but I also might be wrong. Then please correct me :)


  • Thanks for your experience report!

    Yeah man, Aurora (and uBlue in general) is fucking amazing. I’m using it on my laptop, and Bazzite on my gaming PC, which is pretty much almost the same tbh.

    Sometimes, people here on Lemmy might think I’m getting paid by someone to make advertisements for uBlue, but it’s literally the best distro I tried so far.

    It’s one of the few distros I would recommend for non-techy people, like my mum or friends.

    The only thing I dislike about Aurora in particular is the release schedule of KDE.

    Bluefin (Gnome) offers a gts variant, which offers older (and therefore more stable) packages, so you have half a year of extra testing.

    Sadly, KDE doesn’t allow that, so it’s more of a rolling release, like you said. Because of that, my experience with Aurora has been a bit worse than Bluefin, but still better than most other distros with KDE imo.

    EDIT: Dumbass me chose aurora:latest and not aurora:stable, no wonder I constantly got brand new packages. Ignore the last part.