entityMap|blocks|key|evair|text|这经常发生在我身上，我打开一个根文件来写：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c3or1|而不是丢失所有更改并使用sudo重新打开。请参阅此演示，了解如何保存这些更改：|71nbh|为较低级别的用户创建根用户拥有的只读文件的一次性设置演示：|cq6tu|sudo+touch+temp.txt
sudo+chown+root:root+temp.txt
sudo+chmod+775+temp.txt
whoami
el|code-block|syntax|javascript|52aij|首先以普通用户身份打开文件：|16vdj|vi+temp.txt|5q7ll|然后对文件进行一些更改，它会警告您它是只读的。使用此命令。|ekrpt|:w+!chmod+777+%25|fkn0l|然后写入文件：|28ii5|:wq!|2589o|将展开权限，并保存文件。您需要使用感叹号，因为您是以较小的用户身份编辑根文件。|4i49j|对该命令作用的解释：|45gd9|:w表示写入文件。bang的意思是开始解释为shell。chmod表示更改权限，777表示所有地方的全部权限。百分比表示当前文件名。|1lsov|它会应用更改。它会询问您是否要重新加载。按"O“表示"Ok”。不要重新加载，否则会丢失所做的更改。^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|15|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|16|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|17|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|18|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|19|9|@]|A|@]|B|$]]|$2|N|4|O|6|I|8|1A|9|@]|A|@]|B|$J|K]]|$2|P|4|Q|6|7|8|1B|9|@]|A|@]|B|$]]|$2|R|4|S|6|I|8|1C|9|@]|A|@]|B|$J|K]]|$2|T|4|U|6|7|8|1D|9|@]|A|@]|B|$]]|$2|V|4|W|6|I|8|1E|9|@]|A|@]|B|$J|K]]|$2|X|4|Y|6|7|8|1F|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1G|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|1H|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1I|9|@]|A|@]|B|$]]]]

<h2>That happens to me all the time, I open a root file for writing:</h2>

Instead of losing all your changes and re-opening with sudo. See this demo of how to save those changes:

One time Setup demo to create a root owned read only file for a lower user:

<pre><code>sudo touch temp.txt
sudo chown root:root temp.txt
sudo chmod 775 temp.txt
whoami
el
</code></pre>

First open the file as normal user:

<pre><code>vi temp.txt
</code></pre>

Then make some changes to the file, it warns you its read only. Use this command.

<pre><code>:w !chmod 777 %
</code></pre>

Then write the file:

<pre><code>:wq!
</code></pre>

The permissions are expanded, and the file is saved. You need the exclamation point because you are editing a root file as a lesser user.

Explanation of what that command does:

The :w means write the file. The bang means start interpreting as shell. chmod means change permissions, 777 means full permissions everywhere. The percent means the current file name. 

It applies the change. And it ask if you want to re-load. Press "O" for "Ok". Don't reload or you'll lose your changes.

entityMap|blocks|key|3g3nf|text|对我来说，有一个非常简单的解决方案。我试着编辑/创建文件夹中不存在的文件。因为我已经在我正在尝试的文件夹中编辑/创建中的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cnvis|即pwd+folder/file|offset|length|style|CODE|3sqh9|并且正在输入|149k2|sudo+vim+folder/file|code-block|syntax|javascript|77lle|更明显的是，它正在查找文件夹中的文件夹，但未能保存。^0|0|1|F|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|S|9|@$E|T|F|U|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|V|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|W|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|X|9|@]|A|@]|B|$]]]]

For me there was was quite a simple solution. I was trying to edit/create a file in a folder that didn't exist. As I was already in the folder I was trying to edit/create a file in.

i.e. <code>pwd folder/file</code>

and was typing 

<pre><code>sudo vim folder/file
</code></pre>

and rather obviously it was looking for the folder in the folder and failing to save.

entityMap|blocks|key|2bdnj|text|或者您可能在一个只读的挂载文件系统上|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

Or perhaps you are on a readonly mounted fs

entityMap|blocks|key|co6mh|text|我在level+2中引用了Zsolt，我输入：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|652do|:w+!sudo+tee+%25+>+/dev/null|code-block|syntax|javascript|2rrhs|然后在我的情况下，我仍然不能修改文件，所以它提示添加"!“。所以我输入|8cp11|:q!|flufm|然后它就能工作了^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|N|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|O|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|P|9|@]|A|@]|B|$]]|$2|J|4|K|6|E|8|Q|9|@]|A|@]|B|$F|G]]|$2|L|4|M|6|7|8|R|9|@]|A|@]|B|$]]]]

