In article <[🔎] 87zp1umrtq.fsf@hedgehog.zoo> you write: >How does the following sound: > >NFS does not allow passive translators. They are not stored; the call >fails. If the user wants to set up passive translators, e can use >shadowfs to slap a writable filesystem over top. If the user is using >a diskless machine, the startup scripts can create the correct passive >translatos on a RAM filesystem, say from a tar file. That would mean hurd cannot be used on diskless systems. >Alternatively, when a passive translator is "saved", what is actually >stored is simply a command line, no? Perhaps one could simply store >that in some file on the NFS server (possibly even some automagically >named file). One could possibly even arrange >it so that a non-Hurd-extended server could cope with these files. What I would like is if all of the above could be implemented in the client without requiring any changes to the server... (Actually I think that is what you have suggested). -- Brian May <bam@snoopy.apana.org.au>
Attachment:
pgpb4IhuBaVKK.pgp
Description: PGP signature