• centopus@kbin.social
    39·
    1 year ago

    If its freshly installed, you still remember how to do it again… 15 minutes and its installed again.

    • Bipta@kbin.social
      37·
      1 year ago

      Worse is managing to type your password and confirm password identically incorrectly. It takes the same 15 minutes, but also 15 minutes of not being able to believe it.

      Based on a true story.

  • bazzett@lemmy.world
    20·
    1 year ago

    Last September I installed Debian 12 in my laptop with an encrypted LVM. Then I tried to add a secondary SSD, also as an encrypted volume, by following some random tutorial I found (spare me, it was my first time fiddling around with an encrypted installation). The next thing I remember is that I was in an initramfs shell trying to fix the boot process 😅🤣. Since I was running low on patience (and it was like 3 AM) I simply decided to nuke the install and start again. Eventually I was able to configure the SSD correctly, but this event reminded me how easily is to brick your system if you’re not careful enough. Fun times.

    • Kepabar@startrek.website
      101·
      1 year ago

      It’s things like this that prevent me from using Linux more.

      I force myself to use it for projects where it’s an option because I feel I need to learn it better but I kind of dread it every time.

      Inevitably I’m stuck frustrated reading conflicting guides from years ago and wondering just how badly I’m going to fuck things up this time.

      Sometimes it all feels so esoteric.

      • seitanic@lemmy.sdf.org
        4·
        1 year ago

        I’ve always loved Linux, even when it was kicking my ass. I can’t imagine approaching it with the attitude “Ugh, I have to force myself to use this thing, and I know that it’s going to frustrate me”.

        That sort of thing is a self-fulfilling prophecy, because everybody has cognitive biases. Since you expect it to be frustrating, you’re going to remember all the times that it is and forget the times when it isn’t.

        • Kepabar@startrek.website
          1·
          1 year ago

          It’s a chicken and egg situation.

          It’s frustrating because I don’t know it, and I don’t learn it because it’s frustrating.

      • spez@sh.itjust.worksEnglish
        3·
        1 year ago

        Get on it. If you can manage to daily drive it for a few months I think you’ll learn a lot. When I jumped ship I only knew basic commands like cd and ls.

    • narshee@iusearchlinux.fyi
      20·
      1 year ago

      Not in this case. It’s */ here so it expands to directories at current location. I’m sure that’s a typo though

        • narshee@iusearchlinux.fyi
          11·
          1 year ago

          You can do echo */ and echo /* to see how they expand. Also rm -rf / already is enough without the * as it already is recursive

          • fl42v
            15·
            1 year ago

            * is there to bypass the need for --no-preserve-root

              • second@feddit.ukEnglish
                7·
                1 year ago

                Originally, rm would merrily nuke your whole filesystem if you told it to. At some point, someone thought that was a pretty stupid default behaviour, so they added that flag to change the default to not nuke your entire filesystem. However, they made the change backwards compatible in case someone still needed the old behaviour. I can imagine in a container or throwaway environment, it might be vaguely reasonable to expect to be able the blat /.

                See also:

                Unix gives you just enough rope to hang yourself – and then a couple of more feet, just to be sure.

                – Eric Allman