• centopus@kbin.social
    link
    fedilink
    arrow-up
    41
    ·
    10 months ago

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

    • Bipta@kbin.social
      link
      fedilink
      arrow-up
      37
      ·
      10 months 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
    link
    fedilink
    arrow-up
    21
    ·
    10 months 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.

    • narshee@iusearchlinux.fyi
      link
      fedilink
      arrow-up
      21
      ·
      10 months 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
          link
          fedilink
          arrow-up
          12
          ·
          10 months 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

              • second@feddit.uk
                link
                fedilink
                English
                arrow-up
                7
                ·
                edit-2
                10 months 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

          • FuglyDuck@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            10 months ago

            Anybody brave enough to tell the MS rep this on patch night??

            (You have backups, right?)