Kalle Olavi Niemitalo <[EMAIL PROTECTED]> writes: > > Heh. My best answer is that NFS will only support passive translators > > by extending the protocol, and then it will only do anything if the > > server supports it.
> Assume this was some Hurd-specific protocol. Where would passive > translators then be saved? The server stores it on the server, as a translator, with nothing special done. > When the client sets the passive translator of a file to > "/hurd/ext2fs /dev/hd0s2", the server must not attempt to > activate the translator when the file is accessed. Quite right. If you look at the implementation of the NFS lookup call in the Hurd nfsd (hurd/nfsd/ops.c:op_lookup) you will see that the server uses O_NOTRANS to prevent such activation. Thomas
