On 17/05/03 13:26, Gary Johnson wrote:
On 2017-05-03, Christian Brabandt wrote:
Hi Gary!
On Mi, 03 Mai 2017, Gary Johnson wrote:
> > > If that was true, I would expect the inode number of the file to be
> > > different after Vim had edited it, but that is not what I observe.
> > > The inode number is unchanged.
> > >
> > > I created a file with only read permissions and successfully edited
> > > it with Vim. I repeated the experiment in a directory with only
> > > read and execute permissions and was able to edit that file as well.
> >
> > Did you check the backupcopy option?
>
> 'backupcopy' is set to "yes".
Okay, so apparently it is not so easy (as usual).
I made a little test:
[...]
So it is clear, by removing a file with a lower inode number before
trying to write file2, that inode number of the deleted file file1 is
re-used when re-creating file2.
So it looks like ext3/ext4 always uses the first free inode number for a
directory it can find and therefore, when deleting a file and
re-creating the file, it is possible that the same inode is re-used.
Today I learned something new ;)
So did I! Nice work. Thank you.
Thanks a lot :)
Niels
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
