From: ebiederm@xmission.com (Eric W. Biederman)
To: "Riley Williams" <Riley@Williams.Name>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Using GPL'd Linux drivers with non-GPL, binary-only kernel
Date: 07 May 2003 10:57:41 -0600 [thread overview]
Message-ID: <m1issm8zju.fsf@frodo.biederman.org> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
"Riley Williams" <Riley@Williams.Name> writes:
> Hi Eric.
>
> >> I disagree. Many of the most successful TCP stacks _forked_ from the
> >> BSD one at some time or other (e.g. SunOS, Microsoft), but then they
> >> evolved in their own directions, with their unique quirks.
>
> > And that ultimate fate and people shutting up has created a number of
> > advocates for the GPL. And at the very least people will now insist
> > on getting the source and the writes to modify and share their
> > modifications of the source. To some extent this is behind the large
> > national labs wanting Linux on their supercomputers.
>
> Do you have any web pointers relating to this issue or those advocates?
That enumerates these issues no. From a practical standpoint
on systems built or proposed, I can here are a couple.
>From Lawrence Livermore National Labs see MCR:
http://www.llnl.gov/linux/mcr
Position #5 on the top500 list
http://top500.org/list/2002/11/
see the ASCI Purple RFP:
http://www.llnl.gov/asci/purple/
>From Los Alamos National Labs see Pink:
http://www.lanl.gov/projects/pink/
Eric
next parent reply other threads:[~2003-05-07 16:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BKEGKPICNAKILKJKMHCAAEBCCLAA.Riley@Williams.Name>
2003-05-07 16:57 ` Eric W. Biederman [this message]
2003-05-13 9:08 Using GPL'd Linux drivers with non-GPL, binary-only kernel Dean McEwan
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 1:23 Jean Tourrilhes
[not found] <20030506165014$3d57@gated-at.bofh.it>
[not found] ` <20030506193019$0d29@gated-at.bofh.it>
[not found] ` <20030506220018$5b96@gated-at.bofh.it>
2003-05-07 1:17 ` Tony 'Nicoya' Mantler
2003-05-06 16:42 Jamie Lokier
2003-05-06 17:35 ` Alan Cox
2003-05-06 18:54 ` Jamie Lokier
2003-05-06 19:28 ` Jean-Marc Lienher
2003-05-06 19:53 ` Alan Cox
2003-05-06 22:31 ` Jamie Lokier
2003-05-06 21:38 ` Alan Cox
2003-05-08 21:36 ` Pavel Machek
2003-05-06 19:17 ` Eric W. Biederman
2003-05-06 21:55 ` Jamie Lokier
2003-05-06 22:21 ` David Schwartz
2003-05-07 8:21 ` Eric W. Biederman
2003-05-07 14:25 ` Valdis.Kletnieks
2003-05-07 14:31 ` Jamie Lokier
2003-05-07 15:50 ` Eric W. Biederman
2003-05-06 20:43 ` Pavel Machek
2003-05-06 22:18 ` Jamie Lokier
2003-05-06 21:31 ` Alan Cox
2003-05-06 22:48 ` Jamie Lokier
2003-05-07 12:20 ` Alan Cox
2003-05-07 14:26 ` Jamie Lokier
2003-05-07 15:18 ` Pavel Machek
2003-05-08 11:11 ` Krzysztof Halasa
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=m1issm8zju.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Riley@Williams.Name \
--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 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.