💀☠️

  • sepi@piefed.socialEnglish
    0·
    10 days ago

    This is where we sort the younglings from the grizzled veterans that backup and test their backups. Haven’t lost a file since 2002.

    • Peffse@lemmy.world
      0·
      10 days ago

      I had a coworker preparing a customer database that arrived via sneakernet. He typo’d a variable during an rm -f step and ended up wiping the device because it was his working directory and the variable was undefined.

    • hddsx@lemmy.ca
      0·
      10 days ago

      Nobody deletes “./“. It’s far far more likely to be “/ tmp/file”

      Also, without the -f it will prompt you. Chances are, the meme is with -f

      The other possibility, though I haven’t tested it, is the working directory is / and they did “rm -rf .” Without first checking with pwd. I know that most OS will refuse to remove root without passing in a special flag nowadays. Only a few OS still respect you as sudo.

      • T156@lemmy.worldEnglish
        0·
        10 days ago

        Though the check isn’t very sophisticated, if memory serves. It more or less checks whether / is passed to rm -r.

        If you did something like rm -r $VAR/*, but didn’t check to make sure that $VAR was set and not empty, it could still fire, since rm wouldn’t see that root got passed, only a bunch of directories in root.

  • nemith@programming.dev
    0·
    10 days ago

    At a previous job I remember a PR to do essentially

    temp=$(mktemp -d) mv $target $temp rm -r $temp &

    I thought it was pretty clever. Obviously you would need to make sure mktemp is on the same filesystem (there are good flags to just use a dot file in the current directory). mv is atomic on most filesystems and then the & just runs the rm in the background .

  • 7U5K3N@lemmy.dbzer0.com
    0·
    10 days ago

    Honestly I was cleaning up some docker stuff today…

    So I’m

    rm -r /mnt/NVME/opt/folder(s)

    Hit the refresh button in my gui file browser and it was still there. Lol Took a good 15 seconds for it to vanish.

    Crazy. But idk why I expected it to be instant.

  • Nemoder@lemmy.ml
    0·
    9 days ago

    …and this is the reason I added this to my root .bashrc:
    export PS1="\h:\$(realpath .)\$ "
    no more following symlinks on a remote mount and forgetting about it.

  • ☂️-@lemmy.ml
    0·
    9 days ago

    call me paranoid or stupid but i always use the graphical file manager whenever i can to delete stuff for this very reason.

    • mech@feddit.org
      0·
      9 days ago

      I do the opposite. Whenever I delete anything I use rm -rf.
      Just typing that triggers a fear response and makes me triple-check what I’m doing.

      • unwarlikeExtortion@lemmy.ml
        0·
        8 days ago

        Honestly, this idea has me pretty mortified as well. Just seeing ”rm -rf /” as part of a string sends chills down my spine.

        Granted, any reasons or explanations to cause a string being cut short to this godforsaken form and accidentally run is extremely unlikely, but a valid theoretical possibility: I can easily imagine someone mistyping the first letter after root and, wishing to delete it, pressing Backspace while simultaneously accidentally grazing the Enter key.

        Sure, the chances of it happening are about the same as a gun user accidentally dropping their gun, clumsily catching it in the air and accidentally shooting someone right in between the eyes as a result.

  • janAkali@lemmy.sdf.org
    0·
    9 days ago
    1. create a read-only directory
    2. create regular rw directories inside it
    3. put your files in the writable dirs
    4. create symlinks for convenience (optional)
    5. now you can fuck up rm -rf ~ and it will not delete files in protected directory
    6. just dont fuck up rm -rf ~/protected/writeableDir