From: Mike Fedyk <mfedyk@matchmail.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Bruce Ferrell <bferrell@baywinds.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: is it possible to have a kernel module with a BSD license?!
Date: Wed, 24 Dec 2003 14:11:14 -0800 [thread overview]
Message-ID: <20031224221114.GB6438@matchmail.com> (raw)
In-Reply-To: <1072282214.5267.0.camel@laptop.fenrus.com>
On Wed, Dec 24, 2003 at 05:10:14PM +0100, Arjan van de Ven wrote:
> On Wed, 2003-12-24 at 16:17, Bruce Ferrell wrote:
> > from the project announcement on freshmeat:
> >
> >
> > Dazuko 2.0.0-pre5 (Default)
> > by John Ogness - Tuesday, November 11th 2003 06:56 PST
> >
> > About:
> > This project provides a kernel module which provides 3rd-party
> > applications with an interface for file access control. It was
> > originally developed for on-access virus scanning. Other uses include a
> > file-access monitor/logger or external security implementations. It
> > operates by intercepting file-access calls and passing the file
> > information to a 3rd-party application. The 3rd-party application the
>
> I think you need to look further; the linux kernel portion sure is GPL
> ...
Then the wrapper can be GPL then and the rest BSD?
next prev parent reply other threads:[~2003-12-24 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 15:17 is it possible to have a kernel module with a BSD license?! Bruce Ferrell
2003-12-24 16:10 ` Arjan van de Ven
2003-12-24 22:11 ` Mike Fedyk [this message]
2003-12-24 23:12 ` Samuel Flory
2003-12-25 8:33 ` Arjan van de Ven
2003-12-24 22:01 ` Stan Bubrouski
2003-12-24 22:10 ` Mike Fedyk
2003-12-24 23:34 ` David Lang
2003-12-26 20:14 ` Samuel Flory
2003-12-27 14:51 ` Helge Hafting
2003-12-28 15:27 ` Ryan Anderson
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=20031224221114.GB6438@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=arjanv@redhat.com \
--cc=bferrell@baywinds.org \
--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.