On Mon, 9 Dec 1996 16:12:43 -0500 (EST), Tom Rini <trini@ntplx.net> wrote:
> Not that i know of, but i've talked to nick stephens about this before,
> and he said that porting it over would have been easier then linux (still
> a whole lota fun though)

BSD OS servers are much easier to build due to the amount of example code  
left over from the CMU BSD4.3 over Mach2/3 mk's.

Actually, it doesn't make much of a difference with what you start, or at  
least to me it doesn't.  Writing Mach OS servers is always the same process.   
Just a little more evolved with BSD and monolithic Linux.

For starters, look at simple servers like Poe and go from there.

> >2.	Are the hardware-dependant sections of NetBSD's code essentially
> >all in one section, or are there a number of #ifdefs scattered throughout
> >the code?
>
> You'd need to make its own arch of course,  but some of it should work
> form the arch/mac68k, and other bits from arch/powerpc (pci only).

I second that as a conservative but reasonable assumption.

> Well, you don't need a second booting partition to use the multi-server
> part of mach.  You can run it off a zip untill it out grow that.  Just
> need to find an fs that both linux and netbsd can read.  You may also
> wanto look though the mklinux src, and join
> mklinux-developer-system@mklinux.apple.com.  I remeber someone asking
> about doing something like this to FreeBSD before, and I took a quick stab
> at Lites (don't know much C, so it died fast)

Hold on! ;-).. don't whether you use multi-server or single server (Mach-US  
and Mach-UX respectively) do not matter for the booting portion at all.

I think you mean single server anyway ;-).

Use a Minix filesystem (gasp), since it is so darn easy to implement and  
comes with a wide open license agreement.

Regards,
Chris

--
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/