Reboot, 10 seconds later: Oh good, it works.
Be Root, 10 hours later: Why won't this work!?
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.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.
Reboot, 10 seconds later: Oh good, it works.
Be Root, 10 hours later: Why won't this work!?
sudo reboot
sudo reboot now, because waiting's for chumps
You guys log in as regular users?
No please don't encourage running things as root as a random troubleshooting step. Only run as root if you understand what you are doing and know what the command is going to do.
Disregard this comment, become root and then run rm -rm /*
to fix many common pc problems (it won't wipe your drives :trollface:) ~s~
This is the way.
Real admins screw instead of root
For Mac Problems,
Lick Boot
software guide: if it fails to run, it needs configuration. you really shouldn't run this thing as root
me: πΆhow bout I do anywayπΆ
I mean, whatβs the worst that could go run with running pip
as root?
But in order to configure you need to be root in many cases.
Clever
I want that pengin on a tshirt
sudo shutdonw -r NOWWW
Reinstall Windows, get new, different problems π€‘
restart systemd service-> Restart Shell -> Reboot OS -> Reinstall OS