329
Bazzite sees a massive jolt in installs in late June and early July, catapulting it to over 86k active devices. It has doubled the number of active devices since November. (lemmy.ml)
submitted 3 months ago by to c/linux@lemmy.ml
81 comments fedilink hide all child comments
 

Upstream images vs bazzite: https://github.com/ublue-os/countme/blob/main/growth_upstream_with_bazzite.svg

My prediction: bazzite may have more installs than Fedora KDE by the end of the year.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 months ago (6 children)

I reckon this must be true. However I do not see this as a reason for wide adoption of immutable systems. I guess that is a fairly valid use case.

I'd like to understand why some users are enthusiastic about bazzite. As of now I understood two of the reasons:

  • updates work and do not break the system
  • it is a bit more secure

However I do not understand why these two things make their users so enthusiastic. It's two things you rarely worry about when using a computer. They are indeed important, but in my opinion not much of a problem in modern distributions.

In the other hand you have to install everything through flatpak, which is something which would really get to my nerves.

I understand there are some good advantages, I just fail to understand which ones those are.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S] 5 points 3 months ago* (last edited 3 months ago) (6 children)

    It requires literally zero work from me to maintain, that's why I'm enthusiastic and want the project to do well. Saying mutable Linux is zero work is dead wrong. And if you do put work into your system, it actually sticks and doesn't decide to explode one day over it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 3 months ago (5 children)

    Most of the work in my system is installing software and changing configurations of said software. The rest is using the software. What is the difference in the amount of work here? I guess on an immutable system you will also be installing software and modifying configuration files.

    In my system something can malfunction to which I have to change some system configurations: for example past week I had to change some systemd-resolved configuration because on a specific interface it was using some random DNS I didn't want it to use. I assume this work will also have to be done on an immutable system.

    What is the work which you have to do on a normal distribution and not on an immutable system?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 4 points 3 months ago* (4 children)

    How long have you been using Linux? I've been using it since around 2004. About every 2 years a major upgrade would make my computer kill itself and I'd have to manually repair it over the course of a weekend. I do security software work and often to make that suite of software (some of it not niche like vpn apps) function you must alter some system files. Layering these apps over the system solves the problem.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 months ago (3 children)

    I've been using Linux as my main OS for about 15 years. I had my system break down in other occasions in the same way you describe. It is a nuisance, but luckily it never was a major problem. I believe once I had to reinstall the system, I was very happy to have a separate home partition.

    I'm not sure what you mean by layering apps over the system, that could be interesting. Especially because I imagine something like a VPN needs root access. Is it possible to install a binary as a service with root access if that is not available in the repositories? I do for example have to use a quite obscure VPN protocol.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] [S] 3 points 3 months ago* (2 children)

    Yeah. You can layer it like a git repo fork layers it's changes. If something breaks you can just clear that forked branch and redo it. Takes like 2 minutes to fix.

    So yeah you can alter system files in a very safe way and can easily revert changes if you don't like the result. rpm-ostree reset is the command that clears all changes and resets to master. I'd recommend looking at the rpm-ostree docs for a full explanation of functionality

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • load more comments (-1 replies)