From: Arjan van de Ven <arjanv@redhat.com>
To: Alan Cox <alan@redhat.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Douglas Gilbert <dougg@torque.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: sg driver and Fedora Core 2
Date: Sat, 29 May 2004 18:36:42 +0200 [thread overview]
Message-ID: <20040529163641.GG31365@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040529162912.GA5922@devserv.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Sat, May 29, 2004 at 12:29:12PM -0400, Alan Cox wrote:
>
> Fedora bugzilla has demonstrated it *doesn't* work.
yes cdrecord broke due to a bug in cdrecord and a somewhat discutable
behavior difference between SG_IO and /dev/sg when it comes to oversized IO
(which cdrecord issues as a result of it's own bug)
> There is a long list
> of broken third party apps such as drive firmware tools many of which will
> never include source code. The whole point of sg is arbitary management of
> devices.
*AND SG_IO IS THAT*. You seem to ignore that consistently.
What changed is that you don't need top open some OTHER device to send
arbitrary commands to /dev/sda, but you can open /dev/sda directly to send
those commands, with the same ioctl. THAT changed. Don't tell me that very
long list of third party apps ALL doesn't take a device as argument....
undoubtedly several don't but... "long list"...
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-29 16:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 14:05 sg driver and Fedora Core 2 Douglas Gilbert
2004-05-28 14:18 ` Jens Axboe
2004-05-28 14:28 ` Jens Axboe
2004-05-28 17:25 ` Alan Cox
2004-05-29 15:55 ` James Bottomley
2004-05-29 15:57 ` Alan Cox
2004-05-29 16:07 ` James Bottomley
2004-05-29 16:29 ` Alan Cox
2004-05-29 16:36 ` Arjan van de Ven [this message]
2004-05-29 16:42 ` Alan Cox
2004-05-29 17:45 ` Matthew Wilcox
2004-05-29 16:49 ` James Bottomley
2004-05-29 16:56 ` Alan Cox
2004-05-29 17:28 ` James Bottomley
2004-05-29 17:38 ` Alan Cox
2004-05-29 17:27 ` Jeff Garzik
2004-05-29 17:29 ` Jens Axboe
2004-05-30 10:37 ` Douglas Gilbert
2004-05-30 10:41 ` Alan Cox
2004-06-07 8:56 ` Douglas Gilbert
2004-05-29 17:35 ` Alan Cox
2004-05-29 17:42 ` Jeff Garzik
2004-05-29 17:38 ` James Bottomley
2004-05-29 17:46 ` Alan Cox
2004-05-29 17:58 ` Jeff Garzik
2004-05-30 10:20 ` Jens Axboe
2004-05-29 16:24 ` Arjan van de Ven
2004-05-28 17:39 ` Arjan van de Ven
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=20040529163641.GG31365@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=alan@redhat.com \
--cc=dougg@torque.net \
--cc=linux-scsi@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