Path: utzoo!utgpu!jarvis.csri.toronto.edu!torsqnt!tmsoft!robohack!woods
From: woods@robohack.UUCP (Greg A. Woods)
Newsgroups: comp.sys.att
Subject: comp.sys.att/unix-pc.* (was Re: Undocumented "features and bug fixes" found in FIXDISK2.0 (3.51m))
Summary: cross-posting
Keywords: UNIXpc 3.51m 3.5
Message-ID: <1990Feb1.145517.29568@robohack.UUCP>
Date: 1 Feb 90 14:55:17 GMT
References: <1072@icus.islp.ny.us> <364@heurikon.UUCP>
Followup-To: alt.flame
Organization: R. H. Lathwell Associates:  Elegant Communications, Inc.
Lines: 25

As always, when something exciting happens in the Unix-PC world, I
have to carefully wade through comp.sys.att, because the traffic gets
heavy.

Now this wouldn't be so bad if there wasn't a unix-pc.* heirarchy.

You see, I'm interested in unix-pc's, but not as interested as I am in
386's and 3B2's.  I read comp.sys.att all the time, but unix-pc.* only
25% of the time.  I don't want to have a kill file for comp.sys.att.

I don't want to start the old war again either.

What I do want to do is point out that the article I'm following up
came from a USA site, and was NOT cross-posted to unix-pc.general.

I should also say I receive the u3b groups too, and I see a lot of 3b2
stuff cross-posted between u3b and comp.sys.att too.  I'd like to
suggest that everyone evaluate the possible generality of their
articles and only cross-post when the article is not specific to one
particular type of system.
-- 
						Greg A. Woods

woods@{robohack,gate,tmsoft,ontmoh,utgpu,gpu.utcs.Toronto.EDU,utorgpu.BITNET}
+1 416 443-1734 [h]   +1 416 595-5425 [w]   VE3-TCP   Toronto, Ontario; CANADA