All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@redhat.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Alan Cox <alan@redhat.com>,
	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 12:42:39 -0400	[thread overview]
Message-ID: <20040529164239.GA8855@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040529163641.GG31365@devserv.devel.redhat.com>

On Sat, May 29, 2004 at 06:36:42PM +0200, Arjan van de Ven wrote:
> > 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.

Unfortunately my devices randomly change name according to what is loaded

> 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"...

I had to recompile my kernel to flash my scsi drive firmware. It works
in the generic kernel but not in 2.6.5-Fedora. That alone says its not
an acceptable change for a "stable" kernel tree - which hopefully 2.6.x
will become in the next six months.

(If you want to argue about 2.7.x then its somewhat different - if scsi
 devices appear in sysfs and the sysfs nodes also support SG_IO then the
 entire notion of /dev/sg could go away in 2.7)



  reply	other threads:[~2004-05-29 16:42 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 [this message]
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=20040529164239.GA8855@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.