On Mon, 9 Dec 1996 13:12:59 -0800 (PST), wrstuden@loki.stanford.edu (Bill  
Studenmund) wrote:
> Also, I don't know how the microkernel advertises
> what devices it has (since if you do this right, it could run on the
> microkernel on a PPC, ix86, and whatever else the microkernel supports).

The generic answer:  It is up to you how you let the OS server use use its  
message passing to discover the microkernels abilities.  There are numerous  
ways, including running your own seperate configuration database server and  
talking to its ports.

>
> I think all you'd have to do is have the tool chain make a binary
> (elf?) of the type the microkernel expects.

Most Mach mk's expect Mach-O.   If I remember that correctly, it is a  
derivative of a.out.  But then again, it depends on what Mach mk with what OS  
server combo you chose.  You can launch a simple OS server like Poe and make  
it launch your OS server until you figure out how to do it directly.  A lot of  
Mach ports I have seen bootstrap themselves that way...

> It might be that you need to make a "ppcmach" port. Among other things
> because I hope we eventually get a "direct" port too. But if things are
> done right, user-land binaries won't be able to tell the difference. :-)

No, you don't need to create a separate platform specific Mach port within  
NetBSD.  You need to port the mk and a generic OS server on top.  The rest is  
almost automagic (except for the driver portion).

> The part which would scare me the most (reflecting my lack of experience)
> would be configuring the tool chain. If you can do that, you're set; you
> can compile from anything.

Descriptions of all that can be found at CMU.  Including a toolbox.  Gee,  
this is almost like a MUD ;-)

--
Christian Kuhtz          kuhtz@ix.netcom.com - hm, ckuhtz@paranet.com - wk
Network/UNIX Specialist      BOYCOTT INTERNET SPAM http://www.vix.com/spam
Paranet, Inc.                                      http://www.paranet.com/