From: Keith Owens <kaos@ocs.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Running ia64 2.4.17 kernel on RedHat 7.2 and problems with LoadModule: "scanpci
Date: Fri, 22 Mar 2002 01:07:28 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905324@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905319@msgid-missing>
On Thu, 21 Mar 2002 16:55:58 -0800,
Piet/Pete Delaney <piet@sgi.com> wrote:
>What about modules that aren't distributed with the kernel but
>are released as objects (perhaps src) to be linked into the kernel
>by the customer. For example, something like kdb. Your saying a company
>that distributes kdb like objects that the a sustomer links into the
>kernel must release the src of the objects under the GPL license.
Yes. Statically linking an object with the kernel requires GPL source,
even if the object is distributed separately from the kernel. The act
of distributing and statically linking trips the GPL virus.
>So for you to release something like kdb sourceless you would have to
>link it into the kernel as a module and make it useless for early startup.
Yes, but there is no way for kdb to be released without source, it is
far too dependent on the kernel. I would never contemplate making kdb
binary only.
... IANAL, speaking only for myself, blah, blah, blah
next prev parent reply other threads:[~2002-03-22 1:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 0:27 [Linux-ia64] Re: Running ia64 2.4.17 kernel on RedHat 7.2 and problems with LoadModule: "scanpci" wh Keith Owens
2002-03-22 0:55 ` [Linux-ia64] Re: Running ia64 2.4.17 kernel on RedHat 7.2 and problems with LoadModule: "scanpci Piet/Pete Delaney
2002-03-22 1:07 ` Keith Owens [this message]
2002-03-22 5:18 ` [Linux-ia64] Re: Running ia64 2.4.17 kernel on RedHat 7.2 and problems with LoadModule: "scanpci" wh Piet/Pete Delaney
2002-03-22 16:59 ` [Linux-ia64] Re: Running ia64 2.4.17 kernel on RedHat 7.2 and Luck, Tony
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=marc-linux-ia64-105590701905324@msgid-missing \
--to=kaos@ocs.com.au \
--cc=linux-ia64@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