Mark Kettenis <[EMAIL PROTECTED]> writes:

> How about having a magic translator /dev/underlying to represent the
> underlying node of a translator (similar to /dev/tty for the
> controlling terminal)?

How would libc know about the underlying port?  Remember, the
same process may be translating multiple nodes....

Maybe I've said this earlier: I'd also like a syntax for nesting
translators on the command line.  Something like "/hurd/shadowfs
--nest /hurd/ext2fs /dev/foo".  (Shadowfs allows multiple
directory arguments so there should also be an
--end-nest... perhaps it wasn't such a good idea after all.)

Reply via email to