this post was submitted on 18 Feb 2026
532 points (99.4% liked)

linuxmemes

30114 readers
1345 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

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.
  • Don't come looking for advice, this is not the right community.
  • 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 figuresWe 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
     

    I accidentally untarred archive intended to be extracted in root directory, which among others included some files for /etc directory.
    I went on to rm -rv ~/etc, but I quickly typed rm -rv /etc instead, and hit enter, while using a root account.

    top 50 comments
    sorted by: hot top controversial new old
    [–] justme@lemmy.dbzer0.com 7 points 8 hours ago

    Reminds me in the t-shirt: "don't drink and root"

    [–] dukatos@lemmy.zip 6 points 9 hours ago

    it could be worse: rm -rv ~ /etc

    [–] rushmonke@ttrpg.network 4 points 9 hours ago* (last edited 9 hours ago)

    I fucking hate using rm for these very reasons.

    There's another program called "trash-cli" that gives you a trash command instead of going straight to deletion.

    I'm not sure why more distros don't include it by default, or why more tutorials don't mention it.

    [–] tulliandar@lemmy.world 12 points 23 hours ago (2 children)

    Next time:

    ls ~/etc
    rm -rv !$
    
    [–] filip@sopuli.xyz 1 points 6 hours ago

    This is also dangerous because you could run the second command by accident later when browsing command history

    [–] myotheraccount@lemmy.world 3 points 8 hours ago

    Or press alt+. to paste final argument of previous command

    [–] lavander@lemmy.dbzer0.com 13 points 1 day ago (1 children)

    Genuinely curious… why using root for operations like these?

    [–] Viceversa@lemmy.world 12 points 1 day ago

    To feel the thrill

    [–] frozen@lemmy.frozeninferno.xyz 9 points 1 day ago* (last edited 1 day ago) (1 children)

    Reminds me of when I had a rogue ~ direction sitting in my own home directory (probably from a badly written script). Three seconds into rm -rf ~ and me wondering why it was taking so long to complete, I CTRL+C, reboot, and pray.

    Alas, it was a reinstall for me that day (good excuse to distro hop, anyway). Really glad I don't mount my personal NAS folder in my home directory anymore, holy shit.

    [–] MonkeMischief@lemmy.today 50 points 1 day ago (5 children)

    OOOOOOOOOOOF!!

    One trick I use, because I'm SUPER paranoid about this, is to mv things I intend to delete to /tmp, or make /tmp/trash or something.

    That way, I can move it back if I have a "WHAT HAVE I DONE!?" moment, or it just deletes itself upon reboot.

    [–] MonkderVierte@lemmy.zip 12 points 1 day ago* (last edited 1 day ago) (1 children)

    Just get a cli trash tool and alias it to rm. Arch wiki

    [–] MonkeMischief@lemmy.today 19 points 1 day ago* (last edited 23 hours ago) (2 children)

    That's certainly something you can do! I would personally follow the recommendation against aliasing rm though, either just using the trash tool's auto complete or a different alias altogether.

    Reason being as someone mentioned below: You don't want to give yourself a false sense of security or complacency with such a dangerous command, especially if you use multiple systems.

    I liken it to someone starting to handle weapons more carelessly because the one they have at home is "never loaded." Better safe than sorry.

    Lol we should have "rules of rm safety":

    • Assume rm is always sudo unless proven otherwise.
    • (EDIT)Finger should be off the Enter key until you are certain you are ready to delete.
    • Never point rm at something you aren't willing to permanently destroy.
    • Always be aware of your target directory, and what is recursively behind it!
    [–] rushmonke@ttrpg.network 1 points 8 hours ago

    Yeah, there's no need to alias it. Trash-cli comes with its own trash command.

    [–] sylveon@lemmy.blahaj.zone 6 points 22 hours ago

    I think this is the best approach. I've created a short alias for my trash tool and also aliased rm to do nothing except print a warning. This way you train yourself to avoid using it. And if I really need it for some reason I can just type \rm.

    If you want to train yourself even more effectively you can also alias rm to run sl instead :)

    [–] Alberat@lemmy.world 7 points 1 day ago

    i always do "read;rm ./file" which gives me a second to confirm and also makes it so i don't accidentally execute it out of my bash history with control-r

    Also stealing this. What an awesome tip

    [–] Tangent5280@lemmy.world 8 points 1 day ago (1 children)

    Hey that's a pretty good idea. I'm stealing that.

    [–] ICastFist@programming.dev 5 points 1 day ago (5 children)

    After being bitten by rm a few times, the impulse rises to alias the rm command so that it does an β€œrm -i” or, better yet, to replace the rm command with a program that moves the files to be deleted to a special hidden directory, such as ~/.deleted. These tricks lull innocent users into a false sense of security.

    load more comments (5 replies)
    load more comments (1 replies)
    [–] kertain@sh.itjust.works 12 points 1 day ago

    I am new to Linux and just getting somewhat comfortable as my daily driver, very proud of myself that I got the joke pretty quickly :)

    [–] Ghostie@lemmy.zip 10 points 1 day ago (1 children)
    [–] wabasso@lemmy.ca 6 points 1 day ago (1 children)

    Ok speaking of this, where do a distro’s config and boot scripts even come from? Are they in a package? Like on Debian so the .debs have metadata that can add cron jobs and such?

    [–] MonkderVierte@lemmy.zip 9 points 1 day ago* (last edited 7 hours ago)

    Yeah, same thing like with unclosed bottles, cup too close to the table edge, etc.: Accidents that can hapen, will happen.
    Better name them something else in your user dir.

    And yes, painful experience.

    Thank god you used -rv and not -rf πŸ˜‚πŸ˜‚πŸ˜‚

    [–] partial_accumen@lemmy.world 170 points 1 day ago (10 children)

    Reusing names of critical system directories in subdirectories in your home dir.

    [–] underscores@lemmy.zip 49 points 1 day ago (1 children)

    I agree with this take, don't wanna blame the victim but there's a lesson to be learned.

    [–] neatchee@piefed.social 58 points 1 day ago* (last edited 1 day ago) (2 children)

    except if you read the accompanying text they already stated the issue by accidentally unpacking an archive to their user directory that was intended for the root directory. that's how they got an etc dir in their user directory in the first place

    load more comments (2 replies)
    load more comments (9 replies)
    [–] dunz@feddit.nu 16 points 1 day ago

    Be happy that you didn't remeber the ~ and put a space between it and etcπŸ˜ƒ.

    Ohohoho man did you ever fuck up. I did that once too. I can't remember how I fixed it. I think I had to reinstall the whole OS

    [–] w3ird_sloth@lemmy.world 3 points 1 day ago

    That's what tools like trash-cli are for.

    [–] quelsh@programming.dev 104 points 2 days ago (2 children)

    HAH rookie, I once forgot the . before the ./

    [–] Viceversa@lemmy.world 2 points 10 hours ago

    Nvidia once did it in their install script

    load more comments (1 replies)
    [–] Treczoks@lemmy.world 11 points 1 day ago

    Ahh, the rites of passage!

    [–] ICastFist@programming.dev 20 points 1 day ago (12 children)

    So good to see that, even in 2026, Unix Haters' Handbook's part on rm is still valid. See page 59 of the pdf

    load more comments (12 replies)
    [–] Thrydwulf@lemmy.today 33 points 1 day ago

    β€œJust a little off the top please”

    I've had a combination of tab complete and filename spaces lead to things like rm Some\ Common\ Prefix * at least three times. Instant regret. I've now got a pretty good intuitive reflex around this type of thing. You eventually get enough callouses.

    [–] Loce@lemmy.world 22 points 1 day ago

    Things like these are right of passage on Linux :)

    load more comments
    view more: next β€Ί