• beleza pura@lemmy.eco.br
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    19 days ago

    people laughed at me for choosing debian. they asked why i chose to have ancient runes running in my computer

    who’s laughing now?

    • PushButton@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      18 days ago

      We are still laughing, no worries.

      p.s. Debian is great, I am just a “kind of new” void converted.

      • beleza pura@lemmy.eco.br
        link
        fedilink
        arrow-up
        1
        ·
        18 days ago

        went looking for it. “stable rolling release” sounds really interesting, but i’m scared of installing it and being mistaken for a systemd hater

        • PushButton@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          18 days ago

          Yeah, systemd hater or not, runit is quite fabulous Imo.

          Some software with a hard requirement on systemd will not work, of course. I believe it is possible to run void using systemd, I’ve never tried though.

          I really like runit, but once it’s configured, like systemd, I mostly just don’t see it anymore - you know what I mean…

          Give it a shot, for me it’s the packaging system, take a look at it and at the github “void-repository”.

          I really like how it’s working, the simplicity of it, create your own package, your own repository, etc.

          The killer features, for me, isn’t really runit, but the stability of a rolling distro with the xbps package system.

      • Atemu@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        19 days ago

        staging rebuild cycles only happen every two weeks or so.

        The reason is always that something changed and causes all dependent packages to change, requiring a rebuild of those too.

  • AwkwardLookMonkeyPuppet@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    19 days ago

    I have an Arch laptop that I didn’t update for 3.5 years. The system update took a while when I finally went through with it. Amazingly it didn’t break anything!

    • SunRed@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      18 days ago

      Yes, I am amazed that quite a few people in this thread are saying they ‘had to completely reinstall the os’ and that it broke everything after not much time. As long as one doesn’t rely on the AUR for system critical packages or much in generel, it is incredibly hard to break an Arch system (Manjaro and other Arch-based distros don’t count). This is due in part to Arch being quite reproducible but it also having very good maintainership.
      It doesn’t hurt to apply new package configs by going through pacdiff once in a while though.

      Edit: Typo

      • Fonzie!@ttrpg.network
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        18 days ago

        I ran a base-Arch with i3 before, I got tired of restoring backups and fixing things and went back to Debian. It broke too quickly by its defaults in my experience.

    • thingsiplay@beehaw.org
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      19 days ago

      So you neglected the operating systems maintained regularly, despite it being a rolling release? I assume you didn’t read the manual intervention instructions that are posted regularly too. I don’t understand people using a rolling release and then not caring about the maintenance. Off course it won’t end very well.

      • MyNameIsRichard@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        19 days ago

        I used Tumbleweed for eight years with no problems. I only moved to EndeavourOS because Suse bared their corporate teeth and I got fed up being a couple of generations behind on the Nvidia drivers. EndeavourOS is also good.

      • WeAreAllOne@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        19 days ago

        Used tumbleweed for ages. No issues. Switched to slowroll again with no issues. Now trying fedora. All with Kde plasma.

  • nomen_dubium@startrek.website
    link
    fedilink
    arrow-up
    3
    ·
    19 days ago

    welp, looks like you don’t use python virtualenvs… well i guess jokes on you all your shit is probably broken now (and as a bonus, that’s probably a big part of the donwload size as well) :p

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    19 days ago

    Sometimes I wish someone would make a an Arch box and come back to it years later to see the updates it has missed.

    But that’s assuming an Arch box would be reliable enough to stay alive that long lol.

    Always heard of 20+ year old bsd and debian machines chugging along with no issue.

    • Ephera@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      19 days ago

      It won’t rise much beyond that, since you only get one update per package. Whether it’s upgrading Firefox from version 120 to 121 or to version 130, it doesn’t change much in terms of download size, nor the number of updates.

      At least, I assume, Arch doesn’t do differential updates. On some of the slower-moving distributions, they only make you download the actual changes to the files within the packages. In that case, jumping to 121 vs. 130 would make more of a difference.

      If you do want lots of package updates, you need lots of packages. The texlive-full package is always a fun one in that regard…

    • nous@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      19 days ago

      I have updated arch systems that had not been powered on for years before. It was fine. No issues what so ever. Arch is not some flaky distro that breaks if you look away for a minute. My main system has had had the same install for over 5 years now and I regularly forget to update it for months at a time. Again, no issues.

      • kautau@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        19 days ago

        Yeah really the biggest issue I could see is pacman’s keyring being so out of date that it has to be manually refreshed with a new one

  • Mwa@lemm.ee
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    19 days ago

    This is why I Dont use rolling release Distros on Pcs i wont use often.

    • GHiLA@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      19 days ago

      I used to care but with recovery tools being what they are and most apps being containers… my base systems tend to be a little more disposable.

      That said, I haven’t had problems, even if I am at risk for more of them. I have my snapshots and my backups.

      • Mwa@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        19 days ago

        Because you get a update once a update for a package comes out, If you dont update for a very long time you need to download a very large update.

        • thingsiplay@beehaw.org
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          19 days ago

          Sure, and that’s exactly what you want if you are on a rolling release, isn’t it? If you neglect the rolling release for a month, what did you expect would happen? Also if you have more apps and packages, the more updates will come out. Rolling releases are for people who maintain the system and care about the updates.

          • Mwa@lemm.ee
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            19 days ago

            What if my pc breaks down or I cannot use it for a month or smth.
            On servers and pcs I don’t use often yeah its fair

            • thingsiplay@beehaw.org
              link
              fedilink
              arrow-up
              1
              ·
              19 days ago

              Read the manual intervention notes from Arch that could be important. And do the update. That’s normal and nothing to worrry about, if you know what you are doing.

  • dingdongitsabear@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    19 days ago

    I’m sorry, I gotta - you have the menu on AND the button bar? like, why? you click on those things? you got your screen real-estate on a sale, what?

    • idefix@sh.itjust.works
      link
      fedilink
      arrow-up
      0
      ·
      19 days ago

      Are you talking about the 2 bars at the top of the window? If yes, I find them more useful than the used space. Probably a matter of taste

      • dingdongitsabear@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        19 days ago

        oh, of course, sorry if I came off harsh. it’s just, I escaped Gnome’s gigantic title bars and useless buttons in it occupying like half the screen, and couldn’t wait to turn it all off in Konsole, so I’m kinda baffled with anyone having them on. just FYI, check out the keyboard shortcuts for Konsole and you’ll boost your productivity considerably.

        edit: this one’s mine. there are many like it but this one’s mine.

        • Zombie@feddit.uk
          link
          fedilink
          arrow-up
          1
          ·
          19 days ago

          Keyboard shortcuts mean memorising. Some people have issues with memory. On-screen buttons mean no memorising.

          That’s the cool thing about Linux. You can customise it to your own needs and desires. Everybody is different.