I referenced to Zsolt in level 2, I input: 

<pre><code>:w !sudo tee % &gt; /dev/null
</code></pre>

and then in my situation, I still can't modify the file, so it prompted that add "!". so I input 

<pre><code>:q! 
</code></pre>

then it works

entityMap|blocks|key|4vdv|text|因为目录不存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|85fqi|可以使用:!mkdir+-p+/etc/apt/创建目录。|offset|length|style|CODE|103il|然后:wq^0|0|4|K|0|2|3^^$0|$]|1|@$2|3|4|5|6|7|8|K|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|L|9|@$E|M|F|N|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|O|9|@$E|P|F|Q|G|H]]|A|@]|B|$]]]]

because the dir is not exist.
can use <code>:!mkdir -p /etc/apt/</code> to make the directory.
then <code>:wq</code>

entityMap|blocks|key|dcqen|text|对于我来说，在运行vim之前将文件系统从只读更改为：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|9tgt2|bash-3.2#+mount+-o+remount+rw+/|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

for me worked changing the filesystem from Read-Only before running vim:

<pre><code>bash-3.2# mount -o remount rw /
</code></pre>

entityMap|blocks|key|26k1e|text|将用户更改为root|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6jomq|sodu+su+-|code-block|syntax|javascript|5v0pm|浏览至etc|3nd56|vi+sudoers|1bggf|在用户权限部分查找root用户。你会得到这样的结果|fgk1f|root+ALL=(ALL:ALL)+ALL|teo|对您的用户名进行相同的输入。如果您的用户名是'myuser‘，则添加|86dtb|myuser+ALL=(ALL:ALL)+ALL|4e73j|它看起来就像|4rts7|root+ALL=(ALL:ALL)+ALL+

myuser+ALL=(ALL:ALL)+ALL|7304o|省省吧。将root用户更改为您的用户。现在尝试与获取sudoers问题相同的方法^0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|Z|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|10|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|11|9|@]|A|@]|B|$]]|$2|J|4|K|6|E|8|12|9|@]|A|@]|B|$F|G]]|$2|L|4|M|6|7|8|13|9|@]|A|@]|B|$]]|$2|N|4|O|6|E|8|14|9|@]|A|@]|B|$F|G]]|$2|P|4|Q|6|7|8|15|9|@]|A|@]|B|$]]|$2|R|4|S|6|E|8|16|9|@]|A|@]|B|$F|G]]|$2|T|4|U|6|7|8|17|9|@]|A|@]|B|$]]|$2|V|4|W|6|E|8|18|9|@]|A|@]|B|$F|G]]|$2|X|4|Y|6|7|8|19|9|@]|A|@]|B|$]]]]

change user to root

<pre><code>sodu su -
</code></pre>

browse to etc

<pre><code>vi sudoers
</code></pre>

look for root user in user priviledge section. you will get it like 

<pre><code>root ALL=(ALL:ALL) ALL 
</code></pre>

make same entry for your user name. if you username is 'myuser' then add

<pre><code>myuser ALL=(ALL:ALL) ALL
</code></pre>

it will look like 

<pre><code>root ALL=(ALL:ALL) ALL 

myuser ALL=(ALL:ALL) ALL 
</code></pre>

save it. change root user to your user. now try the same where you were getting the sudoers issue

entityMap|blocks|key|fsu1c|text|尝试以root用户身份连接，然后编辑文件。这对我很有效|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

Try to connect as root and then edit file. This works for me

entityMap|blocks|key|9f8jn|text|在命令前附加sudo。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|ea8kl|例如，不是vim+textfile.txt，使用sudo+vim+textfile.txt。这将解决问题。^0|6|4|0|5|G|O|L^^$0|$]|1|@$2|3|4|5|6|7|8|I|9|@$A|J|B|K|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|L|9|@$A|M|B|N|C|D]|$A|O|B|P|C|D]]|E|@]|F|$]]]]

Pre-append your commands with <code>sudo</code>.
For example, Instead of <code>vim textfile.txt</code>, used <code>sudo vim textfile.txt</code>. This will resolve the issue.

