From: Jeff Garzik <jgarzik@pobox.com>
To: James Buchanan <jamesbuch@iprimus.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel rant
Date: Thu, 20 Feb 2003 12:22:24 -0500 [thread overview]
Message-ID: <20030220172224.GD9800@gtf.org> (raw)
In-Reply-To: <200302211551.28222.jamesbuch@iprimus.com.au>
On Fri, Feb 21, 2003 at 03:51:28PM +1100, James Buchanan wrote:
> Linux is starting to include code written under non-disclosure
> agreements and other nasties, and for me this kills the magic of
> Linux. Doesn't stop anyone from reading the code, but it's the
> principle that counts.
This has been going on for ages -- and happens in FreeBSD all the time
too.
I can point to multiple BSD net drivers written under NDA, for example.
It's the way of the hardware world.
If you don't get an NDA, you don't get open source support.
Jeff
next prev parent reply other threads:[~2003-02-20 17:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 4:51 Linux kernel rant James Buchanan
2003-02-20 17:22 ` Jeff Garzik [this message]
2003-02-20 17:26 ` Tomas Szepe
2003-02-21 5:42 ` James Buchanan
2003-02-20 17:45 ` Tomas Szepe
2003-02-21 5:54 ` James Buchanan
2003-02-20 18:15 ` Tomas Szepe
2003-02-21 6:23 ` James Buchanan
2003-02-20 18:20 ` Rik van Riel
2003-02-21 6:24 ` James Buchanan
2003-02-20 17:54 ` Rik van Riel
2003-02-21 6:01 ` James Buchanan
2003-02-20 18:09 ` Rik van Riel
2003-02-21 6:17 ` James Buchanan
2003-02-20 18:19 ` Rik van Riel
2003-02-20 18:20 ` Tomas Szepe
2003-02-21 6:25 ` James Buchanan
2003-02-21 14:53 ` Chris Friesen
2003-02-21 15:34 ` Dave Jones
2003-02-20 18:22 ` Jeff Garzik
2003-02-21 6:29 ` James Buchanan
2003-02-20 18:02 ` Jeff Garzik
2003-02-21 6:21 ` James Buchanan
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=20030220172224.GD9800@gtf.org \
--to=jgarzik@pobox.com \
--cc=jamesbuch@iprimus.com.au \
--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