> IMO, a more serious problem is that the current situation about GNU
> Mach is somewhat confusing. There are at least three variants, that
> is, gnumach-1.2 and later which have glue code with Linux's block and
> net drivers, gnumach-char which has glue code with Linux's char
> drivers additionally, and oskit-mach which doesn't have the glue code
> natively but uses OSKit instead. So it is difficult for contributors
I completely agree with Okuji on this point. It would be interesting
to contribute to *mach, but which mach is actually used for the Hurd and
who is maintaining it?
I'm currently hacking on some modifications and enhancements of Utah's Mach4
which are not yet ready for public. I'm testing those with the single lites
Server and I'd like to test them with the Hurd too. Knowing which Mach is to
be used for the Hurd would be of great help.
BTW, modifying or enhancing Mach in general or gnumach-* in particular,
by adding/enabling NORMA and other mechanisms, is a very deep and hairy
matter and I'm looking for other people with Mach experience to first
discuss the issues involved.
I'm currently digging through the Hurd libs and trying to figure out,
how Hurd's interface to Mach exactly looks like. Are the sources the
only documentation now, or am I missing something?
Thank you.
--
Farid Hajji -- Unix Systems and Network Administrator | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany | [EMAIL PROTECTED]
Fermat: ...I've found a remarkable proof for this: Let x,y @#$!@$!2@ NO CARRIER
