MI400 is NOT alt.2600

[Don <dr2@xxxxxxxxxxxx>]

Lo, et al...

MI400 is not a hackers list.  That's what alt.2600 is for.  Neither is
MI400 intended to be a CERT function...but if it becomes an alert medium,
that's fine.

MI400 is for the open and free exchange of information related to MI and
system internals.  alt.2600 tends toward the malicious exchange
of....although there are some ligitimate workarounds on it.

When I see a fellow system person that tells me "hey, I think I have a
problem.  Please verify and help me fix it." Or, "hey, I've got a
ligitimate problem of major gravity that my primary vendor refuses to
address..." then yeah, I don't have a problem with seeing it.  I think
that's what we saw this week....

Lo, I can assure you that I didn't manufacture the events of the last
several days for PR purposes...nor will I allow that to occur on this
list.  It's not what we're here for.

Lo, what we saw this week were people asking for a solution.  And they got
it.  It was a situation where following the channels failed and something
needed to be done.  

Helping our fellow users find solutions is one big reason why this
listserver exists.  Problems will vary in size, complexity and impact.

case closed.

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---