2026-08-02 19:40 UTC
Replies (9)
-
@jjdavis@infosec.exchange 2026-08-02 19:55
@contrapunctus@fe.disroot.org Scripts using rm have potential issues you might not run in to with using rm interactively. Unfortunately I've learned that from experience.
-
@incentive@mastodon.circlewithadot.net 2026-08-02 20:11
@contrapunctus@fe.disroot.org you've never run "rm -rf *" in the wrong folder? 🫠
-
@mezz@mstdn.games 2026-08-02 19:52
@contrapunctus@fe.disroot.org I've never had that happen with rm either, but I can easily see how that would happen when using stuff like bash wildcards. If I'm feeling particularly paranoid, I'll just do the deleting in a GUI file manager, that moves stuff to trash first.
-
@jautero@indieweb.social 2026-08-02 20:03
@contrapunctus@fe.disroot.org removing (non-empty) directory using rm -rf $PATHNAME/ comes to mind.
-
@neilvandyke@mastodon.online 2026-08-02 20:09
@contrapunctus@fe.disroot.org Here's one way... Me as a teen intern, trying to clean up some dotfile directories in /tmp of a server with an overfull filesystem (with /tmp on /), as root: rm -rf .* Only when it didn't return instantly did I start to realize what I had just done, and hammer ctrl-c to make it stop. Too late.
-
@HaraldKi@nrw.social 2026-08-02 20:16
@contrapunctus@fe.disroot.org rm -rf build/ * There is a fat finger space character in the wrong place.
-
@mcepl@en.osm.town 2026-08-02 20:57
@contrapunctus@fe.disroot.org rm -rf / something Already happened to me (space between / and dirname).
-
@argv_minus_one@mastodon.sdf.org 2026-08-03 03:14
@contrapunctus@fe.disroot.org Yes, you can't footgun yourself with rm if you don't use rm.
-
@realestninja@social.linux.pizza 2026-08-03 03:34
@contrapunctus@fe.disroot.org when you are super tired and/or super stressed