Ok, another suggestion for the "9P Dubious Protocol Enhancement Committee":
> Tclunk can't fail (and close(2) doesn't return -1 on real fds). I agree that it doesn't make sense for Tclunk to fail in the "no, you must continue making I/O requests against this object" sense. But any time there's asynchrony in the system Tclunk may end up being the last time an error related to a previous operation can be reported. There isn't a "Tensure-all-bits-are-stable", right? I believe the Linux guys used to believe that VOP_CLOSE "couldn't return errors" and defined the operation as void, and I don't think they still do that. Dave Eckhardt