entityMap|blocks|key|87f9t|text|您正在访问的文件可能在同一目录中已有交换副本(或交换版本|type|unstyled|depth|inlineStyleRanges|entityRanges|data|e436q|因此，首先查看是否存在隐藏文件。|8mt5a|例如，有关以下类型的文件，请参见|6hv4o|.system.conf.swp|code-block|syntax|javascript|2spto|通过使用命令|ebt9m|ls+-a|fl9o0|然后，使用...删除它。|2ar86|rm+.system.conf.swp|ci7oj|通常，我建议开始使用超级用户权限...|72q26|sudo+su^0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|X|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Y|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|Z|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|10|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|11|9|@]|A|@]|B|$]]|$2|N|4|O|6|I|8|12|9|@]|A|@]|B|$J|K]]|$2|P|4|Q|6|7|8|13|9|@]|A|@]|B|$]]|$2|R|4|S|6|I|8|14|9|@]|A|@]|B|$J|K]]|$2|T|4|U|6|7|8|15|9|@]|A|@]|B|$]]|$2|V|4|W|6|I|8|16|9|@]|A|@]|B|$J|K]]]]

It might be possible that the file you are accessing has a swap copy (or swap version) already there in the same directory

Hence first see whether a hidden file exists or not.

For example, see for the following type of files

<pre><code>.system.conf.swp
</code></pre>

By using the command 

<pre><code>ls -a
</code></pre>

And then, delete it using ...

<pre><code>rm .system.conf.swp
</code></pre>

Usually, I recommend to start using super user privileges using ...

<pre><code>sudo su
</code></pre>

entityMap|blocks|key|1uf8e|text|当我使用git+rm在目录中的文件上。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|cojen|我在~/gitRepo/code/newFeature中|eml73|在newFeature中只有一个文件。我做了一个git+rm然后尝试使用vi创建一个新文件myNewFile。|an9tp|Ubuntu显示我仍然在newFeature目录中，但实际上git+rm删除了整个目录。|2sh70|我必须退出vi，向上导航一个目录，然后重新创建newFeature目录。^0|4|6|0|0|O|6|0|U|6|0^^$0|$]|1|@$2|3|4|5|6|7|8|O|9|@$A|P|B|Q|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|R|9|@]|E|@]|F|$]]|$2|I|4|J|6|7|8|S|9|@$A|T|B|U|C|D]]|E|@]|F|$]]|$2|K|4|L|6|7|8|V|9|@$A|W|B|X|C|D]]|E|@]|F|$]]|$2|M|4|N|6|7|8|Y|9|@]|E|@]|F|$]]]]

I got this error when I used <code>git rm</code> on a file in a directory. 

I was in something like ~/gitRepo/code/newFeature

In newFeature there was only one file. I did a <code>git rm</code> on that file then tried to create a new file myNewFile using vi. 

Ubuntu showed me as still being inside the newFeature directory but actually <code>git rm</code> had removed the whole directory.

I had to exit out of vi, navigate up one directory and then recreate the newFeature directory.

entityMap|blocks|key|5808d|text|当我的目录路径不正确时，我得到了这个错误，请确保你的目录名称和路径是正确的|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

I got this error when my directory path is incorrect, ensure your directory names and path are correct

entityMap|blocks|key|96igs|text|更改其他用户对该类型的权限setfacl+-m+u:username:rw+filename|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

change the permission for the other user
for that type
setfacl -m u:username:rw filename

entityMap|blocks|key|1rc9d|text|您只需使用root访问权限即可访问Gemfile。之前vi：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2io7g|命令：|8oaq6|sudo+su+-|code-block|syntax|javascript|c9bt4|然后：|btvmr|vi+~/...^0|R|2|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@$A|S|B|T|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|U|9|@]|E|@]|F|$]]|$2|I|4|J|6|K|8|V|9|@]|E|@]|F|$L|M]]|$2|N|4|O|6|7|8|W|9|@]|E|@]|F|$]]|$2|P|4|Q|6|K|8|X|9|@]|E|@]|F|$L|M]]]]

You just need to access to Gemfile with root access. Before <code>vi</code>:

command: 

<pre><code>sudo su -
</code></pre>

then:

<pre><code>vi ~/...
</code></pre>

I am trying to edit sources.list using vi editor but getting the following error while saving the file:

<pre><code>/etc/apt/sources.list" E212: Can't open file for writing
</code></pre>

/etc/apt/sources.list" E212: Can't open file for writing

 我正在尝试使用vi编辑器编辑sources.list，但在保存文件时遇到以下错误： /etc/apt/sources.list" E212: Can't open file for writing

问/etc/apt/Sourcees.list“E212:无法打开文件进行写入
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/etc/apt/Sourcees.list“E212:无法打开文件进行写入EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问/etc/apt/Sourcees.list“E212:无法打开文件进行写入
EN