All of lore.kernel.org
 help / color / mirror / Atom feed
From: tabris <tabris@tabris.net>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org,
	"Alexander E. Patrakov" <patrakov@ums.usu.ru>,
	arklinux-list <arklinux-list@arklinux.org>
Subject: Re: ide-cd problems
Date: Mon, 2 Aug 2004 10:38:16 -0400	[thread overview]
Message-ID: <200408021038.17268.tabris@tabris.net> (raw)
In-Reply-To: <20040802135615.GX10496@suse.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 02 August 2004 9:56 am, Jens Axboe wrote:
> On Mon, Aug 02 2004, tabris wrote:
> > On Sunday 01 August 2004 11:57 am, Jens Axboe wrote:
> > > On Sun, Aug 01 2004, Alexander E. Patrakov wrote:
> > > > Zinx Verituse wrote:
<snip>
> > > Don't ever use that interface, period. It's not just the cdrecord
> > > code that may be alpha (I doubt it matters, it's easy to use),
> > > the interface it uses is not worth the lines of code it occupies.
> >
> > 	Then we have a severe disagreement between the cdrecord code (or
> > at least the runtime warnings) and the Linux-Kernel IDE folks.
> > specifically, these lines, while running with cdrecord
> > dev=/dev/cdrom
<snip>
> Warning: Open by 'devname' is unintentional and not supported.
>
> just says that open-by-device name is unintentional, it doesn't give
> you warnings on the transport.
>
> So in short (and repeating): don't use ATAPI (CDROM_SEND_PACKET), it
> sucks. Use SG_IO (which means using open-by-device, which works at
> least as well as the stupid faked ATAPI bus/id/lun crap and has the
> much better transport). Don't compare apples and oranges.
I'll take your point on the technical merits.

But now I get to wondering what to do about all the old HOWTOs. the 
cdrecord folks aren't helping.

	Maybe instead what should be done is a BIG FAT WARNING in the syslog? 
that the CDROM_SEND_PACKET interface is deprecated in kernel 2.6? I 
know that I personally can listen and take your advice, but I worry 
more about the rest of the users, who either will not hear, or will 
hear too many conflicting things. Perhaps it won't help, but I'd really 
like to be able to sell this stuff. And among the necessary things is 
to be able to have sane warnings, and not have warnings that will scare 
my customers off!

	Yes, this isn't really your (you==Jens) problem, but probably the 
distro maintainers (cc:d ArkLinux) to put in patches silencing some of 
these warnings, and/or change the default behaviour of their front-end 
tools.

	I merely hope to find some sanity. Though I have a feeling I'm looking 
in the wrong places (Free and Open Source).

- --
tabris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBDlHY1U5ZaPMbKQcRAnrhAJwPM+sSRInlRy5kmpqQ+nlwS+1D5QCbBZc6
8NsRqRQqLddQgY8FuCzEvck=
=BhCR
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-08-02 14:40 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 19:36 ide-cd problems Zinx Verituse
2004-07-31 15:36 ` Jens Axboe
2004-07-31 18:27   ` Zinx Verituse
2004-07-31 20:00     ` Jens Axboe
2004-07-31 21:02       ` Zinx Verituse
2004-08-01  4:07         ` Alexander E. Patrakov
2004-08-01 15:57           ` Jens Axboe
2004-08-02  3:20             ` Horst von Brand
2004-08-02 12:25               ` Jens Axboe
2004-08-02 20:44               ` Bill Davidsen
2004-08-02 13:45             ` tabris
2004-08-02 13:56               ` Jens Axboe
2004-08-02 14:26                 ` Andreas Metzler
2004-08-02 14:33                   ` Jens Axboe
2004-08-02 14:38                 ` tabris [this message]
2004-08-02 14:50                   ` Jens Axboe
2004-08-02 16:30           ` Bill Davidsen
2004-08-03  7:17             ` Jens Axboe
2004-08-02 17:16         ` Zinx Verituse
2004-08-05  5:40         ` Jens Axboe
2004-08-05 21:06           ` Alan Cox
2004-08-06  5:44             ` Jens Axboe
     [not found]               ` <20040806062331.GE10274@suse.de>
2004-08-06 12:14                 ` Alan Cox
2004-08-06 14:32                   ` Jens Axboe
2004-08-06 15:14                     ` Charles Cazabon
2004-08-06 15:13                       ` Jens Axboe
2004-08-07 14:01                       ` Alan Cox
2004-08-06 17:26                     ` dleonard
2004-08-06 22:47                       ` Jens Axboe
2004-08-07 14:04                         ` Alan Cox
2004-08-07 21:54                           ` Alan Cox
2004-08-07  3:11                     ` Jason L Tibbitts III
2004-08-09  8:39                       ` Jens Axboe
2004-08-07 14:08                     ` Alan Cox
2004-08-09  8:49                       ` Jens Axboe
2004-08-02 23:54       ` Alan Cox
2004-08-03  5:53         ` Jens Axboe
2004-08-03 16:17           ` Zinx Verituse
2004-08-04  5:01             ` Jens Axboe
2004-08-05 15:52               ` Alan Cox
2004-08-05 17:46                 ` Jens Axboe
2004-08-05 20:58                   ` Alan Cox
2004-08-05 18:53                 ` Bill Davidsen
2004-08-05 18:46           ` Bill Davidsen
2004-08-05 19:35             ` Jens Axboe
2004-08-05 21:02               ` Alan Cox
2004-08-06  5:42                 ` Jens Axboe
2004-08-03 15:28         ` Doug Maxey
2004-08-03 17:28           ` Alan Cox
2004-08-09 20:24       ` Bill Davidsen
2004-08-02 16:41   ` Bill Davidsen
2004-08-03 15:50     ` Horst von Brand

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=200408021038.17268.tabris@tabris.net \
    --to=tabris@tabris.net \
    --cc=arklinux-list@arklinux.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrakov@ums.usu.ru \
    /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.