From: Wolfgang Draxinger <wdraxinger@darkstargames.de>
To: linux-kernel@vger.kernel.org
Subject: Jörg Schilling again... [Please reply CC: wdraxinger@darkstargames.de]
Date: Tue, 14 Jun 2005 12:18:21 +0200 [thread overview]
Message-ID: <200506141218.29200.wdraxinger@darkstargames.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
A few weeks ago I was updating cdrecord, and as ever when doing
updates I'm RTFM (as any user should). Now while doing so I ran about
a few lines, complainung about the Linux developers attitude to some
patched, and so on, well, the address developers surely know what I
mean. However I was disturbed by the fact, that despite a lot of
flaming there only few code examples. Admittingly: Not getting back
the SCSI error codes is a problem (it somehow reminds me on the GPL
vs. BSD joke, where GPL people try to fetch any sort of error while
BSD people just don't let errors happen), but communicating with HW
it's surely a good idea to do as much error checking possible, as
long it's for a sane reason and not just for the heck of it.
So there was this patch by Jörg Schilling, which IMHO inroduced a nice
solution to the problem, yet keeping compatibility. The awnser by
Douglas Gilbert seemed not so elegant to me. However I also know that
you don't reject a patch without reason. And this is what I wasn't
able to find on the archives.
Lately I had a few emails with Jörg and despite his contra Linux
attitude (Ok, he likes OpenSolaris more than Linux, so let him do so;
but instead of OpenSolaris, which tries to follow a pure academic
style, Linux _just works_) I got no information of any real technical
value.
Well I didn't cared about the so called issues, as I never had
problems with cdrecord - ok the SUID bug required me to workaround,
but nothing that a 5 line sh script and a "%cdrw ALL=(ALL)
NOPASSWD: /usr/bin/cdrecord.real" rule for sudo can't solve.
But a today's post on heise.de user forums really made me wonder,
what's the problem of the guy is - on a pure technically base.
So what's the Linux Kernel developers' opinion on the lack of SCSI
error code return, technically?
Happy coding
--
Wolfgang Draxinger
lead programmer - DARKSTARgames
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-06-14 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 10:18 Wolfgang Draxinger [this message]
2005-06-14 11:10 ` Andi Kleen
2005-06-15 3:25 ` Bill Davidsen
2005-06-15 9:24 ` Bartlomiej Zolnierkiewicz
[not found] <4fgGA-7S1-7@gated-at.bofh.it>
2005-06-14 22:46 ` Bodo Eggert
2005-06-15 8:32 ` Måns Rullgård
[not found] <4fsop-zf-13@gated-at.bofh.it>
[not found] ` <4fsop-zf-11@gated-at.bofh.it>
[not found] ` <4fBBk-7l0-3@gated-at.bofh.it>
2005-06-17 8:47 ` Bodo Eggert
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=200506141218.29200.wdraxinger@darkstargames.de \
--to=wdraxinger@darkstargames.de \
--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
all inboxes | Powered by JetHome®