Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!news-feed-1.peachnet.edu!paperboy.wellfleet.com!noc.near.net!news.delphi.com!usenet From: John Dyson <dysonj@delphi.com> Newsgroups: comp.unix.bsd Subject: Re: BSD for the Sun386i Date: Sun, 8 May 94 17:24:00 -0500 Organization: Delphi (info@delphi.com email, 800-695-4005 voice) Lines: 33 Message-ID: <ho4MM7o.dysonj@delphi.com> References: <2qcljn$gqt@norm.eng.gtefsd.com> <michaelv.768258619@ponderous.cc.iastate.edu> NNTP-Posting-Host: bos1a.delphi.com X-To: Michael L. VanLoon <michaelv@iastate.edu> Michael L. VanLoon <michaelv@iastate.edu> writes: >>I would like to port NetBSD or FreeBSD to the Sun386i. Any >>one have any suggestions or advice? > >FreeBSD is not architecture-neutral -- it's for i386 only. NetBSD is >layed out in such a way as to lend itself to porting to any >architecture. Ahww, come on now... The machine independant portions of FreeBSD are just as architecture neutral as NetBSD. There have been some I386 specific enhancements (many of which are applicable to other machines.) We have been making improvements to the base architecture *before* doing ports and getting all balled up trying to track them all. We are about ready and give us just alittle time. When we made some mods, say to the VM system -- there are some minor machine dependencies, but we can either ifdef them out or move say, portions of vm_glue to where they should be. The only gross machine dependency that I know of in the VM code right now is that some of the enhancements depend on a real reference bit. That can be removed (very quickly.) Anyone that wants to do a port to another machine or architecture -- get involved with is on FreeBSD -- in about 3-4 weeks I think that our code base will be fully ready with its high performance etc... FreeBSD IS NOT FOR I386's ONLY!!!! It is correct to say though, that the only current port is for the 386/486/Pentium. This is not to start a flame war -- but incorrect statements about other people's work should be avoided... John dyson@implode.root.com