Hello! I’m thinking about switching from my beloved fedora to a rolling release distro, because it really intrigues me, but I’m a bit scared of Arch, it’s still too soon for me to go down this rabbit hole XD
what do you think about debian testing? It’s not a “true” rolling release as long as I understand, but it “practically” behaves like one, correct? On the system informations I still see Debian 12, what will happen when Debian 13 stable will be released?

sorry if these are silly questions and thanks to all in advance!

  • @oranki
    1•1 year ago

    Devuan is more stable

    So Devuan has even older versions of packages than Debian? Stability in the distro context means that features, APIs, UIs don’t change. Please don’t mix software bugs with stability.

    It may be I’ve entirely misunderstood how systemd works, but I think your description of it is off by a mile too.

    but a different init starts a new process ID for each separate program

    Of course there are PIDs with systemd too! First of all, systemd itself has a PID (1).

    For systemd, which runs system wide to handle everything, if one program locks, systemd has to make adjusts for the whole system to fix the problem.

    This is just wrong… Sure, if the service in question is dependent on a lot of other services, or vice versa. If your programs tend to lock, that’s the application’s fault and should be handled at the application level.

    I found Artix to run smoother or lighter than Arch.

    This is most definetly a difference in what else is running on the system. Systemd doesn’t really use that much resources. Unless you are measuring RAM usage in the megabytes. Which is of course valid on constrained systems, but on a regular desktop one browser tab will need orders of magnitude more resources than any init system.

    I want Firefox running an isolated process from the one that Plasama desktop is running

    This just shows you have absolutely no clue on Linux processes, I really really doubt anyone is running Firefox under systemd. And neither have you.

    There are valid reasons for choosing a different init system, but you have not provided a single one that is really true. It seems like you are only repeating things heard from some one else.

    The difference is systemd is one thing to handle everything

    This is true, but it refers to systemd handling a lot more than process management. Systemd has the problem that nowadays it does log management, memory management, login management, user management etc. This goes against the UNIX philosophy of one tool for one job, and THAT is why people frown on systemd.