public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Suggestions for backup scheme?
Date: Thu, 8 Feb 2024 17:36:56 +0000	[thread overview]
Message-ID: <9424ee8e-a300-4f14-83d7-1d81eddcf67b@youngman.org.uk> (raw)
In-Reply-To: <12379239.O9o76ZdvQC@iris>

On 08/02/2024 06:32, J. Roeleveld wrote:
>> 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.

> I'll have a look at that one.

Basically, each individual source file is copyleft, but not the work as 
a whole. So if anybody copies/modifies YOUR work, they have to 
distribute your work with their binary, but this requirement does not 
extend to everyone else's work.
> 
> Maybe not included fully into the kernel, but there is nothing preventing it
> to be packaged with a Linux distribution.
> It's just the hostility from Linus Torvalds and Greg Kroah-Hartman against ZFS
> causing the issues.
> 
> See the following post for a clear description (much better written than I
> can):
> https://eerielinux.wordpress.com/2019/01/28/zfs-and-gpl-terror-how-much-freedom-is-there-in-linux/
> 
> Especially the lkml thread linked from there:
> https://lore.kernel.org/lkml/20190110182413.GA6932@kroah.com/
> 
>> 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.

> Linux (kernel) and ZFS can't be merged. Fine.

But they can.

> But, Linux (the OS, as in, kernel + userspace) and ZFS can be merged legally.
> 
Likewise here, they can.

The problem is, the BINARY can NOT be distributed. And the problem is 
the ZFS licence, not Linux.

What Linus, and the kernel devs, and that crowd *think* is irrelevant. 
What matters is what SUSE, and Red Hat, and Canonical et al think. And 
if they're not prepared to take the risk of distributing the kernel with 
ZFS built in, because they think it's a legal minefield, then that's 
THEIR decision.

That problem doesn't apply to gentoo, because it distributes the linux 
kernel and ZFS separately, and combines them ON THE USER'S MACHINE. But 
the big distros are not prepared to take the risk of combining linux and 
ZFS, and distributing the resulting *derived* *work*.

Cheers,
Wol


  reply	other threads:[~2024-02-08 17:37 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
2024-02-08  6:32                                 ` J. Roeleveld
2024-02-08 17:36                                   ` Wols Lists [this message]
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=9424ee8e-a300-4f14-83d7-1d81eddcf67b@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