On Tue, Mar 04, 2003 at 02:34:47PM -0500, Roland McGrath wrote:
> > No, that is the FUN part. I've got that working rather well, if I may
> > say so (rewritten since my first try). The hard part is putting it
> > all together.
>
> Nice. I hope you will make your code available even if unfinishe
> 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 M
> No, that is the FUN part. I've got that working rather well, if I may
> say so (rewritten since my first try). The hard part is putting it
> all together.
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
> This stuff is really all using the "minimal" code. This is just stuff for
> booting and such, and things like _exit to reboot and printf for the
> boot-time output on the minimal console.
> The use now is pretty minimal and if anything there will be less use rather
> than more.
Thanks Roland,
> I see that GNU Mach links with a few OSKit libraries including
> -loskit_c. However, it seems to require only a few functions from
> that library, and most (all?) of its OSKit dependencies exist for the
> device driver framework ("osenv").
That and booting, and for the unfinished SMP support, t
I see that GNU Mach links with a few OSKit libraries including
-loskit_c. However, it seems to require only a few functions from
that library, and most (all?) of its OSKit dependencies exist for the
device driver framework ("osenv").
Is there any plan to integrate the Mach parts more closely with
