From: "Henning P. Schmiedehausen" <hps@tanstaafl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: What is 2.4 Linux networking performance like compared to BSD?
Date: Fri, 2 Mar 2001 09:02:13 +0000 (UTC) [thread overview]
Message-ID: <97nnil$dn9$1@forge.intermeta.de> (raw)
In-Reply-To: <Pine.A41.4.33.0102282123180.68876-100000@aix09.unm.edu>, <3A9E96A6.41D725A3@namesys.com>
reiser@namesys.com (Hans Reiser) writes:
> If I can't get information about BSD v. Linux 2.4 networking code,
> then reiserfs has to get ported to BSD which will be both nice and a
> pain to do.
So we would get dual-licensed ReiserFS (BSD and GPL)?
Are you aware of the legal implications, making your currently
GPL-only code BSD-licensed (status of third party patches for the GPL
code and so on)?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
next prev parent reply other threads:[~2001-03-02 9:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 23:26 What is 2.4 Linux networking performance like compared to BSD? Hans Reiser
2001-03-01 4:25 ` Todd
2001-03-01 16:03 ` Hans Reiser
2001-03-01 17:04 ` Nathan Dabney
2001-03-01 18:36 ` Hans Reiser
2001-03-01 19:16 ` David Weinehall
2001-03-01 19:19 ` Alan Cox
2001-03-02 4:57 ` David L. Parsley
2001-03-01 19:22 ` Nathan Dabney
2001-03-02 9:02 ` Henning P. Schmiedehausen [this message]
2001-03-02 13:00 ` Gregory Maxwell
2001-03-05 8:09 ` Re[2]: " linuxjob
2001-03-02 14:28 ` Alan Cox
2001-03-01 17:17 ` God
2001-03-01 18:04 ` Lincoln Dale
2001-03-01 10:32 ` Alan Cox
2001-03-01 17:15 ` James Lewis Nance
2001-03-01 18:38 ` Hans Reiser
2001-03-01 19:25 ` Tigran Aivazian
2001-03-01 23:30 ` Hans Reiser
2001-03-01 20:26 ` kuznet
2001-03-02 3:05 ` linuxjob
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='97nnil$dn9$1@forge.intermeta.de' \
--to=hps@tanstaafl.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