[news.groups] Name disappointments for comp.periphs.scsi

mehl@cs.iastate.edu (Mark M Mehl) (02/16/90)

In news.groups emv@math.lsa.umich.edu (Edward Vielmetti) writes:
>I put forth the idea of comp.periphs.scsi about a month ago on
>comp.periphs and a few other groups.  Reaction to the idea was almost
>entirely positive, reaction to the name was pretty good.  A question
>arose to whether it wouldn't be better to have a
>comp.bus.<name-your-bus>, not a bad idea for future consideration.
 ^^^^^^^^                                     ^^^^^^ ^^^^^^^^^^^^^
I'm very disappointed you simply didn't call it comp.bus so we could
discuss all bussing issues in one big group.  If traffic warrents it,
we can split the group latter to comp.bus.scsi and comp.bus.

I would very much like to have a group that discusses bussing issues,
but I'm going to have to vote NO on this one simply because I think
the discussion forum should include ESDI, IPI, and IEEE-488 busses
as well.  Sorry guys.

BTW, where does one post an IEEE-488 bus quesiton?
--
 /\ Mark M Mehl, alias Superticker (Supertickler to some)
<><> Internet: mehl@atanasoff.cs.IAstate.edu
 \/ UUCP: {{mailrus,umix}!sharkey,hplabs!hp-lsd,uunet}!atanasoff!mehl
Disclaimer: You got to be kidding; who would want to claim anything I said?

emv@math.lsa.umich.edu (Edward Vielmetti) (02/17/90)

In article <636@dino.cs.iastate.edu> mehl@cs.iastate.edu (Mark M Mehl) writes:

   In news.groups emv@math.lsa.umich.edu (Edward Vielmetti) writes:
   >I put forth the idea of comp.periphs.scsi about a month ago on
   >comp.periphs and a few other groups.  Reaction to the idea was almost
   >entirely positive, reaction to the name was pretty good.  A question
   >arose to whether it wouldn't be better to have a
   >comp.bus.<name-your-bus>, not a bad idea for future consideration.
    ^^^^^^^^                                     ^^^^^^ ^^^^^^^^^^^^^
   I'm very disappointed you simply didn't call it comp.bus so we could
   discuss all bussing issues in one big group.  If traffic warrents it,
   we can split the group latter to comp.bus.scsi and comp.bus.

I'm interested in it more from the peripherals standpoint -- which
scsi drives will plug in and work with which computer systems,
collection formatting information for drives not directly supported by
the manufacturer, drivers for more esoteric scsi devices.  Discussion
of scsi bus issues per se (like what should be in scsi-3) would be
welcomed as well.  I'm not a bus designer, just a user, hence my bias
here.

One of my goals for this group is to accelerate the process of
evaluating new SCSI hardware as it appears on the market, forming
a clearinghouse for information on what works well with what,
across different computer platforms. 

   I would very much like to have a group that discusses bussing issues,
   but I'm going to have to vote NO on this one simply because I think
   the discussion forum should include ESDI, IPI, and IEEE-488 busses
   as well.  Sorry guys.

   BTW, where does one post an IEEE-488 bus quesiton?

I'd drop it in comp.periphs with a cross-posting to comp.sys.<system>
or comp.sys.<system>.hardware if that exists.  I believe that
comp.realtime has had some related traffic.  I don't think that any
reasonable discussion in the group would be discouraged -- certainly
news about ESDI, especially in comparison with SCSI, would be fine.
Wait and see when it's created....

--Ed

-- 
Edward Vielmetti, U of Michigan math dept.
comp.periphs.scsi: mail your votes to emv@math.lsa.umich.edu
	Subject: YES vote on comp.periphs.scsi
or	Subject: NO vote on comp.periphs.scsi