this post was submitted on 13 Sep 2025
201 points (99.0% liked)
linuxmemes
27282 readers
470 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 users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- 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.
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
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
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 remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
i think the better way would be to replace rm with something that just moves files to a trash bin like how graphical file managers do it.
if you were just pulling the data back off the disk, and you didnt notice it IMMEDIATELY or a background process is writing some data, it could still be corrupted.
there was something like that i had on win3.2 called like undel.exe or something, but same deal, often it was courupted somehow by the time i was recovering the data
I usually don't think about it at all, but every now and then I'm struck by how terrifyingly destructive
rm -r
can be.I'll use it to delete some build files or whatever, then I'll suddenly have a streak of paranoia and need to triple check that I'm actually deleting the right thing. It would be nice to have a "safe" option that made recovery trivial, then I could just toggle "safe" to be on by default.
I think one solution is (browseable) Snapshots
Honestly, after re-reading my own comment, I'm considering just putting some stupid-simple wrapper around
mv
that moves files to a dedicated trash bin. I'll just delete the trash bin every now and then...-Proceeds to collect 300 GB of build files and scrapped virtual environments over the coming month-
There are solutions already. Just use them instead of
rm
https://wiki.archlinux.org/title/Trash_management
Then can alias rm to
echo Use trash instead!
or something. You wanna build new habits, not co-opt rm, it could happen easily that you're ssh'd into a system where your rm alias doesn't exist or similarMy thought wasn't to alias
rm
, but rather to make a function likermv <file>
that would move the file to a trash directory.But of course this already exists- thanks for pointing me to the resource:)
This breaks the advice to never alias a standard command to do something radically different from its regular function.
Sure, go ahead and alias
ls
to have extra options like--color
, but don't aliasrm
to do nothing, or evenrm -i
(-i
is interactive and prompts for each file).Why? Because one day you'll be logged into a different system that doesn't have your cushioning alias and whoops, bye-bye files.
Now that you think about it, you thought that
ls
output looked weird, but that didn't actually break anything.As you suggest, yes, look into your OS's trash option, but leave
rm
alone.GNOME-derived systems can use
gio trash fileglob
(orgvfs-trash
on older systems) to put things in the actual desktop trash receptacle.KDE's syntax sucks, but it's
kioclientX move fileglob trash:/
whereX
may or may not be present and is a version number of some kind.You could set up a shell function or script that fixes that syntax and give it any name you like - as long as it doesn't collide with a standard one. On that rare foreign system it won't exist and everything will be fine.
You alias
rm
to do nothing. There is no danger of aliasing rm to echo. The only thing that'll happen is nothing.Or are you seriously suggesting that if you do this, you somehow get used to
rm
doing nothing? Like you'll just start rm'ing randomly because you know it'll echo? I mean, stupider things have happened, but... yeahI admit that of the things
rm
could be aliased to do, it is one of the safer ones. It's still bad practice in my book.My "trick" with this is to mv files I'm very sure I want to be "deleting" into
/tmp
. If it instantly turns out to be a mistake, I can pull it back. Else, it gets purged on reboot.This is usually A-okay for my home server since it reboots so rarely! A desktop machine might give you a little less time to reconsider. But it at least solved the "trash is using 45% of my hard disk now" issue haha.
In the very worst case scenario there's the "Drop everything and run photorec / testdisk" as a last resort!