this post was submitted on 27 Jun 2025
1147 points (99.5% liked)
memes
15795 readers
3396 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
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
Just to have linux be even more ruthless with its permission schemes.
When you switch to an admin account on Windows, there are still files owned by "TrustedInstaller" that you can't touch, and processes owned by "System" that you can't terminate.
Linux doesn't have that. When you switch to root, you can kill any process. You can modify or delete any file.
Sometimes (often?) at your own peril!
To anyone else following, if you're mucking around with "I am Root/Admin. OBEY ME!!" you had better have important data backed up!
I once thought an unlisted BTRFS snapshot was an orphan folder taking up space. No permission? Nonsense! Obey my commands!
Suddenly not even terminal commands worked. ("Command 'cd'/'ls'/whatever not found")
. . . it was the "writable snapshot" currently mounted, and the system was so borked it couldn't rollback, and I needed to completely reinstall.
Fortunately I had things backed up on another drive. Live and learn! But that could have been TRAGIC.
sudo edit this file!