🚀 go-pugleaf

In article <62468@pyramid.pyramid.com> csg@pyramid.pyramid.com (Carl S. Gutekunst) writes:

(You obviously have source.  I don't.)

>What Dynix needs is to be brought up to date; 

This isn't unique to the SysV world.  I could mention Van Jacobson
code, (which is might not be fair), but surely async io, sigio, and a
host of other 4.3 socket features are long overdue.

>SVR2 was old
>news three years ago. Perhaps even smarter would be a brand new symmetric port
>of SVR3, and forget Berkeley.

Uh, this isn't really quite possible.  There are some of us out here
who are really using symmetric code and applications that SysV hasn't
even begun to think about.

First and foremost, (remember I'm not a source code owner), if at&t
has a working version of streams, why are so many vendors marketting
SysV w/sockets only?

>What is humorous -- to me, anyway -- is that Dynix has the internal implemen-
>tation of a merged system, but the external appearance of a Pyramid-style dual
>port. [...] Given all the reasons why *not* to do a dual port, this
>seems like more of a marketing decision than an R&D one.

I don't agree.  Must simpler to support as is.  And personally, I get
kind of pissed at the Sun only features of SunOS.  ie, I'd rather
system V was in SysV universe and I can import the things I
like/want/need which is precisely what sequent currently provides.

>In article <455@sendai.ann-arbor.mi.us> rich@sendai.UUCP (K. Richard Magill) writes:
>>What news?  Oxtrap has been running news for almost 2 years now.
>Wrong concept. There is a System V utility called news(1), which has nothing
>at all to do with Netnews or Usenet.

Ok, ok.  too many things called gnus or gnews or news or nEws or ...
in the world.
-- 
rich.