this post was submitted on 09 Sep 2024
273 points (80.7% liked)
linuxmemes
21410 readers
844 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Never create a file named "-rf *" unless you really plan on keeping it.
Am I missing something?
I'm not sure that you belong in this thread :)
I'm not going to try it but... rm "./-rf *" would do the same? rm "./-rf \*" maybe?
Couldn’t get single quotes to type on my phone, but best to always use them for problems like that, to completely get rid of shell interference.
I always forget about the single quotes.
If you do want to try, just start a docker container and try inside there. That should negate all risk
if you use fish you can tab-cycle tour way to the file
rm ./-rf
I've been using Linux as my main driver for a couple of years now but I didn't know the list of reserved file name characters is so short.
I didn't believe '*' is allowed. That alone is so error-prone, it's insane. Backslash is allowed too - how do you escape that? Sometimes I think they giggled while writing the specs.
It's backslashes all the way down
Just use double backslashes for each backslash