From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Slavcho Nikolov <snikolov@okena.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: feature request - why not make netif_rx() a pointer?
Date: Wed, 23 Oct 2002 10:03:44 -0400 [thread overview]
Message-ID: <3DB6AC40.20007@nortelnetworks.com> (raw)
In-Reply-To: 004c01c27a99$927b8a30$800a140a@SLNW2K
Slavcho Nikolov wrote:
> As for GPL, I hope that commercial enterprises be allowed to utilize
> business models
> which do not necessarily consist in providing services around free software.
> The more replaceable hooks you provide to filesystems and network stacks,
> the better.
I don't think you understand the nature of the GPL and linux development.
The kernel developers do not have any obligation to anything other than
technical excellence. You're getting a highly optimized operating
system *at no financial cost*. In return, the community requires that
certain types of modifications be made publicly available.
If you want to replace the messaging code, make a GPL'd kernel patch and
make it available to your clients (of course they can then publish it
all over the place if they so desire). If those terms are not
acceptable, there's always BSD.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2002-10-23 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 0:39 feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 13:39 ` Slavcho Nikolov
2002-10-23 14:03 ` Chris Friesen [this message]
2002-10-23 16:23 ` over&out (Re: feature request - why not make netif_rx() a pointer?) Slavcho Nikolov
2002-10-23 22:59 ` jw schultz
2002-10-24 6:25 ` Gilad Ben-Yossef
2002-10-24 7:08 ` Ben Greear
2002-10-25 11:50 ` Adrian Bunk
2002-10-23 16:48 ` feature request - why not make netif_rx() a pointer? Jean Tourrilhes
2002-10-23 17:27 ` Ben Greear
2002-10-24 4:13 ` David S. Miller
2002-10-24 9:28 ` Henning P. Schmiedehausen
2002-10-24 10:15 ` David S. Miller
2002-10-24 11:01 ` Henning Schmiedehausen
2002-10-24 13:30 ` Slavcho Nikolov
2002-10-24 13:46 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 21:01 Slavcho Nikolov
2002-10-22 21:15 ` Matti Aarnio
2002-10-22 22:42 ` David S. Miller
2002-10-22 23:16 ` Ben Greear
2002-10-22 23:29 ` Jeff Garzik
2002-10-23 15:16 ` Henning P. Schmiedehausen
2002-10-23 16:11 ` Alan Cox
2002-10-23 16:26 ` Henning P. Schmiedehausen
2002-10-22 21:30 ` Alan Cox
2002-10-22 22:40 ` David S. Miller
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=3DB6AC40.20007@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=snikolov@okena.com \
/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;
as well as URLs for NNTP newsgroup(s).