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 13:38:09 -0400 [thread overview]
Message-ID: <20040529173809.GB24516@devserv.devel.redhat.com> (raw)
In-Reply-To: <1085851726.2004.186.camel@mulgrave>
On Sat, May 29, 2004 at 12:28:45PM -0500, James Bottomley wrote:
> > think anyone who gets told "the major supplier of this OS has arbitarily
> > broken your software during stable releases for no good reason" is likely
> > to update their firmware.
>
> Actually, yes, I think Linux is growing enough market momentum for them
> to take notice.
If we act professionally maybe. But breaking that the way FC2 did wasnt
professional
> depending on what your after, device scanning (without any ULDs,
> including sg) is simple in 2.6; it's ls /sys/bus/scsi/devices.
and opening those is probably a 2.7 way to get rid of /dev/sg
> There's no patch to veto yet. If you redhat people are taking it out of
> fedora, then, for 2.6, there probably never will be.
That is Arjan's call. I already build Fedora 2 kernels with it removed
and I'm far from unique in that. The simple fact its an API change makes
it a 2.7 kernel thing.
next prev parent reply other threads:[~2004-05-29 17:38 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
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 [this message]
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=20040529173809.GB24516@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