From: drizzt.dourden@iname.com
To: LLX <llx@swissonline.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Module Licensing?
Date: Thu, 8 Nov 2001 01:36:25 +0100 [thread overview]
Message-ID: <20011108013625.A3316@menzoberrazan.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110311535250.2963-100000@imladris.surriel.com> <200110311831.f9VIVeR09294@mail.swissonline.ch>
In-Reply-To: <200110311831.f9VIVeR09294@mail.swissonline.ch>; from llx@swissonline.ch on Wed, Oct 31, 2001 at 07:31:40PM +0100
Decía LLX:
> > The irrelevance here is IYHO ... it may well be judged that
> > since these two portions of the work need each other in order
> > to function, the thing really is one work.
>
> a)
> vmware for linux needs a linux kernel to work. does that meen
> you whant to gpl it?
>
> b)
> you can write abstraction modules for different os's. and the
> non-gpl module works with all of them. so my module does not
> need the linux abstraction module it also works with the free-
> BSD module. the only #ifdef in my module will be around the
> module registration code. or i write a propriatary loader,
> so that even the same binary works for different os's
>
And you can use a big array with your binary code and made the source public:
/*
This code is GPL
*/
char *code={big array of code}
void do_somenthin(){
void (*fun) = code;
(*fun)();
}
(well, I dosn't remember the exact sintax of pointer to funtioncs but ... )
You can put the binary driver like "microcode", and GPL
Saludos
Drizzt
--
... 10 IF "LAS RANAS"="TIENEN PELO" THEN PRINT "Windows is good".
____________________________________________________________________________
Drizzt Do'Urden
drizzt.dourden@iname.com
next prev parent reply other threads:[~2001-11-08 0:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 3:46 Module Licensing? Kevin D. Wooten
2001-10-30 4:08 ` Ben Greear
2001-10-30 4:58 ` TimO
2001-10-30 5:10 ` Ben Greear
2001-10-30 7:24 ` Kevin D. Wooten
2001-10-30 17:27 ` Timur Tabi
2001-10-30 23:10 ` Alan Cox
2001-10-31 0:13 ` Timur Tabi
2001-10-31 0:25 ` Alan Cox
2001-10-31 16:53 ` Timur Tabi
2001-10-31 17:10 ` Rik van Riel
2001-10-31 17:22 ` Larry McVoy
2001-10-31 17:27 ` Rik van Riel
2001-10-31 18:34 ` Larry McVoy
2001-10-31 18:44 ` Rik van Riel
2001-10-31 18:53 ` Andreas Dilger
2001-10-31 20:08 ` Craig Milo Rogers
2001-10-31 17:32 ` dean gaudet
2001-10-31 19:55 ` [OT] " Craig Milo Rogers
2001-10-31 21:42 ` Cort Dougan
2001-10-31 23:47 ` Jamie Lokier
2001-10-31 23:54 ` Larry McVoy
2001-11-01 0:10 ` Jamie Lokier
2001-11-01 0:43 ` Alan Cox
2001-11-01 23:52 ` n0ano
2001-10-31 17:29 ` Timur Tabi
2001-10-31 17:37 ` Rik van Riel
2001-10-31 18:31 ` LLX
2001-11-08 0:36 ` drizzt.dourden [this message]
2001-11-08 12:41 ` Alan Cox
2001-11-08 13:19 ` Drizzt Do'Urden
2001-11-08 14:53 ` Module Licensing? (thinking a little more) Drizzt Do'Urden
2001-11-08 15:56 ` Doug McNaught
2001-11-08 17:00 ` Drizzt Do'Urden
2001-11-08 17:18 ` Russell King
2001-11-08 17:47 ` Drizzt Do'Urden
2001-11-09 7:50 ` Stefan Smietanowski
2001-11-10 18:09 ` QuoteMstr - Danny Colascione
2001-11-08 17:29 ` Doug McNaught
2001-11-08 19:28 ` drizzt.dourden
2001-10-31 20:15 ` Module Licensing? Craig Milo Rogers
2001-10-31 19:49 ` Craig Milo Rogers
2001-11-04 3:37 ` Albert D. Cahalan
2001-10-31 17:11 ` Alan Cox
2001-11-05 4:40 ` [file interface] " Roger Larsson
2001-10-30 9:22 ` Alan Cox
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=20011108013625.A3316@menzoberrazan.dhis.org \
--to=drizzt.dourden@iname.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llx@swissonline.ch \
/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).