• yamanii@lemmy.world
    link
    fedilink
    arrow-up
    56
    arrow-down
    3
    ·
    8 months ago

    I thought the point of Linux was not doing this every year like with Windows?

    • Ibaudia@lemmy.world
      link
      fedilink
      English
      arrow-up
      43
      ·
      8 months ago

      Realistically you don’t have to if you’re not constantly tinkering, but if you’re changing a lot of low-level stuff without knowing what you’re doing, you have the ability to break things. If you don’t know how to fix them, then it’s easier to just reformat. Basically it’s a skill issue lol.

      • eletes@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        7
        ·
        8 months ago

        I’ve broke things often and had to reinstall a lot because I didn’t know what I was doing. Still kinda don’t know, but do y’all recommend anyways to learn the knowledge?

        Like I could probably read through man pages but I want something that shows how everything builds on each other to fill any gaps I’m missing

        • CalicoJack@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          8
          ·
          8 months ago

          The Arch Linux Wiki is an incredible resource, even if you’re running another distro. Most of it is pretty universal (other than specific commands like the package manager), and it explains how everything functions and fits together. If I’m troubleshooting, it’s always my first stop.

        • PainInTheAES@lemmy.world
          link
          fedilink
          arrow-up
          7
          ·
          edit-2
          8 months ago

          Just keep breaking stuff! It means your learning and trying new things, for the most part. Eventually you’ll just break stuff less and less or know what to look for when something breaks. On that note do try to struggle with something a little bit before rolling back or reinstalling.

        • Ibaudia@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          Depends on what you’re breaking I guess. If it’s DE stuff, kernel stuff, etc. Usually I just find a good YouTube tutorial if I want to learn something new and don’t know what I’m doing.

        • jozep@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          I would recommend reading the manuals yes. Their are many manuals and not all are equal. The man pages can feel a bit strange as they list everything the software can do. To learn I found the archwiki to be better. (Also info manuals but many people are weirded out by the controls used to read these.)

          Also don’t blame yourself for reinstalling if you mess up. It’s normal especially if you need the computer to actually work in a timely fashion

      • fuck_u_spez_in_particular@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        8 months ago

        Yep tinkering with the system is probably the main issue (for that NixOS is awesome btw.). But even when you’re not constantly tinkering. System-State accumulates over time, bugs are also apparent in (upgrading of) distros, and the maintainers of a distro cannot realistically handle every upgrade time-point x -> y, so stuff will likely break after some time.

        But even when I have fixed all the issues in my previous at some time broken distros, at some point it just feels good to have a freshly installed system without all that dirty accumulated state (NixOS + impermanence and you’ll have that every reboot :P, see also this)

    • Hexarei@programming.dev
      link
      fedilink
      arrow-up
      14
      arrow-down
      1
      ·
      8 months ago

      I’ve been running the same installation of Manjaro since 2018, across three different machines. Each time I’ve upgraded hardware I just pop the SSD out and stick it in the new motherboard. Zero instability or troubles from that. Meanwhile I’ve done that to my wife’s Windows PC and it resulted in going through a whole rigmarole with calling Microsoft because the OS install was suddenly no longer activated.

      Linux didn’t even care that I went from AMD to Intel to AMD.

      • ikidd@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 months ago

        I have 3 clones of my 10yo Manjaro desktop install running on other hardware around my network, including a Proxmox VM. It just jumps across, fires up and I fix the hostname, good to go.

        • Hexarei@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          8 months ago

          Cloning a base image and creating VMs from it is one of the coolest things. I do it for my VMs on my Proxmox cluster any time i need a new server for something - and yeah just copying my dev desktop to my new laptop for going to a conference was such a great way to avoid hours of setup

    • kshade@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      edit-2
      8 months ago

      You don’t have to do this, I manage some machines that haven’t been reinstalled for over a decade. It’s really just because “it feels cleaner”, I guess.

    • Rolder@reddthat.com
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      Whose doing it every year with Windows? I’ve had it for years and only reinstalled once when I got a bunch of new hardware

    • agent_flounder@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      8 months ago

      It is nowhere near necessary to reinstall the OS to fix anything… at least for Mint and Raspbian which are the two I’ve used over the last decade. I may have done an upgrade on mint a few times. Otherwise it chugged on merrily.

      PS: now that I think about it I’ve never reinstalled windows on my old laptop either. I like to find the root cause of problems and fix them rather than giving up and reinstalling… call me crazy?