126
when you notice that the rm command takes longer to run than expected (lemmy.world)
submitted 10 months ago by to c/programmerhumor@lemmy.ml
20 comments fedilink hide all child comments
 

πŸ’€β˜ οΈ

all 22 comments

sorted by: hot top controversial new old
[–] 46 points 10 months ago (1 child)

Everyone asks what is rm but nobody asks how is rm.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 16 points 10 months ago (1 child)

    Those French dictionaries are massive.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 12 points 10 months ago (1 child)

    Don't delete the french language pack, it's vital to the OS

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 8 points 10 months ago (3 children) 
    sudo rm -r . /
  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 10 points 10 months ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months 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.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 5 points 10 months 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.

  • permalink
  • fedilink
  • source
    •
    [+] 4 points 10 months ago* (last edited 9 months ago) (2 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 3 points 10 months ago

    Use trash-put and trash-cli.

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 10 months ago (2 children)

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

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 4 points 10 months ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 10 months ago*

    Last evening, I deleted a file by mistake in my dhcp server. Five minutes later I had recovered the file from the previous night's backup and was going about my merry way as if nothing happened.
    If humans can make mistakes with the files, you should consider having backups. Having backups is something you decide to engage in BEFORE you have a loss event, so that you are prepared for when humans make their mistakes.
    I am a human, and I know I make mistakes, therefore I prep even my silly infrastructure at home to defend against my sillyness.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 2 points 10 months 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.

  • permalink
  • fedilink
  • source
    •
    [–] 1 point 10 months ago (1 child)

    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 .

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •