Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!usc!chaph.usc.edu!phakt.usc.edu!tli
From: tli@phakt.usc.edu (Tony Li)
Newsgroups: news.groups
Subject: Re: Call for discussion: comp.sys.cisco
Keywords: dcom, brouters, repeaters, net analysis
Message-ID: <7422@chaph.usc.edu>
Date: 16 Jan 90 08:08:28 GMT
References: <3223@zehntel.UUCP>
Sender: news@chaph.usc.edu
Organization: University of Southern California, Los Angeles, CA
Lines: 16

In article <3223@zehntel.UUCP> deb@zehntel.UUCP (Deborah Heller) writes:
    	I vote for comp.dcom.cisco with something more like 
      Tom's idea of "comp.dcom.brouters." comp.dcom.hardware is another
      good one: for discussion of networking hardware problems/solutions and
      pointers to, perhaps, vendor specific groups such as comp.dcom.cisco.
      Hmmm... which will it be, comp.dcom.cisco or comp.sys.cisco (I vote for
      dcom.  Seems more appropriate).
    
I should point out that there is already a comp.sys.proteon, and that
while cisco's products are for data communications, they are also
computer systems in their own right.  Currently, computer system
newsgroups are not separated by the usage of the computer.
Tony Li - USC Computer Science Department
Internet: tli@usc.edu Uucp: usc!tli
Thus spake the master programmer: "A well written program is its own
heaven; a poorly-written program its own hell."