this post was submitted on 05 Dec 2023
946 points (98.1% liked)
linuxmemes
20880 readers
6 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You shouldn't really use editor with sudo, but instead use sudoedit to edit files restricted to root user
SUDO_EDITOR=nano sudoedit /etc/fstab
This accomplishes the same function while running the text editor as unprivileged user
Why?
Files from user: nano
Files from root: sudo nano
Files from another user: sudo nano (and if new sudo chown after)... ๐
Never had any problems with this in over 10 years... ๐ ๐
Doing
sudo nano
will not load your user configuration,sudoedit
will. I had plenty of problems with this, but I assume you don't have any custom configuration.One reason why sometime I don't do sudoedit is that I make a lot of changes to the config/restart service/see it works/edit etc.. sudoedit only write to the file when exiting, so that flow won't work...
for example when having adding a new host on nginx and some configuration and see if everything work (sudo vim/systemc nginx restart/curl https:// domain loop)
but yeah in general i'll just use sudoedit (which alias to se for me) for my root editing