Xref: utzoo comp.sys.3b1:351 comp.sys.att:11834
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!jethro!gakbox.Corp.Sun.COM!gak
From: gak@gakbox.Corp.Sun.COM (Richard Stueven)
Newsgroups: comp.sys.3b1,u3b.misc,comp.sys.att
Subject: Re: "comp.sys.3b2" and "comp.sources.3b2" anyone?
Message-ID: <3274@jethro.Corp.Sun.COM>
Date: 28 Jan 91 20:38:03 GMT
References: <1991Jan28.012133.13672@mtek.com> <1991Jan28.152827.8986@mthvax.cs.miami.edu>
Sender: news@jethro.Corp.Sun.COM
Reply-To: gak@gakbox.Corp.Sun.COM (Richard Stueven)
Followup-To: comp.sys.3b1
Distribution: na
Lines: 20

In article <1991Jan28.152827.8986@mthvax.cs.miami.edu>, aem@mthvax.cs.miami.edu (a.e.mossberg) writes:
>It seems that it would make more sense from the beginning to have a
>comp.sys.3b and comp.sources.3b [...]

The 3B1 and the 3B2 are wildly different machines.  In fact, no 3B
model resembles any other 3B model, except for the numerous variations
of the 3B2, and the 3B5/3B15 models.  (Are they still making any of
these anymore?  I've been out of it for a while...)

comp.sys.att lumps these models together nicely, as far as we 3b1-ites
are concerned.

have fun

gak

**    Richard Stueven           attmail!gak               gak@sun.com       **
**               Monday is a work day, Tuesday's much the same              **
**           Wednesday comes and goes away, Thursday's back again - Madness **
**                  Relax, don't worry, have a homebrew!                    **