Xref: utzoo comp.protocols.tcp-ip:5395 comp.unix.questions:10252 comp.unix.wizards:12520 news.admin:4014 news.sysadmin:1547 news.groups:6243
Path: utzoo!attcan!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!sm.unisys.com!oberon!bbn!bbn.com!cosell
From: cosell@bbn.com (Bernie Cosell)
Newsgroups: comp.protocols.tcp-ip,comp.unix.questions,comp.unix.wizards,news.admin,news.sysadmin,news.groups
Subject: Re: comp.security - LET'S DO IT!  CALL FOR VOTES
Message-ID: <32417@bbn.COM>
Date: 17 Nov 88 13:31:13 GMT
References: <6514@galbp.LBP.HARRIS.COM> <5493@saturn.ucsc.edu>
Sender: news@bbn.COM
Reply-To: cosell@BBN.COM (Bernie Cosell)
Distribution: na
Organization: Bolt Beranek and Newman Inc., Cambridge MA
Lines: 20

In article <5493@saturn.ucsc.edu> haynes@ucscc.UCSC.EDU (Jim Haynes) writes:
}There is a misc.security already - don't believe there has been anything
}in it for quite some time.


Just so -- the call for comp.security is pretty much misguided.  The problem
with misc.security is that the moderator moved machines and, apparently, has
not yet been able to reestablish connection to the news world, and so the
list has been moderator-blocked for something like eight months now.
There are, I'm quite sure, LOTS of postings backed up (I know for sure that
hobbit is holding onto two or three of mine).

Instead of rushing off to start a new newsgroup, why don't we just unmoderate
misc.security and see how it works moving all of the security stuff OUT of
the random newsgroups for a while.

   __
  /  )                              Bernie Cosell
 /--<  _  __  __   o _              BBN Sys & Tech, Cambridge, MA 02238
/___/_(<_/ (_/) )_(_(<_             cosell@bbn.com