From: Matt Mackall <mpm@selenic.com>
To: John Sage <jsage@finchhaven.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Parentage of BPF code in Linux
Date: Thu, 1 Jul 2004 13:43:55 -0500 [thread overview]
Message-ID: <20040701184354.GJ5414@waste.org> (raw)
In-Reply-To: <20040701181002.GG6445@sparky.finchhaven.net>
On Thu, Jul 01, 2004 at 11:10:02AM -0700, John Sage wrote:
> [Non-subscriber: please cc on replies]
>
> WRT to the SCO/IBM/Linux imbroglio, there was an interesting assertion
> made on the Yahoo! Finance message board for SCOX, and I wondered if
> anyone could shed some light.
>
> The assertion is this:
>
> "...among other things, the Berkeley Packet Filter code, which was
> written by an independent developer for the Missouri School District,
> licensed under the BSD license terms that never was part of SysV at
> any time..."
There's a from-scratch reimplementation of BPF in Linux (called Linux
Socket Filter) by Jay Schulist in net/core/filter.c. And he appears to
have worked for the _Wisconsin_ school district at the time. A Google
search on "schulist filter wisconsin" reveals:
Jay Schulist, a senior software engineer with Pleasanton,
California's Bivio Networks says he wrote the 500 lines of code in
1997 as part of a volunteer project for the Stevens Point Area
Catholic Schools in Wisconsin. "I used it for helping a local school
district in my home town to connect their old Apple Macintosh machines
to the Internet," he said.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-07-01 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 18:10 Parentage of BPF code in Linux John Sage
2004-07-01 18:43 ` Matt Mackall [this message]
2004-07-01 18:55 ` John Sage
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=20040701184354.GJ5414@waste.org \
--to=mpm@selenic.com \
--cc=jsage@finchhaven.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).