On Thu, 2 Dec 1999, Alexander Viro wrote:

>Don't bring the policy question into the kernel. If you want to kill the
>contents of inode - unlink() is _not_ a way to go. truncate() is.

What have unlink() or truncate() to do with this issue? The only system
call we are talking about is _link_(2).

Even supposing you can undo after 1 pico second the effect of the link(2),
for one pico second the system stayed in a state I don't like.

Andrea

Reply via email to