Xref: utzoo comp.arch:22442 comp.unix.ultrix:7104
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: comp.arch,comp.unix.ultrix
Subject: Re: ACE, buses, and the future of ultrix
Message-ID: <3405@crdos1.crd.ge.COM>
Date: 6 May 91 14:04:35 GMT
References: <1991Apr30.191117.4373@vax5.cit.cornell.edu> <32459@usc> <281f3e99.2f35@petunia.CalPoly.EDU> <1991May2.224316.17903@ico.isc.com> <816@cadlab.sublink.ORG>
Reply-To: davidsen@crdos1.crd.ge.com (bill davidsen)
Followup-To: comp.arch
Organization: GE Corp R&D Center, Schenectady NY
Lines: 17

In article <816@cadlab.sublink.ORG> martelli@cadlab.sublink.ORG (Alex Martelli) writes:

| I share your perplexity; and I shake my head at the rumor that Dec is going
| to hand over Ultrix-cum-OSF/1, lock, stock, and barrel, to SCO, to become
| the base of the ACEy ODT, which Dec will in turn adopt, dropping Ultrix...
| I hope this last rumor is wildly unfounded???  We're evaluating a centralized
| NFS server, and DS5500 was looking pretty good, but I would be VERY hesitant
| to place in such a crucial hub role in our LAN a box from a company who has
| just decided its system software is better manufactured by somebody else!

  I think the most likely course is that SCO will start from Mach and go
from there. And why shouldn't DEC have someone make their software, when
they are having someone (MIPS) make their CPU?
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
        "Most of the VAX instructions are in microcode,
         but halt and no-op are in hardware for efficiency"