Greg A. Woods writes:

>But it should, not, indeed must not, else a fundamental feature of how
>unix I/O works would be trashed all to hell.

Of course it is and I only gave this example to show how nonsense
an "funlink()" call would be -- because the only valid behaviour
in the current framework (clearing of inode / invalidating all fds)
would be totally impractical.

Now can we stop this thing?  Or should I also propose some b*llsh!t
system call and have a hundred-mails long thread debate its uselessness?

-- 
  Matthias Buelow;  mkb@{mukappabeta.de,informatik.uni-wuerzburg.de}