this post was submitted on 11 Nov 2023
178 points (83.7% liked)

linuxmemes

20765 readers
2100 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] narshee@iusearchlinux.fyi 15 points 10 months ago (9 children)

Not in this case. It's */ here so it expands to directories at current location. I'm sure that's a typo though

[–] rockSlayer@lemmy.world 5 points 10 months ago (8 children)

I'm not brave enough to test it on my distro, so I'll take your word on that lol

[–] narshee@iusearchlinux.fyi 11 points 10 months ago (7 children)

You can do echo */ and echo /* to see how they expand. Also rm -rf / already is enough without the * as it already is recursive

[–] second@feddit.uk 4 points 10 months ago* (last edited 10 months ago) (2 children)

rm -rf / needs --no-preserve-root on GNU coreutils, I think.

[–] cupcakezealot@lemmy.blahaj.zone 1 points 10 months ago (1 children)

why do they even have that lever

[–] second@feddit.uk 6 points 10 months ago* (last edited 10 months ago)

Originally, rm would merrily nuke your whole filesystem if you told it to. At some point, someone thought that was a pretty stupid default behaviour, so they added that flag to change the default to not nuke your entire filesystem. However, they made the change backwards compatible in case someone still needed the old behaviour. I can imagine in a container or throwaway environment, it might be vaguely reasonable to expect to be able the blat /.

See also:

Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure.

-- Eric Allman

load more comments (4 replies)
load more comments (4 replies)
load more comments (4 replies)