Xref: utzoo unix-pc.general:6417 comp.sys.att:10806
Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!lobster!limbic!gil
From: gil@limbic.ssdl.com (Gil Kloepfer Jr.)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: comp.sys.3b1? (was Re: Monthly posting about Unix-PC networ
Summary: I say comp.sys.3b1
Message-ID: <733@limbic.ssdl.com>
Date: 12 Nov 90 06:49:03 GMT
References: <1990Nov3.045636.12735@cs.ucla.edu> <315@sphere.UUCP> <35841@cup.portal.com>
Organization: Southwest Systems Development Labs, Houston, TX
Lines: 17

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.

As with the original thread of this discussion, I would be more inclined
to make it comp.sys.3b1.*, rather than comp.sys.unix-pc.  Already, we have
had several instances of people who have mistakenly posted to this hierarchy
thinking it was for PCs running UNIX.

I was mildly upset at the thought of the unix-pc hierarchy being so loosely
held-together, as was suggested by the article that Thad followed-up to.
Although making this hierarchy part of comp.sys would solve some problems,
I wonder how much of the comp hierarchy has been censored out before
being fed to downstream feeds.
-- 
Gil Kloepfer, Jr.              gil@limbic.ssdl.com   ...!ames!limbic!gil 
Southwest Systems Development Labs (Div of ICUS)   Houston, Texas