From: Jens Axboe <jens.axboe@oracle.com>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: teunis@alphatrade.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19 kernel series, SATA, wodim (cd recording), synaptics update,
Date: Thu, 14 Dec 2006 19:01:09 +0100 [thread overview]
Message-ID: <20061214180108.GF5010@kernel.dk> (raw)
In-Reply-To: <4581688c.HZdDIJzhKiuGBiO9%Joerg.Schilling@fokus.fraunhofer.de>
On Thu, Dec 14 2006, Joerg Schilling wrote:
> Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > On Thu, Dec 14 2006, Joerg Schilling wrote:
> > > >CD recording : recorder no longer detected by "wodim" software set in
> > > >2.6.19. I suspect it's a bug in the software... but don't know where
> > > >to look for changes. 2.6.19-rc5 worked.
> > > >hardware: IDE MATSHITADVD-RAM UJ-820S
> > > >(2.6.19-git6 also fails with external LiteON USB DVD burner)
> >
> > It was an intermittent unlucky bug between 2.6.19 and 2.6.20-rc1, it got
> > fixed the other day. Update your kernel, and it'll work again.
>
> OK, thank you for the info.
No problem, I should mention that it's 2.6.19 to 2.6.20-rc1, both
versions exclusive.
> > > Do not use cdrecord derivates but the original as derivates may have bugs
> > > that are not present in the original.
> >
> > And vice versa :-)
>
> I know of no problem that is only in the original, but there are
> dozens of problems that have been fixed since the derivate has been
> frozen in May.
I don't know of any real bugs, was purely speaking in logical terms. A
derivative could equally well have bugs fixed that are not in the
original version. It could also have introduced new, as you mention.
--
Jens Axboe
next prev parent reply other threads:[~2006-12-14 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 13:46 2.6.19 kernel series, SATA, wodim (cd recording), synaptics update, Joerg Schilling
2006-12-14 14:03 ` Jens Axboe
2006-12-14 15:06 ` Joerg Schilling
2006-12-14 18:01 ` Jens Axboe [this message]
2006-12-15 17:18 ` Bill Davidsen
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=20061214180108.GF5010@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=teunis@alphatrade.com \
/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.