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.)
- Re: translators, ext2 and files Olivier Galibert
- Re: translators, ext2 and files Marcus Brinkmann
- Re: translators, ext2 and files Niels M�ller
- Re: translators, ext2 and files Mark Kettenis
- Re: translators, ext2 and files Thomas Bushnell, BSG
- RE: translators, ext2 and files Brent Fulgham
- Re: translators, ext2 and files Gordon Matzigkeit
- Re: translators, ext2 and files Kalle Olavi Niemitalo
- Re: translators, ext2 and files Mark Kettenis
- Re: translators, ext2 and files Roland McGrath
- Re: translators, ext2 and files Kalle Olavi Niemitalo
- Re: translators, ext2 and files Kalle Olavi Niemitalo
- Re: translators, ext2 and files Thomas Bushnell, BSG
