176
Who hasn't typed a risky command? Throw the first stone! (programming.dev)
submitted 4 months ago by to c/programmer_humor@programming.dev
21 comments fedilink hide all child comments
 

Sudo rm -rf .

you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 4 months ago (2 children)

DOS user detected! In linux you don't need *.*, you can just use *

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

    Maybe he wanted to remove only files with a dot in the name

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

    And if he’s on / (root) on most common distros, there won’t be any dirs with . (dot) in their name. Unless this matches the dot from the cwd, in which case this is the same as “rm -rf /“? Now I’m curious, I don’t often perform operations on the cwd using dot.

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

    At least bash doesn't seem to match it...

    gregor@raspberrypi:~ $ ls
bridge  navidrome  seed  traefik
gregor@raspberrypi:~ $ ls *.*
ls: cannot access '*.*': No such file or directory
gregor@raspberrypi:~ $ cat *.*
cat: '*.*': No such file or directory
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 4 months ago* (1 child)

    Right, so then if asterisk wildcards don’t match on . and .. then, in most common distros where there is no dot in any of the top level dirs in /, “rm -rf *.*” in the top level / dir is basically harmless and likely a noop.

    So OP is wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •