From: Brian Litzinger <brian@worldcontrol.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: Summarizing the PWC driver questions/answers
Date: Mon, 30 Aug 2004 10:31:57 -0700 [thread overview]
Message-ID: <20040830173157.GA24392@top.worldcontrol.com> (raw)
In-Reply-To: <20040827162613.GB32244@kroah.com>
On Fri, Aug 27, 2004 at 09:26:13AM -0700, Greg KH wrote:
> Q: Why did you remove the hook from the pwc driver?
> A: It was there for the explicit purpose to support a binary only
> module. That goes against the kernel's documented procedures, so I
> had to take it out.
I think Greg "chose" to take it out.
> Q: That hook had been in there for years! Why did you suddenly decide
> to remove it now?
> A: I was really not aware of the hook, and the fact that it was only
> good for a binary module to use. I'm sorry, I should have realized
> this years ago, but I didn't. Recently someone pointed this hook out
> to me, and the fact that it really didn't belong in there due to the
> kernel's policy of such hooks. So, once I became aware of it, I had
> no choice but to remove it.
I do not believe he "had no choice". The guards at Auswitchs made the
same argument at Nuremberg. The tribunal determined they did have a
choice. I doubt we can consider the conditions here more extreme
then there.
> Q: But you took away my freedom! Isn't Linux about freedom?
> A: Again, it was Nemosoft's decision. The kernel also has to abide by
> it's documented procedures, so that is why the hook had to go.
The kernel cannot act itself. It is more or less an inanimate
object. People must carry out actions on its behalf.
> Q: You jerk, I had invested lots of money in this camera, you are
> costing me money by ripping it out. You should be ashamed of
> yourself!
> A: See the above question about freedom. If it means that much to you,
> then offer to maintain the code, it's that simple.
This confuses me. The functionability people are after is the closed
source part. Maintaining the open source portion seems unrelated.
> Q: You are keeping companies from wanting to write binary drivers for
> Linux.
> A: Duh! What do you think all of the kernel developers have been
> stating for years, in public. Binary drivers only take from Linux,
> they do not give back anything. See Andrew Morton's OLS 2004 keynote
> address for more information and background on this topic.
I disagree. Binary drivers may take away from Linux and they may add to it.
> Q: You are a fundamentalist turd / jerk / pompous ass /
> GNU-freebeer-biased-idiot-fundamentalist fucktard / ignorant slut!
> A: I've been called worse by better people, get over yourself.
I think from statements Greg made above we can at least say he is
willing to hide behind misplaced authority.
--
Brian Litzinger
next prev parent reply other threads:[~2004-08-30 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 16:26 Summarizing the PWC driver questions/answers Greg KH
2004-08-27 16:58 ` David Woodhouse
2004-08-27 18:26 ` Wouter Van Hemel
2004-08-27 19:05 ` Ian Romanick
2004-08-27 20:36 ` Wouter Van Hemel
2004-08-27 16:58 ` Prakash K. Cheemplavam
2004-08-27 17:54 ` Roman Zippel
2004-08-27 18:51 ` [linux-usb-devel] " Alan Stern
2004-08-27 20:31 ` Greg KH
2004-08-30 17:31 ` Brian Litzinger [this message]
2004-08-30 18:24 ` Jeff Kinz
2004-08-30 19:28 ` viro
2004-08-30 20:11 ` Kenneth Lavrsen
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 19:54 Kenneth Lavrsen
2004-08-27 20:22 ` David S. Miller
2004-08-27 20:30 ` David Ford
2004-08-27 21:26 ` Wouter Van Hemel
2004-08-27 20:32 ` Zwane Mwaikambo
2004-08-27 21:25 ` Jesper Juhl
[not found] ` <Pine.LNX.4.61.0408272259450.2771@dragon.hygekrogen.localho st>
2004-08-27 22:08 ` Kenneth Lavrsen
2004-08-27 23:01 ` Bernd Petrovitsch
2004-08-28 0:22 ` Paul Jakma
2004-08-30 12:04 ` Geert Uytterhoeven
2004-08-28 21:07 linux
2004-08-28 22:06 ` Oliver Neukum
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=20040830173157.GA24392@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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