From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Markus Plail <linux-kernel@gitteundmarkus.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: atapi write support? No
Date: Tue, 09 Sep 2003 18:04:30 -0400 [thread overview]
Message-ID: <3F5E4E6E.1070806@wmich.edu> (raw)
In-Reply-To: <87brttemlk.fsf@gitteundmarkus.de>
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...
You seemed to get it without any more.
>
>>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.
this method states that the method of access is unsupported and
unintentional. Which is why i didn't think that it was the right way to
use cdrecord on atapi devices without ide-scsi.
> regards
> Markus
>
> PS: A little change in attitude towards people who are willing to help
> you wouldn't be the worst idea. IMHO of course.
>
If you make what is a general question too specific with details you
limit your responses if anyone thinks their response is correct for you
anyway. I limited my question as much as i wanted to, with the desired
effect no less.
apparently cdrecord's documention is a little behind it's code. Now
tracking down why it seems to be botching audio cds for me would require
a full bugreport style mail now that i know cdrecord is being used in
the correct manner.
next prev parent reply other threads:[~2003-09-09 22:04 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 [this message]
2003-09-10 6:11 ` Markus Plail
2003-09-10 8:33 ` Jens Axboe
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=3F5E4E6E.1070806@wmich.edu \
--to=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