Xref: utzoo unix-pc.general:6444 comp.sys.att:10840
Path: utzoo!utgpu!watserv1!watmath!uunet!shelby!apple!julius.cs.uiuc.edu!wuarchive!cs.utexas.edu!uwm.edu!uwvax!daffy!khan.cs.wisc.edu!sparkie
From: sparkie@khan.cs.wisc.edu (Mark Horn)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: comp.sys.3b1? (was Re: Monthly posting about Unix-PC networ
Message-ID: <1990Nov15.053246.10492@daffy.cs.wisc.edu>
Date: 15 Nov 90 05:32:46 GMT
References: <1990Nov3.045636.12735@cs.ucla.edu> <315@sphere.UUCP> <35841@cup.portal.com>
Sender: news@daffy.cs.wisc.edu (The News)
Reply-To: harier!sparkie@cs.wisc.edu
Distribution: na
Organization: University of Wisconsin -- Madison
Lines: 32

In article <35841@cup.portal.com> thad@cup.portal.com (Thad P Floryan) writes:

[ ... ]

>The above, coupled with John's other anecdotes, presents a VERY compelling
>case to initiate inquiry into forming a comp.sys.unix-pc.* hierarchy.  I
                                         ^^^^^^^^^^^^^^^^^^
[ ... ]

This is probably pre-mature, since we haven't even had a call for discussion,
yet, BUT! before that happens, whoever does organize the call for discussion,
should consider what we call the hierarchy.  I currently have access to 
the unix-pc.* groups and it's very nice.  It's also very ANNOYING when some
bozo who doesn't have a hint as to what an AT&T Unix PC is posts some dumb
question about running Xenix on his '386 box.  I would suggest that we call
the hierarchy comp.sys.3b1.* to avoid the confusion.

I just want to remind whomever might organize this venture, to have that 
be addressed in the call for discussion, and subsequent call for votes.

$.02
- sparkie
P.S.	Please Please Please do not reply to the account from which this
	was posted.  Instead, reply to one of the following:
		harier!sparkie@cs.wisc.edu
		sparkie@picard.cs.wisc.edu
	tnx.
-- 
 ___  ___  ___  ___  _  _  _  ___
/ __\| . \/ . \| . \| |/ /|_|| _ |
\___\| __/|   || _ /|   < | || _[  	sparkie@uhura.cs.wisc.edu 
\___/|_|  |_|_||_|\\|_|\_\|_||___|