Total noob. Any experienced user knows it's
run0 micro file.txt
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.
Total noob. Any experienced user knows it's
run0 micro file.txt
How dare you using a 21st century terminal editor that keeps you sane? You're supposed to learn a whole new set of archaic key bindings! And suffer!
I'm not sure if that's the joke and it flew over my head but isn't editing with sudo what you should be doing anyway if it's a system level file? You shouldn't change permissions unless the file is actually supposed to be owned by your user.
You are supposed to run sudoedit
.
This command creates a temporary copy, opens it in you editor of choice and overwrites the protected file when the temp file changes.
That way the editor doesn't run as root.
You can see the difference if you run shell command, like whoami
, in vim.
If itโs all my system should I really care about chown and chmod? Is the point that automatic processes with user names like www-data have to make edits, and need permission to do so, and thatโs it?
Newish Linux user btw
This is definitely the way for configuration files that you shouldn't change permissions or ownership on but only want to modify a few times.
However, I find chmod easier to use without reference by using the ugoa (+/-) rwxXst syntax rather than the numbers.
vi