From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Suggestions for backup scheme?
Date: Wed, 7 Feb 2024 21:59:38 +0000 [thread overview]
Message-ID: <838555ad-25d5-4c07-876a-9adcaeae4763@youngman.org.uk> (raw)
In-Reply-To: <2327417.ElGaqSPkdT@iris>
On 07/02/2024 11:11, J. Roeleveld wrote:
> On Tuesday, February 6, 2024 9:27:35 PM CET Wols Lists wrote:
>> On 06/02/2024 13:12, J. Roeleveld wrote:
>>>> Clearly Oracle likes this state of affairs. Either that, or they are
>>>> encumbered in some way from just GPLing the ZFS code. Since they on
>>>> paper own the code for both projects it seems crazy to me that this
>>>> situation persists.
>>>
>>> GPL is not necessarily the best license for releasing code. I've got some
>>> private projects that I could publish. But before I do that, I'd have to
>>> decide on a License. I would prefer something other than GPL.
>>
>> Okay. What do you want to achieve. Let's just lump licences into two
>> categories to start with and ask the question "Who do you want to free?"
>
> I want my code to be usable by anyone, but don't want anyone to fork it and
> start making money off of it without giving me a fair share.
Okay, that instantly says you want a copyleft licence. So you're stuck
with a GPL-style licence, and if they want to include it in a commercial
closed source product, they need to come back to you and dual licence it.
Personally, I'd go the MPL2 route, but that's my choice. It might not
suit you. But to achieve what you want, you need a copyleft, GPL-style
licence.
>
>> If that sounds weird, it's because both Copyleft and Permissive claim to
>> be free, but have completely different target audiences. Once you've
>> answered that question, it'll make choosing a licence so much easier.
>>
>> GPL gives freedom to the END USER. It's intended to protect the users of
>> your program from being held to ransom.
>
> That's not how the kernel devs handle the GPL. They use it to remove choice
> from the end user (me) to use what I want (ZFS).
> And it's that which I don't like about the GPL.
>
No. That's Oracle's fault. The kernel devs can't include ZFS in linux,
because Oracle (or rather Sun, at the time, I believe) deliberately
*designed* the ZFS licence to be incompatible with the GPL.
After all, there's nothing stopping *you* from combining Linux and ZFS,
it's just that somebody else can't do that for you, and then give you
the resulting binary.
At the end of the day, if someone wants to be an arsehole, there's not a
lot you can do to stop them, and with ZFS that honour apparently goes to
Sun.
Cheers,
Wol
next prev parent reply other threads:[~2024-02-07 21:59 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 18:15 [gentoo-user] Suggestions for backup scheme? Grant Edwards
2024-01-30 18:47 ` Thelma
2024-01-30 19:29 ` [gentoo-user] " Grant Edwards
2024-01-30 18:54 ` [gentoo-user] " Michael
2024-01-30 19:32 ` [gentoo-user] " Grant Edwards
2024-01-30 19:19 ` [gentoo-user] " Rich Freeman
2024-01-30 19:43 ` [gentoo-user] " Grant Edwards
2024-01-30 20:08 ` [gentoo-user] " Wol
2024-01-30 20:15 ` Rich Freeman
2024-01-30 20:38 ` [gentoo-user] " Grant Edwards
2024-01-31 8:14 ` gentoo-user
2024-01-31 11:45 ` John Covici
2024-01-31 13:01 ` Rich Freeman
2024-01-31 15:50 ` Grant Edwards
2024-01-31 17:40 ` Thelma
2024-01-31 17:56 ` Rich Freeman
2024-01-31 18:42 ` Wols Lists
2024-01-31 21:30 ` Rich Freeman
2024-02-01 10:16 ` Michael
2024-02-05 12:55 ` J. Roeleveld
2024-02-05 13:35 ` Rich Freeman
2024-02-06 13:12 ` J. Roeleveld
2024-02-06 20:27 ` Wols Lists
2024-02-07 11:11 ` J. Roeleveld
2024-02-07 21:59 ` Wols Lists [this message]
2024-02-08 6:32 ` J. Roeleveld
2024-02-08 17:36 ` Wols Lists
2024-02-09 12:53 ` J. Roeleveld
2024-02-06 15:38 ` Grant Edwards
2024-02-06 16:13 ` J. Roeleveld
2024-02-06 17:22 ` Grant Edwards
2024-02-07 11:21 ` J. Roeleveld
2024-01-31 18:00 ` Grant Edwards
2024-02-02 23:39 ` Grant Edwards
2024-02-02 23:58 ` Mark Knecht
2024-02-03 16:02 ` Grant Edwards
2024-02-03 17:05 ` Wol
2024-02-04 6:24 ` Grant Edwards
2024-02-04 9:59 ` Wols Lists
2024-02-04 15:48 ` Grant Edwards
2024-02-05 8:28 ` Wols Lists
2024-02-06 15:35 ` Grant Edwards
2024-02-06 16:19 ` J. Roeleveld
2024-02-06 17:29 ` Grant Edwards
2024-02-07 11:04 ` J. Roeleveld
2024-02-06 23:17 ` Wols Lists
2024-02-07 11:07 ` J. Roeleveld
2024-02-07 21:50 ` Wols Lists
2024-02-08 6:38 ` J. Roeleveld
2024-02-08 17:44 ` Wols Lists
2024-02-09 12:57 ` J. Roeleveld
2024-02-09 15:48 ` Wols Lists
2024-02-09 17:11 ` Peter Humphrey
2024-02-06 20:49 ` Wols Lists
2024-02-03 13:02 ` Michael
2024-02-03 16:15 ` Grant Edwards
2024-02-03 17:32 ` Rich Freeman
2024-02-03 18:10 ` Michael
2024-02-05 12:48 ` J. Roeleveld
2024-01-31 15:38 ` Grant Edwards
2024-02-04 10:54 ` [gentoo-user] " Paul Ezvan
2024-02-07 22:36 ` Frank Steinmetzger
2024-02-08 5:26 ` William Kenworthy
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=838555ad-25d5-4c07-876a-9adcaeae4763@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.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