• wildbus8979
    link
    fedilink
    arrow-up
    87
    arrow-down
    3
    ·
    edit-2
    6 months ago

    Remember kids, you gotta use rm -rf --no-preserve-root /* now a days!

    • Barbarian
      link
      fedilink
      arrow-up
      48
      ·
      edit-2
      6 months ago

      rm -rf /* will work just fine (assuming sudo permissions ofc)

      You need the additional flag for rm -rf --no-preserve-root /

      • ImplyingImplications@lemmy.ca
        link
        fedilink
        arrow-up
        45
        ·
        6 months ago

        Too many people got trolled into “removing the French language pack” on Linux systems that there’s now a check to see if someone is deleting every file off their computer (including the os system files). --no-preserve-root is the option you need to include to actually delete all the files off your system.

        • Jumuta
          link
          fedilink
          arrow-up
          5
          ·
          6 months ago

          weird how it doesn’t warn you for rm -rf /* though

          • lseif@sopuli.xyz
            link
            fedilink
            arrow-up
            8
            ·
            6 months ago

            depending on your shell, i believe the glob is expanded before it gets to the rm program

      • wander1236
        link
        fedilink
        arrow-up
        29
        ·
        6 months ago

        Contrary to the memes, Linux does actually sometimes try to stop you from shooting yourself in the foot

      • CCF_100
        link
        fedilink
        English
        arrow-up
        14
        ·
        6 months ago

        Overrides the protection in place that prevents you from deleting the root of your filesystem.

  • Onno (VK6FLAB)@lemmy.radio
    link
    fedilink
    arrow-up
    83
    ·
    6 months ago

    One of my colleagues managed to accidentally run something like rm -rf /var/tmp/ * on a Solaris machine that was the mail server for the entire organisation.

    After the command finished they realised that the inadvertent space in front of the asterisk meant that the command did slightly more damage than intended.

    They were told to leave the machine running to be able to fix it from a backup, but they rebooted instead.

    An open file is still usable even after it’s been deleted, so the kernel and shell were still up and running … before the reboot …

    If I recall, it took weeks to fix, involving floppy disks, Sun engineers and much egg on face.

    • Kairos@lemmy.today
      link
      fedilink
      arrow-up
      29
      ·
      edit-2
      6 months ago

      The rm command REALLY needs to have the -f flag changed edit: to mean “ignore write protection” not “go turbo fuckery mode”

      • Onno (VK6FLAB)@lemmy.radio
        link
        fedilink
        arrow-up
        25
        arrow-down
        1
        ·
        6 months ago

        Yeah, except for root that is exactly how it works.

        As root you are permitted to shoot your own foot and are expected to know how to aim.