This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: SystemTap License
- From: Arkady <arkady dot miasnikov at gmail dot com>
- To: Daniel Doron <danielmeirdoron at gmail dot com>
- Cc: systemtap at sourceware dot org
- Date: Mon, 13 Feb 2017 15:03:12 +0200
- Subject: Re: SystemTap License
- Authentication-results: sourceware.org; auth=none
- References: <CAFwN=+zVB5RUZ5oJ0LRARpgGN=ru17-5AhynVFGL17j46VfGbQ@mail.gmail.com>
Probably this is relevant
The “System Libraries” of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
“Major Component”, in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
On Mon, Feb 13, 2017 at 2:39 PM, Daniel Doron <danielmeirdoron@gmail.com> wrote:
> Hi,
>
> I looked through the mailing list archives but could not find a
> straight up answer.
> If using SystemTap in a commercial application, i.e. use systemtap to
> create the kernel module, does the company have to publish the
> SystemTap scripts used to create the kernel module when selling the
> commercial product?
>
> I read the wikipedia entry for GPL but still can't get a straight up
> answer...(https://en.wikipedia.org/wiki/GNU_General_Public_License#Terms_and_conditions)
>
> I would appreciate if someone can point me to a simple document
> explaining this vis-a-vis SystemTap.
>
> Daniel.