Xref: utzoo comp.terminals:1071 comp.unix.wizards:14399 news.admin:4586 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-lcc!pyramid!csg From: csg@pyramid.pyramid.com (Carl S. Gutekunst) Newsgroups: comp.terminals,comp.unix.wizards,news.admin Subject: Re: 630MTG Discussions Keywords: 630MTG 5620 Message-ID: <56976@pyramid.pyramid.com> Date: 29 Jan 89 15:44:45 GMT References: <834@ttrde.UUCP> <9533@smoke.BRL.MIL> Followup-To: comp.terminals Organization: Pyramid Technology Corp., Mountain View, CA Lines: 21 >In article <834@ttrde.UUCP> stox@ttrde.UUCP (Kenneth P. Stox) writes: >[rmgroup comp.terminals.tty5620.] >So, let's get that 630 traffic over into comp.terminals.bitgraph, >and out of comp.unix.wizards. In article <9533@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) ) writes: >I think comp.terminals.bitgraph was supposed to be for the BBN >BitGraph terminal only. Probably there should be a > comp.terminals.bitmap >for generic Blit-like terminal discussions. Doug is correct, of course; but what both of you are forgetting is that comp.terminals.tty5620 and .bitgraph are both inet groups. Most sites out in UUCP land don't get either group. So neither is particularly useful. This may also account for why no one is using them. There has been a lot of AT&T 600-series terminal discussions in plain ol' comp.terminals. That group has very low traffic, so I see no reason not to use it.