From: Bill Davidsen <davidsen@tmr.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-rc1/2 CD/DVD burning broken
Date: Thu, 28 Feb 2008 13:41:43 -0500 [thread overview]
Message-ID: <47C70067.6060205@tmr.com> (raw)
In-Reply-To: <E1JR1e0-0001R1-IR@faramir.fjphome.nl>
Frans Pop wrote:
> Joerg Schilling wrote:
>> This fragment is much too short to allow to judge on possible reasons.
>> There is a high probability that your problem is caused by the cdrecord
>> fork called "wodim".
>
> There is also the 100% certainty that this reply was from a known troll and
> should just be ignored.
Actually he is the author of the software in question, and has
maintained it for a decade. Anyone who reads the cdwrite mailing list
knows that I have criticized his endless whining that Linux doesn't do
things right, but aside from the cosole output whining about Linux from
his program[1], and the fact that it must run as root[2], the real
cdrecord works in more cases, with more hardware, produces working burns
in more cases, and has more useful output, and is the software to use in
preference to wodim.
[1] cdrecord advises to use Linux 2.4 (and I think Solaris), and says
you should avoid using readable names for devices and use some
pseudo-SCSI numbers he likes instead.
[2] Linux developers filter commands sent to devices to protect them
from commands like erase BIOS. Joerg uses vendor proprietary commands
for greater functionality, and says if you have write on the device it
shouldn't be filtered and those commands should be permitted by the
filter. (That is a simplification, there are personal issues on both sides).
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-02-28 18:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 23:21 2.6.25-rc1/2 CD/DVD burning broken Joerg Schilling
2008-02-17 23:51 ` Jan Engelhardt
2008-02-18 11:28 ` Joerg Schilling
2008-02-18 11:32 ` Jan Engelhardt
2008-02-18 8:46 ` Frans Pop
2008-02-18 8:56 ` Mike Galbraith
2008-02-18 10:31 ` Frans Pop
2008-02-18 11:41 ` Mike Galbraith
2008-02-18 23:27 ` Jan Engelhardt
2008-02-28 18:41 ` Bill Davidsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-16 20:52 Andreas Schwab
2008-02-17 0:09 ` Jeff Garzik
2008-02-17 0:48 ` Andreas Schwab
2008-02-17 3:57 ` Mark Lord
2008-02-17 9:33 ` Andreas Schwab
2008-02-18 15:59 ` Bartlomiej Zolnierkiewicz
2008-02-18 18:58 ` Kiyoshi Ueda
2008-02-18 19:55 ` Laura Garcia
2008-02-18 20:19 ` Andreas Schwab
2008-02-18 20:20 ` Borislav Petkov
2008-02-18 22:37 ` Borislav Petkov
2008-02-23 15:47 ` Andreas Schwab
2008-02-24 16:32 ` Borislav Petkov
2008-02-24 16:59 ` Andreas Schwab
2008-02-25 2:49 ` Kiyoshi Ueda
2008-02-25 9:23 ` Andreas Schwab
2008-02-25 19:38 ` Andreas Schwab
2008-02-25 20:45 ` Borislav Petkov
2008-02-25 22:08 ` Andreas Schwab
2008-02-26 4:24 ` Borislav Petkov
2008-02-26 14:52 ` Andreas Schwab
2008-02-26 17:38 ` Borislav Petkov
2008-02-26 20:01 ` Bartlomiej Zolnierkiewicz
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=47C70067.6060205@tmr.com \
--to=davidsen@tmr.com \
--cc=elendil@planet.nl \
--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