Re: Future use of OSKit facilities in gnumach

[John Tobey]

> Nice.  I hope you will make your code available even if unfinished so
> people can see (and maybe help), sooner rather than later.  The hurd
> sourceforge project might be a good place for this right now.  If it is
> kept reasonably cleanly isolated, we would love to incorporate this into
> GNU Mach when it's in shape, and have 2.0 include the user-mode-Mach build
> option.

Great.  My sourceforge ID is jtobey, feel free to suggest directory
placement or module naming (I have to familiarize myself with what's
already on the Hurd Sourceforge project).  Currently I have everything
in a /hacks/gnumach/otop/linux/i386 as a psychological aid to avoid
premature portability.

> > Oh, and NCPUS will be > 1 by default thanks to linuxthreads.
> 
> I would certainly not recommend that you start that way.  Even hardware
> aside, the MP code is sufficiently bit-rotted that you are probably asking
> for trouble.  For any port, whether to hardware or software, it just plain
> makes good horse sense to get the NCPUS==1 build working and stable before
> trying MP.

Anything you say.  I would like to build thread-safety into any new
code, though, and I do not intend to support a separate,
single-threaded configuration (for what? speed??).

Btw, I am looking more closely at the OSKit Unix stuff and becoming
more optimistic about it.  Guess I'll have to roll my own mmap()
though, or fish it out of /usr/lib/libc.a .  Theirs just returns
ENOSYS.

-- 
John Tobey <jtobey@john-edwin-tobey.org>
\____^-^
/\  /\