Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!maverick.ksu.ksu.edu!hoss!nolan From: nolan@iti.org (Mike Nolan) Newsgroups: comp.sys.ncr Subject: Re: SVR4 Keywords: Local SE, never Message-ID: Date: 10 Dec 90 18:08:46 GMT References: <1990Dec9.150131.36596@eagle.wesleyan.edu> <4172@vela.acs.oakland.edu> <18360@letni.UUCP> Sender: news@hoss.unl.edu (Network News Administer) Organization: University of Nebraska - Lincoln Lines: 22 doug@letni.UUCP (Doug Davis) writes: >Perhaps I could shed a little light on this, as a developer of >NCR tower clones (yes, not the peecee ones) we committed to SVR4 >back in December of last year. The M68k release (from at&t) was expected >sometime in October. To this date we haven't seen it, nor does it >look like it will be any time real soon. Giving that the '86 code >has been available for a while it is quite likely that NCR is only >talking about SVR4 for '86 machines, since that code is in a known state. According to the 'usually reliable' inside sources, NCR had already succeeded in porting enough of SVR4 to the 68k machines that they had working prototypes of their recently announced Cooperation software package running last spring. It is my understanding that the decision NOT to release SVR4 on 68k machines is a marketing decision, not an engineering one. (By contrast, the decision not to release the 88k systems was based on engineering results. According to at least one source, NCR built about 50 of the 88k machines, but the 80486 machines ran rings around them in performance comparisons.) Michael Nolan UUCP: tssi!nolan (sometimes sparky!dsndata!tssi!nolan is more successful) Internet: nolan@helios.unl.edu