From: Alan Cox <alan@redhat.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Alan Cox <alan@redhat.com>, Douglas Gilbert <dougg@torque.net>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: sg driver and Fedora Core 2
Date: Sat, 29 May 2004 12:29:12 -0400 [thread overview]
Message-ID: <20040529162912.GA5922@devserv.devel.redhat.com> (raw)
In-Reply-To: <1085846840.2103.47.camel@mulgrave>
On Sat, May 29, 2004 at 11:07:19AM -0500, James Bottomley wrote:
> > insmod scsidriver
> > open /dev/sg0 (a hard disk)
> > insmod sd
>
> Refuse the insertion or do not attach, I suppose. It would be the app's
> fault for not managing the interface correctly.
So you stop users being able to hotplug controllers while doing firmware
updates. Thats not good either
> about to make any change like it at this point. But, if fedora can
> demonstrate that it can be made to work sanely and easily, that would be
> a very powerful argument for inclusion.
Fedora bugzilla has demonstrated it *doesn't* work. 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. Its like /dev/mem and so forth, its power is in the fact it can
always be used. This is why Linus vetoed the entire concept.
Fedora hasn't solved the open /dev/sg , insmod case either.
next prev parent reply other threads:[~2004-05-29 16:29 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 [this message]
2004-05-29 16:36 ` Arjan van de Ven
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=20040529162912.GA5922@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjanv@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