![]() The prompt for root access did not exist when I wrote this answer. The absolute best thing to do to is make a copy of a restricted file, edit it, and copy it back when you're absolutely sure it's finished.Īlso for editing files to which your user does not have permissions, I would now recommend Talha Junaid's answer which asks for permissions every single time you want to save a file. I'm not saying that you should never use VSCode as root(though its pretty easy to avoid doing) I'm saying you should be careful when you want to do so and know the risks. It's just good practice on any operating system to run your applications on a user level and leave administrative tasks to the root user, and only on a per-need basis. Or that vulnerability that was just posted in ProFTPD to allow an attacker to gain a ROOT shell. For example, you wouldn't want that recent crash of Rhythmbox to wipe out your entire /usr directory due to a bug. Applications are meant to be run with non-administrative security (or as mere mortals) so you have to elevate their privileges to modify the underlying system. It defeats the security model that's been in place for years. Have fun.įor everyone asking why this isn't recommended, you clearly don't understand why sudo even exists. ![]() Then from the window you can open your project folderĪgain: This is not recommended. ![]() #ARRSYNC RUN AS ROOT CODE#You must specify the user data directory to use when running vs code: sudo code -user-data-dir="~/.vscode-root" The problem is that I don't want to configure the home machine to accept a remote login for a variety of reasons. In other words, I realize I could log into the remote machine, switch to root, and then run RSYNC the other way. ![]() It is very dangerous to run VScode as root (as it is any other application) however, should you absolutely need to: I should also note that I don't want to run it backwards. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |