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.
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.
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!
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.