Newsgroup content

[John Plocher]

>But you don't want the vendor bashing in your support group.

  Speaking as one of those who started this newsgroup (c.u.microport) I'd
like to point out that one reason that the group was NOT created as a
"generic intel unix" group was to try and prevent the "flame wars" which
seem to start as soon as someone says "my X is better than your U".  Since
Microport was the common denominator *when the group was formed*, that name
was chosen (after several aborted attempts at other names: comp.unix.intel,
comp.unix.unix-at, comp.unix.286...)  The matter was "punted" into the future
with the note "call it .microport now, and whenever interest and events
warrent it, someone else will start comp.unix.whateverelse".

  The .microport group was created with the intention of it being a group
for and by people with unix (not xenix) on a 286 or 386 type machine.
Now that 3.2 is coming out, the lines between Xenix and Unix are getting
rather blurred (like my contacts are now ...) and there will be some
crossover.  So be it.

  Lets remember, though, that Xenix people read .xenix, Microport people
read .microport, and those who are interested in both read both.  Those
that don't read both do so because they don't care about the other group.
Moral:  Please DO NOT CROSSPOST between .microport and .xenix.

  Also remember that FLAMES belong in alt.flames, not in .xenix or .microport.
If your article sounds like:

   "I bought ____ and it sucks for these documented reasons"

it may be worthwile to post; on the other hand if it sounds like:

   "____ sucks, buy real ____ because I scream the loudest"   -or-
   "_____ chips are inferior to ____ chips"   -or-
   "soandso is a jerk"

then please don't bother the net with your drivel.

  -John Plocher
Speaking as myself