public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Ian Hastie <ianh@iahastie.clara.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide-scsi oops was: 2.6.0-test4-mm3
Date: Wed, 17 Sep 2003 12:31:27 +0200	[thread overview]
Message-ID: <20030917103127.GM906@suse.de> (raw)
In-Reply-To: <200309161926.04549.ianh@iahastie.local.net>

On Tue, Sep 16 2003, Ian Hastie wrote:
> On Tuesday 16 Sep 2003 10:20, Jens Axboe wrote:
> > On Tue, Sep 16 2003, Ian Hastie wrote:
> > > On Thursday 11 Sep 2003 22:52, Jens Axboe wrote:
> > > > Surely the pro version supports open-by-device as well? And then it
> > > > should work fine.
> > >
> > > It does.  However it also produces the same error message as cdrecord
> > > when doing so, ie
> > >
> > > Warning: Open by 'devname' is unintentional and not supported.
> > >
> > > The implication being that it could go away or become broken at any time.
> >
> > I wouldn't read anything in to that if I were you. Joerg has some mis
> > guided ideas about ATAPI addressing, but he would be a fool to remove
> > open by devname at this point.
> 
> What about this version of the argument then?  There are a number if
> pieces of software, eg cdrdao, that don't support open by devname.
> The kernel developers would be foolish to remove support for them at
> this time.  Works both ways doesn't it.

(cc me if you want me to read the mails, thanks)

That's a different discussion - they don't work with SG_IO typically
either, so they await the block sg driver anyways. It doesn't change the
fact that trying to pretend devices are hanging off a SCSI bus with bus
and device ids when they are not is just horrible.

-- 
Jens Axboe


  parent reply	other threads:[~2003-09-17 10:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29  6:56 2.6.0-test4-mm3 Andrew Morton
2003-08-29  7:45 ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:42 ` 2.6.0-test4-mm3 Ed Sweetman
2003-08-29 15:57   ` 2.6.0-test4-mm3 Andrew Morton
2003-08-29 15:59   ` 2.6.0-test4-mm3 Felipe Alfaro Solana
2003-08-30  1:43 ` OOps in 2.6.0-test4-mm3-1 Mike Fedyk
2003-08-30  3:09   ` Andrew Morton
2003-08-30 23:20     ` Mike Fedyk
2003-08-30 23:36       ` Andrew Morton
2003-09-10 18:53 ` 2.6.0-test4-mm3 Mike Fedyk
2003-09-10 18:55   ` ide-scsi oops was: 2.6.0-test4-mm3 Mike Fedyk
2003-09-10 18:43     ` Andrew Morton
2003-09-10 19:10       ` Mike Fedyk
2003-09-11 15:24         ` Alan Cox
2003-09-10 20:04       ` Martin J. Bligh
2003-09-10 20:35         ` Murray J. Root
2003-09-10 20:53         ` Paul Larson
2003-09-10 21:11           ` Sandisk WiFi + CF card question J.C. Wren
2003-09-11  8:20         ` ide-scsi oops was: 2.6.0-test4-mm3 Jens Axboe
2003-09-11 15:12           ` Gerhard Mack
2003-09-11 21:52             ` Jens Axboe
2003-09-11 15:27           ` Alan Cox
2003-09-11 21:50             ` Jens Axboe
2003-09-11 18:13           ` Martin J. Bligh
2003-09-11 18:30             ` Mike Fedyk
2003-09-11 21:52             ` Jens Axboe
2003-09-16  0:34               ` Ian Hastie
2003-09-16  9:20                 ` Jens Axboe
2003-09-16 18:26                   ` Ian Hastie
2003-09-16 18:58                     ` Mike Fedyk
2003-09-17 10:31                     ` Jens Axboe [this message]
2003-09-16 21:41 ` OOps in HFS " Mike Fedyk
2003-09-16 21:40   ` Andrew Morton
2003-09-16 23:59     ` Mike Fedyk

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=20030917103127.GM906@suse.de \
    --to=axboe@suse.de \
    --cc=ianh@iahastie.clara.net \
    --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