From: Stefan Smietanowski <stesmi@stesmi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Pramod Srinivasan <pramods@gmail.com>,
David Weinehall <tao@acc.umu.se>,
linux-kernel@vger.kernel.org
Subject: Re: GPL issues
Date: Wed, 12 Apr 2006 11:22:22 +0200 [thread overview]
Message-ID: <443CC6CE.6070102@stesmi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0604121057360.12544@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
Jan Engelhardt wrote:
> <obligatory_ianal_marker>
>
>>Suppose I use the linux-vrf patch for the kernel that is freely
>>available and use the extended setsocket options such as SO_VRF in an
>>application, do I have to release my application under GPL since I am
>>using a facility in the kernel that a standard linux kernel does not
>>provide?
>>
>
>
> If vrf has no other uses besides your proprietary application, I'd shudder.
So in order for you not to shudder the vrf people have to write a GPL'd
program or convince someone else to write one?
That sounds .. really odd.
Or more to the point, someone ONLY writes kernelmode stuff, doesn't
touch userspace at all. A proprietary app shows up that uses it,
and all of a sudden this guy's kernelmode whatever is disliked
cause noone wrote any GPL'd program for it?
That's almost forcing the person who wrote the kernel part to write
a GPL'd program JUST because there is a proprietary program using
his stuff - and THAT is insane.
// Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2006-04-12 9:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 7:01 GPL issues Pramod Srinivasan
2006-04-12 8:16 ` David Weinehall
2006-04-12 9:06 ` Jan Engelhardt
2006-04-12 9:22 ` Stefan Smietanowski [this message]
2006-04-12 9:40 ` Martin Mares
2006-04-12 9:28 ` Alan Cox
2006-04-14 11:39 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 6:31 Ramakanth Gunuganti
2006-04-11 8:42 ` Jesper Juhl
2006-04-11 10:51 ` Martin Mares
2006-04-11 17:46 ` Horst von Brand
2006-04-11 13:49 ` Kyle Moffett
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 16:07 ` linux-os (Dick Johnson)
2006-04-11 16:29 ` Stefan Smietanowski
2006-04-11 16:13 ` Adrian Bunk
2006-04-11 16:15 ` Kyle Moffett
2006-04-11 16:23 ` Dave Neuer
2006-04-11 18:58 ` Jan Engelhardt
2006-04-14 11:39 ` David Schwartz
2006-04-14 14:54 ` linux-os (Dick Johnson)
2006-04-14 17:50 ` David Weinehall
2006-04-14 18:56 ` David Schwartz
2006-04-15 11:55 ` Alan Cox
2006-04-15 13:04 ` Steven Rostedt
2006-04-15 18:49 ` David Schwartz
2006-04-11 15:49 ` Ramakanth Gunuganti
2006-04-11 23:06 ` David Weinehall
2006-04-12 2:38 ` Joshua Hudson
2006-04-12 3:18 ` Mark Lord
2006-04-12 5:00 ` Kyle Moffett
2006-04-12 5:31 ` Arjan van de Ven
2006-04-12 5:45 ` jdow
2006-04-12 6:01 ` David Weinehall
2006-04-12 6:26 ` jdow
2006-04-12 9:13 ` Stefan Smietanowski
2006-04-12 11:33 ` Olivier Galibert
2006-04-12 14:51 ` Arjan van de Ven
2006-04-13 22:07 ` Mark Lord
2006-04-15 11:14 ` Arjan van de Ven
2006-04-13 22:17 ` Mark Lord
2006-04-15 11:15 ` Arjan van de Ven
2006-04-11 23:12 ` 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=443CC6CE.6070102@stesmi.com \
--to=stesmi@stesmi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pramods@gmail.com \
--cc=tao@acc.umu.se \
/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