Many bugs in link2symlink extension

[aristarh2704]

There are many bugs. For example,

$ mkdir a b
$ touch a/a
$ ln a/a b/b
$ rm a/a
$ rm -r a                                   
rm: cannot remove 'a/.l2s.a0001': Operation not permitted

Also a bug occurs if the target file exists.

[michalbednarski]

It's normal that if you remove link target that link becomes broken. When proot creates first link2symlink to file it puts two files with name starting with ".l2s." in directory where original file was (and which was deleted in your example). I see two possible solutions for that: * Hiding ".l2s." files (so `rm -rf` won't be able to remove folder with them), however I don't really like that solution as it means that you won't be able to delete folder which had hardlinked files and renaming folder would still break links. * Allowing user to specify folder which will contain all "l2s" files (this would require user to specify folder in order to get fix (and i wouldn't want to specify default one as it would mean leaving leftovers after user deletes whole chroot))

[aristarh2704]

I think using a separate folder for all l2s files is the best solution, for example, /.l2s/ in guest root
It's need make this folder inaccessible for reading and writing
But the second bug is due to the fact that l2s does not check the existence of the target file