Messages in this thread | | | Date | Fri, 23 Dec 2011 10:10:53 -0500 | From | Wakko Warner <> | Subject | Re: Intercepting system calls |
| |
Jiri Kosina wrote: > On Thu, 22 Dec 2011, Wakko Warner wrote: > > > > Oh. I will not do it then, could you suggest me something so that I > > > could prevent unlink on some file say using kernel support. I want to > > > save file on unlink how could I do that without kernel support, or how > > > could I do that using a kernel module. > > > > I wrote a library that can be loaded in userspace that does this. It's not > > very polished, but it works for me. I use it for rsync when I want files > > "deleted" but not from the filesystem. It creates a .deleted directory in > > the $PWD. > > I don't see a way how library could cover any arbitrary userspace process > issuing unlink() (consider statically linked binaries, for starters).
It cannot. I already understand that static binaries cannot be trapped like this.
-- Microsoft has beaten Volkswagen's world record. Volkswagen only created 22 million bugs.
| |