All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbradford@dial.pipex.com
To: B.Zolnierkiewicz@elka.pw.edu.pl (Bartlomiej Zolnierkiewicz)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ATAPI + cdwriter problem
Date: Tue, 9 Jul 2002 12:26:23 +0100 (BST)	[thread overview]
Message-ID: <200207091126.MAA01269@darkstar.example.net> (raw)
In-Reply-To: <Pine.SOL.4.30.0207091218350.6859-100000@mion.elka.pw.edu.pl> from "Bartlomiej Zolnierkiewicz" at Jul 09, 2002 12:22:59 PM

Hi,

> Dont punish performance and do not connect drives on the same channel
> if you can, the same goes for cd and cdrw (if cd -> cdrw of course)...

I don't think he's got much choice with all those devices :-)

> Also there was some problem recently with running 2 ATAPI devices on the
> same channel.

I generally prefer to use EIDE for hard disks, and SCSI for other peripherals, (and disks which are for, e.g. databases, but certainly not for boot disks, or general usage disks).

I tend to find 'silly' problems occuring with ATAPI devices, such as a motherboard/ATAPI CD-ROM drive combination that would never boot from the CD, because the BIOS reset the bus just before booting, and the CD-ROM would respond 'not ready'.  Generally SCSI peripherals tend to have a bit more thought put in to their design.

John.

  reply	other threads:[~2002-07-09 11:18 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 18:25 ATAPI + cdwriter problem James Stevenson
2002-07-08 21:44 ` James Stevenson
2002-07-08 21:59 ` jbradford
2002-07-08 22:00   ` James Stevenson
2002-07-08 18:09     ` Andy
2002-07-08 22:32       ` James Stevenson
2002-07-09  7:08     ` jbradford
2002-07-09  8:10       ` James Stevenson
2002-07-09  9:41         ` jbradford
2002-07-09 10:22           ` Bartlomiej Zolnierkiewicz
2002-07-09 11:26             ` jbradford [this message]
2002-07-09 19:54 ` Anssi Saari
2002-07-09 20:29   ` Alan Cox
2002-07-10 14:21     ` Anssi Saari
2002-07-10 15:00       ` Alan Cox
2002-07-11  2:30 ` James Stevenson
2002-07-11 11:47   ` Alan Cox
2002-07-11 13:52     ` James Stevenson
2002-07-11 17:22     ` Andre Hedrick
2002-07-11 21:38       ` Alan Cox
2002-07-11 21:44         ` Andre Hedrick
2002-07-11 22:53     ` James Stevenson
2002-07-11 22:57       ` Andre Hedrick
2002-07-11 23:31       ` Alan Cox
2002-07-12 18:55     ` Anssi Saari
2002-07-12 19:22       ` Alan Cox
2002-07-13  9:10       ` James Stevenson
2002-07-13 10:20         ` Anssi Saari
2002-07-13 11:11           ` James Stevenson
2002-07-11  2:36 ` James Stevenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200207091126.MAA01269@darkstar.example.net \
    --to=jbradford@dial.pipex.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.