• stoy@lemmy.zip
    link
    fedilink
    arrow-up
    127
    arrow-down
    6
    ·
    12 days ago

    That is idiotic, there is absolutely a reason to reinstall in some cases

    • fl42v@lemmy.ml
      link
      fedilink
      arrow-up
      22
      arrow-down
      3
      ·
      12 days ago

      Not when you’re “stuck”, tho. You understand the problem, boot live system, fix it and learn from your mistakes. Like, my first reinstalls of arch were due to not understanding I can just chroot or pacstrap some packages I forgot, for example.

    • QuarterSwede@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      12 days ago

      Some times but not most, like Windows. macOS is the same way thanks to its *nix underpinnings. I honestly can’t remember a time I ever reinstalled the system to fix a problem.

    • KubeRoot@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      12 days ago

      With the way most distros are structured, you should never need a reinstall, since reinstalling the packages will fix any issues with broken system files. Broken configuration wouldn’t be as easy to fix, but still something you should be able to fix.

      The only reason to be reinstalling, in my eyes, is if you have a mess of packages and configuration you don’t remember, and want to get a clean slate to reconfigure instead of trying to figure out why everything was set up in a certain way.

      • stoy@lemmy.zip
        link
        fedilink
        arrow-up
        22
        arrow-down
        1
        ·
        12 days ago

        As an IT guy who has worked professionally as a Linux sysadmin.

        While you are correct, the factor you are missing is time.

        There have been countless times I have reinstalled Linux machines because it is faster than troubleshooting the issue

        • anamethatisnt@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          11 days ago

          Professionally on a non-recurring issue - absolutely.
          With my stuff at home? Only if the wife suffers from the downtime.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          11 days ago

          If you do it right you should be able to trigger rebuild within about 20 min by kicking off the right automation.

          Virtualization and containerization are your friends. Combine that with Ansible and you are rock solid.

        • KubeRoot@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 days ago

          Fair, but machines at work as sysadmin are a different thing - hopefully there you’re also dealing with fast deployment, prepared ahead of time. But if the issue is that you messed something up on your own computer, ignoring the issue in favor of reinstalling sounds likely to leave you oblivious to what the issue was, and likely to repeat your mistake.

          • stoy@lemmy.zip
            link
            fedilink
            arrow-up
            2
            arrow-down
            1
            ·
            11 days ago

            That is fair, but ignores compounding issues like installing several software packages over years and forgetting about them, and something like that causes an issue years after installing and forgetting about the software, then it is far easier to just reinstall.

    • cmnybo@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 days ago

      Unless the drive gets corrupted or infected with malware, you can just load a previous snapshot. That’s much faster and easier than reinstalling.

      • stoy@lemmy.zip
        link
        fedilink
        arrow-up
        2
        arrow-down
        4
        ·
        11 days ago

        Snapshot as in a VM?

        Most people run their OS on physical hardware.

          • stoy@lemmy.zip
            link
            fedilink
            arrow-up
            1
            ·
            11 days ago

            Ah, yeah, I have read about that, I do feel a bir hesitant to use BTRFS so I didn’t think about that.

            The Linux machines I have worked with all ran ext3/4 or xfs.

            To be completely fair, I never gave BTRFS a proper chance, at first because it felt too new and unstable when I heard about it, and later I heard that it was developed by Facebook and let my distaste for that company color my perceptions of btrfs.

            But I just checked the wikipedia article and saw that plenty of reputable oranizations have worked on btrfs, so I guess I’ll get it a go when I build a NAS…

            Thanks for reminding me of it, I may get set in my ways from time to time but I do genuinely try to learn and change my way of thinking.

            • Possibly linux@lemmy.zip
              link
              fedilink
              English
              arrow-up
              4
              ·
              11 days ago

              I wouldn’t use it for a NAS. You want ZFS for that.

              Btrfs is good for small setups with either single or dual disks.

        • Possibly linux@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 days ago

          You can run your desktop inside of a VM with the GPU and USB PCIe devices passed though.

          However, I think they are talking about btrfs

        • ArcaneSlime@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          11 days ago

          Tbf “funny” is, by nature, subjective. Something may be funny to others but not to you, just as you may like onions while I may not, or I may find Shakira attractive while you may not, or I may be into pokemon but you may not, etc.

          So, jokes are supposed to be funny, to someone, but you’re not necessarily that “someone.”