this post was submitted on 05 Dec 2023
936 points (98.0% liked)

linuxmemes

20742 readers
1133 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. 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
[โ€“] hemko@lemmy.dbzer0.com 23 points 9 months ago (29 children)

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

[โ€“] doctorn@r.nf 10 points 9 months ago* (last edited 9 months ago) (20 children)

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... ๐Ÿ˜…๐Ÿ˜‚

[โ€“] Hawk@lemmy.dbzer0.com 14 points 9 months ago (2 children)

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.

[โ€“] samuelc@lemmy.world 9 points 9 months ago* (last edited 9 months ago)

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

load more comments (1 replies)
load more comments (18 replies)
load more comments (26 replies)