Who's in charge?
-
wrote on last edited by [email protected]
God that is great mascot. It sears itself into your brain.
-
This post did not contain any content.
-
One time Windows told me I needed admin privileges to edit s file. I had admin privileges.
You needed permission from the SYSTEM or TrustedInstaller account.
Which you can give to yourself if you are admin.
-
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.
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.
-
Windows moment
wrote on last edited by [email protected]Only if you don't know how to use Windows.
Which I am starting to suspect a ton of Linux users on here are incapable of.
-
Me, realizing I can't delete Edge because the OS assumes it's installed
-
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.
What the hell are you talking about? Permissions issues in Windows have absolutely nothing to do with Microsoft owning your files.
-
That isn't the reason to yeet Windows. If you were talking years ago about 7 or XP, things were different. 10 is not that great comparably, and 11 is a mess. But keep your Windows, if it's what works for you. Until it doesn't.
Dual boot for the best of both worlds (although I'm finding myself more and more on the Linux side because it's better for me.)
Even Windows 11 still has all the options Windows 7 had, and plenty more. Stop swallowing the Linux propaganda.
-
"TakeOwnership Registry Hack" PSA. It just werks.
Why use a hack when you can just go into properties and take ownership there?
The only thing this does is make a shortcut.
-
sudo chown -R 1000:1000 /* && sudo chmod -R 777 /*I use:
alias thisfolderismine='sudo chown -R $USER' alias thisfileismine='sudo chown $USER' -
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.
-
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.
-
This post did not contain any content.
Wrong OS.
-
Now I've learned enough to know that I can easily learn what all that apparent gibberish does with the "man" command, but you have no idea how unbelievably unapproachable this makes Linux look to the uninitiated.
wrote on last edited by [email protected]Create one command "iownyou" that does tbe following: Change the owner of every file on the computer to the default user and make every file readable, writeable, an executable by anyone or anything on the computer. It may not be secure, but on the bright side, you'll never have permission issues again!
-
You needed permission from the SYSTEM or TrustedInstaller account.
Which you can give to yourself if you are admin.
wrote on last edited by [email protected]Last time I did that it didn't work so I figured I will restart and it will recognize then. Windows got a 30 minute update.
When I logged back in my account was gone and still asked for a password. My old password didn't work.
Recovery option also fucked my grub. (Probably just the EFI now that I think about it.)
-
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.
wrote on last edited by [email protected]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.
-
This post did not contain any content.
Ah ah ah! You didn’t say the magic word!
sudo edit the file!
…
Ah ah ah! You didn’t say the secret word right after!
-
Can't shutdown there is a running program
/Me finger immediately goes to the power switch
I still remember the biggest brainfart moment as a child. I was playing video games on my computer, and kinda just looked around. On the pc was a turbo button, so i pressed it, turbo makes games faster. I looked again and one button said power. I wonder what that doe... I'm dumb.
-
This post did not contain any content.
sudo chown....
-
Last time I did that it didn't work so I figured I will restart and it will recognize then. Windows got a 30 minute update.
When I logged back in my account was gone and still asked for a password. My old password didn't work.
Recovery option also fucked my grub. (Probably just the EFI now that I think about it.)
That last bit about GRUB is why I never put Windows on the same drive as my Arch, btw install. If they both have their own EFI partitions, Windows doesn't mess with Linux.
