linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Gammans <roger@computer-surgery.co.uk>
To: mikpe@csd.uu.se
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ATAPI cdrecord issue 2.5.67
Date: Sun, 20 Apr 2003 00:22:17 +0100	[thread overview]
Message-ID: <20030419232217.GA6873@computer-surgery.co.uk> (raw)
In-Reply-To: <16022.40189.672337.427776@gargle.gargle.HOWL>

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Fri, Apr 11, 2003 at 12:46:21PM +0200, mikpe@csd.uu.se wrote:
> Alan Cox writes:
>  > On Thu, 2003-04-10 at 20:53, H. Peter Anvin wrote:
>  > > I think ide-scsi needs to be supported for some time going forward.
>  > > After all, cdrecord, cdrdao, dvdrecord aren't going to be the only
>  > > applications.
>  > 
>  > And far longer than that. People seem to be testing and demoing 
> [snip]
> 
> ATAPI tape drives will need ide-scsi too, unless ide-tape somehow
> got repaired lately. And some people already use ide-scsi+st in
> 2.4 since ide-tape doesn't always work reliably.

Whan I last looked at the ide-tape driver  , which was
back in 2.2, it looked like the big problem was actually 
in it error handling , rather than anywhere else.

I don't think it has been changed significantly it that regard
since.

IIRC , the behaviour which appeared to be caueing me a problem
was that some slow driver would be busy long for ide-tape to
get bored. It also didn;t like getting error codes which weren't
spelled out it the quik spec. The common travan mechanism I
get lots of here, spits out quite a few of those. (As well
as failing one of st's enquiry cmds).

TTFN
-- 
Roger. 	                        Home| http://www.sandman.uklinux.net/
Master of Peng Shui.      (Ancient oriental art of Penguin Arranging)
   GPG Key FPR: CFF1 F383 F854 4E6A 918D  5CFF A90D E73B 88DE 0B3E
Work|Independent Systems Consultant | http://www.firstdatabase.co.uk/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2003-04-19 23:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 14:01 ATAPI cdrecord issue 2.5.67 Grzegorz Jaskiewicz
2003-04-10 14:16 ` Grzegorz Jaskiewicz
2003-04-10 14:53   ` Felipe Alfaro Solana
2003-04-10 14:43     ` Grzegorz Jaskiewicz
2003-04-10 19:34     ` Aaron Lehmann
2003-04-10 19:53       ` H. Peter Anvin
2003-04-10 19:44         ` Alan Cox
2003-04-11 10:46           ` mikpe
2003-04-11 11:29             ` John Bradford
2003-04-19 23:22             ` Roger Gammans [this message]
2003-04-10 14:52 ` Felipe Alfaro Solana
     [not found] <20030410143018$100e@gated-at.bofh.it>
     [not found] ` <20030410144011$6cc1@gated-at.bofh.it>
     [not found]   ` <20030410150015$0682@gated-at.bofh.it>
     [not found]     ` <20030410194019$3cf5@gated-at.bofh.it>
     [not found]       ` <20030410200011$156b@gated-at.bofh.it>
     [not found]         ` <20030410205020$3813@gated-at.bofh.it>
2003-04-10 21:36           ` Pascal Schmidt

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=20030419232217.GA6873@computer-surgery.co.uk \
    --to=roger@computer-surgery.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).