> What parts of OSKit is GNU Mach going to use? I'm assuming that it is not > going to use all of it...
You should build the oskit and oskit-mach for x86 (even if you're not going to use it) so you can see for yourself. > So far, I've already got oskit/dev, oskit/oskit/alpha, and oskit/threads > ported (these modules compile, but have not been tested)... Please subscribe to [EMAIL PROTECTED] and post there immediately about your Alpha work. I think some group somewhere already started some Alpha oskit work that was never incorporated, and it would be a shame if you duplicated work that's already been done. I am all for the approach of porting the oskit, if you are up for doing it. That would be fabulous! In that case, the thing to do is to get the oskit port basically working first before worrying about Mach at all. So, take the discussion to oskit-users, get some oskit example kernels working, and then come back here to start talking about oskit-mach. Get the hello world examples, and some examples that use the disk and net drivers (there are several simple ones) working, and a usable minimal console (for oskit getchar and printf). That's the oskit code you need to have working to get started on Mach. (Well actually you could get started on Mach without the disk and net devices working yet, but you could only get Mach as far as booting and setting up a task before you would have to go back and make drivers work.) _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
