Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!gatech!uflorida!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: System V Release 4.0 Developer Conferences
Message-ID: <8615@smoke.ARPA>
Date: 3 Oct 88 07:50:48 GMT
References: <167@hsi86.hsi.UUCP> <1988Sep22.173745.14647@utzoo.uucp> <5634@vdsvax.steinmetz.ge.com> <1649@ficc.uu.net>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <1649@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>What if you want to stick Blit terminals on it? Does that count?

I assume you mean the whole Blit ("xt" protocol) family, which includes
the 5620, 615, 625, 630, and PC/Layers.

It shouldn't be hard to port the existing stuff to SVR4, since all it
really needs is either kernel support for multiplexing (easy enough
with STREAMS) or a user-mode multiplexer, which is available from
several sources including AT&T-formerly-Teletype.  Pre-STREAMS "xt"
support used a special pseudo-device driver (that also handled details
of the "xt" protocol), but BSD-based systems usually have used ptys
with user-mode protocol handling and multiplexing.  If SVR4 doesn't
have enough hooks for at least one of these approaches to work, it
won't be worth using anyway.