Return to BSD News archive
Xref: sserve comp.unix.bsd:12400 comp.sys.dec:14776 Newsgroups: comp.unix.bsd,comp.sys.dec Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!headwall.Stanford.EDU!CSD-NewsHost.Stanford.EDU!CS.Stanford.EDU!jonathan From: jonathan@CS.Stanford.EDU (Jonathan Stone) Subject: Re: ?wuarchive 4.3bsd-reno code for VAX Message-ID: <1993Aug12.220025.6133@CSD-NewsHost.Stanford.EDU> Sender: news@CSD-NewsHost.Stanford.EDU Organization: Computer Science Department, Stanford University. References: <2495tfINNrul@cbl.umd.edu> <7009223@zl2tnm.gen.nz> Date: Thu, 12 Aug 1993 22:00:25 GMT Lines: 16 The unix ``bigot'' in question recalls that the original Uvax II support for 4.3bsd was contributed by (I think) mt.Xinu, and was in the archives of postings to comp.bugs.4bsd at (I think) ucbarpa.berkeley.edu. Amongst other things (mostly support for the KA650 cache, and emulation code for the missing string instructions that acutally *worked*), it included a Uvax booblock and a tk50 bootstrap, which the sufficently perverse could probably build and put onto tk50 media. (One really doesn't want to overwrite one's bootblocks until one is *sure* the new BSD kernel is going to boot.) Having a functional Ultrix system with TK50 media would be a *big* help there; though there's an existence proof that it's not strictly necessary. A replacement for the missing memory management code is probably harder; though in a previous post, Paul Vixie threatened to have some working about now...