lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190121133044.28b6194b@ithnet.com>
Date:   Mon, 21 Jan 2019 13:30:44 +0100
From:   Stephan von Krawczynski <skraw@...net.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Rene Schickbauer <cavac@...ac.at>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        "Hutter, Tony" <hutter2@...l.gov>,
        Marc Dionne <marc.c.dionne@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "x86@...nel.org" <x86@...nel.org>
Subject: Re: x86/fpu: Don't export __kernel_fpu_{begin,end}()

On Tue, 15 Jan 2019 14:42:21 +0100
Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:

> On Tue, Jan 15, 2019 at 02:01:48PM +0100, Rene Schickbauer wrote:
> > To be frank, your argument, which boils down to "GPL is the only correct
> > open source license", makes me ashamed to have been advocating people
> > switching to Linux. This is exactly the kind of argument that made me
> > switch away from closed source operating systems like Windows, only then
> > it was Steve Ballmer using it against open source.  
> 
> What?
> 
> No, my argument is, "If you want to interact directly with Linux kernel
> code in kernel-space, then you have to abide by it's license, which is
> GPLv2".  That's it.  If you wish to use open source code by another
> license, wonderful, I'm not telling you what you can, and can not do,
> but please, do not violate the license of the code I contributed under
> GPLv2.
> 
> ZFS could be the best filesystem ever to grace this planet, that's
> fantastic, but given that the creators of that code placed it under a
> license that was specifically designed to not be compatible with Linux
> to prevent it from ever being used on Linux, well, you can see why I
> really don't care about it.  Why would I?
> 
> Those copyright owners (well license owner at this point in time) could
> fix this all tomorrow if they wanted to.  But they do not, so _THEY_ are
> the people you should be upset at.  Not at the Linux kernel developers
> who are giving you a kernel on which to use on your systems, for free,
> under the GPLv2.  Our position has always been very clear and upfront.
> And really, so has the ZFS license creators.  So why is anyone upset
> about all of this?  Nothing new has changed here with the license of
> anything.
> 
> best of luck!
> 
> greg k-h

Hi Greg,

I'd say this is in fact more a moral question than a technical or legal issue.
The true background is the simple question what the project (i.e. linux) is in
fact all about, is it about helping people with lower skills or is it about
ruling people. A company (more or less every company) is more about ruling,
its aim is to move people into buying and using its products. Me (and quite
surely Rene at least) think that the linux _community_ is more about helping
others and hopefully less about legal and technical ruling.
So your argument "go to the company XYZ and blame them" isn't really
targetting in the right direction - as long as you see linux still as a
community thing and not as a cash-cow company-alike. Maybe it would be a lot
better to think about why there are people using ZFS and not some GPLed fs
instead. Me too being a ZFS user I can tell you the simple fact that there is
no GPL fs with equal features and stability (eh BTRFS). In fact quite some of
us would probably use HAMMER2 (thanks Matt) instead if sure that it equals ZFS
in terms of stability, still not BTRFS. So all you promote currently is the fs
deficit linux actually still has (and had for years, or say decades). I doubt
that this is/was helping the linux community a lot...
Sure maintainers have to rule sometimes, but it only makes sense if you are
able to present a working equal alternative. If you have none (and in this case
you have no alternative to offer) you will only push people away from the
community and that's probably not the right path for a community maintainer.
-- 
Only my 2ct,
Stephan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