Xref: utzoo comp.sys.3b1:20 comp.sys.att:11631
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uunet!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ames!dftsrv!mimsy!nmrdc1!rdc30med
From: rdc30med@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.sys.3b1,u3b.misc,comp.sys.att
Subject: Re: "comp.sys.3b2" and "comp.sources.3b2" anyone?
Keywords: time to continue the process?
Message-ID: <1991Jan28.180448.6953@nmrdc1.nmrdc.nnmc.navy.mil>
Date: 28 Jan 91 18:04:48 GMT
References: <1991Jan28.012133.13672@mtek.com>
Distribution: na
Organization: Naval Medical Research & Development Command
Lines: 13

From what I've seen of the traffic in comp.sys.att, it has been either 3b1 or
3b2 traffic all along.  Now that the unix-pc traffic will (largely) be going
into the 3b1 groups, that would seem to leave 3b2 traffic the sole occupant
of comp.sys.att.  Perhaps a rename to comp.sys.3b2 and the addition of 
comp.sources.3b2 is in order.  How much 3b2 specific source code is actually
out there?  With the exception of ANSI C code and heavily BSDish code, I've had
only minor problems with code from the existing source groups that claims to be
usable on SysV machines so we may not need a 3b2 specifc source group.
-- 
Mike Dobson, Sys Admin for      | Internet: rdc30med@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30med
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719@mcimail.com