From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christer Weinigel <christer@weinigel.se>,
James Bottomley <James.Bottomley@SteelEye.com>,
Jens Axboe <axboe@suse.de>,
linux-scsi@vger.kernel.org
Subject: Re: cd burning with plextor drives.
Date: Mon, 31 Jul 2006 16:38:07 -0400 [thread overview]
Message-ID: <20060731203807.GE4631@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607311328541.4168@g5.osdl.org>
On Mon, Jul 31, 2006 at 01:32:53PM -0700, Linus Torvalds wrote:
>
>
> On Sun, 31 Jul 2006, Christer Weinigel wrote:
> >
> > Yes, a lot of those CD burners are ancient. But I like the fact that
> > Linux supports a lot of ancient hardware. :-)
>
> Sure. But I don't think we should necessarily design any new code for it.
> It's not like this has _ever_ worked differently from what it does now, so
> if you have one of the pre-MMC drives, the right answer right now (and
> always has been, I think) is that you need to be root to burn them.
>
> I seriously doubt anybody _really_ cares.
>
> That said, I don't think Peter Jones' patch is wrong. I don't have any
> strong feelings about it - if people actually want this adn feels it
> improves the situation, why not? Although to actually make _sense_, we'd
> want to have distros that actually want to use the interface to
> auto-populate the command things or something.. In the absense of interest
> from distros, I don't think it is worth it.
With my distro vendor hat on, I'm interested in anything that makes
these bug reports go away. I don't particularly care on the mechanism,
but we need *something*.
Should his patch be accepted, Peter would likely be the poor soul who gets
to implement the userspace bits for Fedora anyway, and I doubt he would've
hacked up the patch if he hadn't intended to do so :)
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-31 20:38 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 4:52 cd burning with plextor drives Dave Jones
2006-07-29 11:12 ` Jens Axboe
2006-07-29 13:40 ` James Bottomley
2006-07-29 15:39 ` Christer Weinigel
2006-07-29 17:06 ` Linus Torvalds
2006-07-29 17:30 ` James Bottomley
2006-07-29 17:49 ` Linus Torvalds
2006-07-30 16:02 ` Christer Weinigel
2006-07-30 19:57 ` Linus Torvalds
2006-07-30 20:18 ` Christian Iversen
2006-07-31 0:12 ` Christer Weinigel
2006-07-31 20:32 ` Linus Torvalds
2006-07-31 20:38 ` Dave Jones [this message]
2006-07-31 20:41 ` Jens Axboe
2006-07-31 20:46 ` Linus Torvalds
2006-08-01 6:54 ` Jens Axboe
2006-07-29 18:39 ` Douglas Gilbert
2006-07-29 18:54 ` Linus Torvalds
2006-07-29 20:12 ` Douglas Gilbert
2006-07-29 20:33 ` Linus Torvalds
2006-07-29 20:53 ` Linus Torvalds
2006-07-29 22:13 ` Arjan van de Ven
2006-07-30 5:57 ` Matthew Wilcox
2006-07-30 9:38 ` Rogier Wolff
2006-07-30 18:02 ` Douglas Gilbert
2006-07-30 20:06 ` Linus Torvalds
2006-07-29 21:40 ` Christer Weinigel
2006-07-30 5:56 ` Linus Torvalds
2006-07-29 17:04 ` Linus Torvalds
2006-07-29 17:22 ` Dave Jones
2006-07-30 10:21 ` Rogier Wolff
2006-07-30 10:31 ` Arjan van de Ven
2006-07-30 11:09 ` Steve McIntyre
2006-07-31 9:33 ` Jens Axboe
2006-07-31 9:32 ` Jens Axboe
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=20060731203807.GE4631@redhat.com \
--to=davej@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=axboe@suse.de \
--cc=christer@weinigel.se \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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