From: Jens Axboe <axboe@suse.de>
To: Markus Plail <linux-kernel@gitteundmarkus.de>
Cc: linux-kernel@vger.kernel.org, ed.sweetman@wmich.edu
Subject: Re: atapi write support? No
Date: Wed, 10 Sep 2003 10:33:51 +0200 [thread overview]
Message-ID: <20030910083351.GK20800@suse.de> (raw)
In-Reply-To: <87brttemlk.fsf@gitteundmarkus.de>
On Tue, Sep 09 2003, Markus Plail wrote:
> On Tue, 09 Sep 2003, Ed Sweetman wrote:
>
> >Jens Axboe wrote:
> >> On Tue, Sep 09 2003, Ed Sweetman wrote:
> > There is no other information needed.
>
> There is...
>
> > By use atapi write support i mean Get it to do anything besides error
> > out reporting that it cant access the drive. If you can query the
> > drive much less actually write anything to it using the ATAPI
> > interface than that's more than i've been able to do.
> >
> > for example cdrecord dev=ATAPI:1,0,0 checkdisk
>
> ATAPI: is most likely wrong for what you want to do. It's meant for
> notebooks (PCATA or something).
> If you just want to get rid of ide-scsi, you have to use dev=/dev/hdX in
> cdrecord.
That ATAPI support is slow and unreliable, Joerg was a fool to merge it.
It shold _not_ be used! Using dev=/dev/hdX is required for SG_IO in 2.6
right now, other methods should be usable in the future. So Markus is
dead right.
> PS: A little change in attitude towards people who are willing to help
> you wouldn't be the worst idea. IMHO of course.
Indeed, and doing just a little work before showing up with an attitude
would be even better. It's amazing how people asking for help think they
can define the rules as well.
--
Jens Axboe
prev parent reply other threads:[~2003-09-10 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 19:36 atapi write support? No Ed Sweetman
2003-09-09 19:54 ` Jens Axboe
2003-09-09 20:09 ` Ed Sweetman
2003-09-09 20:16 ` Jens Axboe
2003-09-09 20:24 ` Markus Plail
2003-09-09 22:04 ` Ed Sweetman
2003-09-10 6:11 ` Markus Plail
2003-09-10 8:33 ` Jens Axboe [this message]
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=20030910083351.GK20800@suse.de \
--to=axboe@suse.de \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@gitteundmarkus.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox