this post was submitted on 27 Jun 2025
1059 points (99.5% liked)
memes
15795 readers
4868 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
To own something is to control it.
You clearly don't have control, therefore you don't own it, microsoft does. You can fix that by seizing the means of computation and install linux.
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!
What the hell are you talking about? Permissions issues in Windows have absolutely nothing to do with Microsoft owning your files.
I'm not talking about just the files. I'm talking more generally.
That's a weird stance to take since the discussion was about file permissions, and there are absolutely ways around Windows protecting system files just like there are ways around Linux doing the same thing.
There are many reasons to criticize Microsoft, but making it difficult for users to fuck up system files isn't one of them. Most users are of the "it's a box filled with magic smoke" variety, and they need to be protected from themselves.
Or just ... right click to change ownership...
You don't have to change your whole OS because you can't access a file. I thought you Linux users knew how to use technology properly. But it seems you are "power users" instead.
Like I said to /u/entwine413 I am talking more generally, not just about literal files.