From: Bernd Petrovitsch <bernd@tuxoid.at>
To: Stephan von Krawczynski <skraw.ml@ithnet.com>
Cc: linux-kernel@vger.kernel.org, bruce@perens.com
Subject: Re: General Discussion about GPLness
Date: Mon, 24 Feb 2020 00:46:03 +0100 [thread overview]
Message-ID: <7896b0b9-c12e-5327-f531-95097cf04eca@tuxoid.at> (raw)
In-Reply-To: <20200223214757.5adf49e4@ithnet.com>
Hi all!
On 23/02/2020 21:47, Stephan von Krawczynski wrote:
[...]
> I do understand why you cannot enter a discussion with your real name, as most
I ignore folks who don't use their real name - this is since Usenet
times an indication for a troll ...
> of your input is of zero quality - and below.
[...]
> But our story is
> about kernel modules, something everybody is free to write and publish, with a
... publish implicitly with a GPLv2 or compatible license ...
> defined and open interface for interaction. No kernel code is modified in that
And that's a point which is completely wrong: the only *defined*
interface of the kernel is sys-calls, /proc and similar. And all of this
is from user-space to kernel-space and back.
There is no (and never was) a "defined interface" within the kernel
(inter-operating in kernel space) in any direction simply because the
kernel-internal (infra)structure changes more or less constantly - some
may call that evolution;-)
And I don't get what an "open interface" here couls seriously mean. You
surely don't want to call the list of the GPL_EXPORTed C functions
(which may change from one kernel version to the next) an "open
interface" (whatever that should suggest).
At most the list of GPL_EXPORTed C functions is a de-facto interface and
that may change from one git-commit to the next.
> sense. But you fail to understand that.
> Hopefully others here do. I do not expect them to stand up and jump into a
> discussion where you are a part of. But I hope people start to think about it
And you are barking up the wrong tree. The discussion has to happen in
the ZFS-world so that they fix their license if they want to interface
with any GPL software (without sys-calls etc. in between - WTF it works
via FUSE) like they seen to do now.
And no, I'm not a lawyer so I won't comment more on the law-aspects -
the above is my short summary of discussions hereover about license
clashes etc. over the last decades ...
[ Full quote deleted - pls do not top-post]
MfG,
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2020-02-24 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 11:03 General Discussion about GPLness whywontyousue
2020-02-23 12:33 ` Stephan von Krawczynski
2020-02-23 12:56 ` whywontyousue
2020-02-23 14:39 ` Stephan von Krawczynski
2020-02-23 16:24 ` whywontyousue
2020-02-23 20:47 ` Stephan von Krawczynski
2020-02-23 23:46 ` Bernd Petrovitsch [this message]
2020-02-24 10:29 ` Stephan von Krawczynski
2020-02-25 13:33 ` Bernd Petrovitsch
2020-02-24 7:46 ` whywontyousue
2020-02-24 14:01 ` Stephan von Krawczynski
2020-02-25 3:56 ` whywontyousue
-- strict thread matches above, loose matches on Subject: below --
2020-02-23 10:14 Stephan von Krawczynski
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=7896b0b9-c12e-5327-f531-95097cf04eca@tuxoid.at \
--to=bernd@tuxoid.at \
--cc=bruce@perens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw.ml@ithnet.com \
/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).