toolbox is preinstalled on fedora silverblue/kinoite whereas distrobox isn’t. What’s the advantage of one vs the other? Why is toolbox preinstalled and not distrobox?

edit: thank you guys! I guess for me this means that I’ll use distrobox because it’s much more mature or documentation is a little bit better and I do not need (or have) fedora’s support

  • alt
    111·
    1 year ago

    Not OP. But for me, atomic updates, reproducibility, (to some degree) declarative system configuration, increased security, built-in rollback functionality and their consequences; rock solid system even with relatively up to date packages, possibility to enable automatic updates in background without fearing breakage, (quasi) factory reset feature, setting up a new system in just a fraction of the time required otherwise are the primary reasons why I absolutely adore atomic[1] distros.

    1. I prefer referring to the so-called ‘immutable’ distros as atomic distros instead. It’s more descriptive, because the distros aren’t actually ‘immutable’ but instead they’re atomic.
    • TheCaconym [any]@hexbear.netEnglish
      22·
      1 year ago

      I disagree with most of the benefits you list (chief among them “increased security”) - not to mention half of them are already supported by traditional package managers - but I was genuinely curious so thanks for the rationale.

      • gnumdk
        6·
        1 year ago

        Ubuntu, then Debian on my University computers, broken every weeks with dpkg killed while updating (students don’t care properly shutting down computers).

        Since we migrated to Silverblue, it just works. We can downgrade the system at any point in time, even previous release. Apps can be individually downgraded, locked at any point in history. Totally not doable with a traditional package manager.

      • alt
        4·
        1 year ago

        I disagree with most of the benefits you list

        I’m curious to hear your objections.

        chief among them “increased security”

        Do you deny that specific protection to some attacks is provided through the chosen model of ‘immutability’ on at least one of the atomic distros?

        not to mention half of them are already supported by traditional package managers

        Hmm…,:

        • atomicity; nope
        • reproducibility =/= reproducible builds for some packages (if that’s what you meant)
        • declarative system configuration; ansible (and any other solution that I’ve witnessed being mentioned in such discussions) succeed (at best) at convergent system management, while e.g. NixOS does congruent system management by default. Consider taking a look at this page if you’re interested in what these are and how they’re different. (Spoiler alert) congruent is better and therefore more desirable.
        • increased security; security is not limited to chosen model for ‘immutability’ if at all; as Qubes OS (read: most secure and private desktop OS) doesn’t rely on it for its security. So I can understand where you’re coming from, but I have yet to see any non-security focused distro that provides the elevated protection against particular attacks that some atomic distros offer by default.
        • built-in rollback functionality; sure, this is not exclusive to atomic distros. Perhaps I should have done a better job at making clear that it isn’t a feature provided necessarily by atomicity. But, the fact that I listed it at the very end, alludes that it isn’t as exclusive and consequential as atomicity is. At this point, however, it has become almost synonymous with atomic distros, while the same can’t be said about traditional distros.
        • regarding the consequences; I’m unaware of any distro that does those out of the box (barring Pop!_OS with their factory reset). Though, I’d love to be educated on this.

        I was genuinely curious so thanks for the rationale.

        It has been my pleasure ☺️! I’m also genuinely curious to read your reply to this comment😉.

        • TheCaconym [any]@hexbear.netEnglish
          21·
          1 year ago

          I really wanted to avoid a debate (doubly so in a thread where some dude just wanted some help), which is why I’m trying not to engage the various answers I got; though just one thing since I apparently can’t help myself: Qubes, which you cite, is indeed an example of such improved security done correctly, through an hypervisor and a solid implementation; not cgroups, some duct-tape and the same kernel, and thinking your security has improved. Thanks again, at any rate.

          • alt
            4·
            1 year ago

            Understandable! Please consider coming back to this at some point (also possible in private) as I’m genuinely curious to hear from you.

          • kanzalibrary
            1·
            1 year ago

            There are may layers of security that every companies have different approach based by their users / their target customers.

      • IverCoder@lemm.eeEnglish
        2·
        1 year ago

        All of the points of the previous comment are actually valid. Plus, immutable distros are much safer and easier to tinker with than traditional mutable distros. For example, an extremely specialized Arch setup would be much more stable and easier to jumpstart if it was a personalized Universal Blue image, even all your Flatpaks can be declared and installed at setup.