From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org, raid5atemyhomework@protonmail.com,
Domagoj Stolfa <ds815@gmx.com>
Subject: Re: ZFS part of Guix? RFC?
Date: Fri, 26 Nov 2021 21:02:16 +0100 [thread overview]
Message-ID: <20211126210216.15e408dc@primarylaptop.localdomain> (raw)
In-Reply-To: <20211126162804.726829e3@primarylaptop.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Fri, 26 Nov 2021 16:28:04 +0100
Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> wrote:
> But I wonder if a license that forbid binary redistribution would
> still be considered free or not.
When we'll have more infos on if that is free or if we consider it as
free until proven otherwise, we still have two remaining issues to deal
with:
- On some architectures (for instance i686) the kernel module doesn't
build. Should we disable the module? Add support for these
architectures? Or disable zfs as a dependency of Gnome?
- Images with the zfs modules won't be redistributable. So if we keep
the ability to build the zfs module, would it be possible to add
opt-in or opt-out settings to make sure that the images are still
redistributable without violating the GPL?
Or will all users always need to use transformations for that?
Here's the build error I have with i686:
> make -C
> /gnu/store/c5n1drdj3j780r6yxnqfldifkmwdz01d-linux-libre-module-builder-5.14.21/lib/modules/build
> M=`pwd` CONFIG_ZFS=m modules make[3]: Entering directory
> '/gnu/store/c5n1drdj3j780r6yxnqfldifkmwdz01d-linux-libre-module-builder-5.14.21/lib/modules/build'
> arch/x86/Makefile:78: arch/x86/Makefile_32.cpu: No such file or
> directory make[3]: *** No rule to make target
> 'arch/x86/Makefile_32.cpu'. Stop.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-11-26 20:02 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 19:33 Effectively force all GNOME users to locally compile ZFS? Mark H Weaver
2021-07-03 19:53 ` Tobias Geerinckx-Rice
2021-07-05 9:53 ` Ludovic Courtès
2021-07-05 17:48 ` Mark H Weaver
2021-07-07 11:59 ` Tobias Geerinckx-Rice
2021-07-11 20:07 ` Mark H Weaver
2021-07-07 11:34 ` Tobias Geerinckx-Rice
2021-07-03 20:01 ` Maxime Devos
2021-07-03 20:16 ` Tobias Geerinckx-Rice
2021-07-03 20:46 ` Domagoj Stolfa
2021-07-03 21:38 ` Tobias Geerinckx-Rice
2021-07-03 21:53 ` Tobias Geerinckx-Rice
2021-11-20 1:09 ` Denis 'GNUtoo' Carikli
2021-11-20 2:34 ` Tobias Geerinckx-Rice
2021-11-21 1:33 ` Denis 'GNUtoo' Carikli
2021-11-21 10:54 ` ZFS part of Guix? RFC? (Re: Effectively force all GNOME users to locally compile ZFS?) pelzflorian (Florian Pelz)
2021-11-22 16:50 ` Denis 'GNUtoo' Carikli
2021-11-22 18:10 ` pelzflorian (Florian Pelz)
2021-11-23 16:37 ` Denis 'GNUtoo' Carikli
2021-11-23 17:29 ` Ludovic Courtès
2021-11-23 23:50 ` Denis 'GNUtoo' Carikli
2021-11-24 0:45 ` Denis 'GNUtoo' Carikli
2021-11-24 12:03 ` pelzflorian (Florian Pelz)
2021-11-24 12:32 ` pelzflorian (Florian Pelz)
2021-11-24 12:51 ` zimoun
2021-11-24 14:40 ` pelzflorian (Florian Pelz)
2021-11-24 20:25 ` zimoun
2021-11-24 13:33 ` Denis 'GNUtoo' Carikli
2021-11-24 20:02 ` ZFS part of Guix? RFC? Vagrant Cascadian
2021-11-26 15:28 ` Denis 'GNUtoo' Carikli
2021-11-26 20:02 ` Denis 'GNUtoo' Carikli [this message]
2021-11-26 20:34 ` Vagrant Cascadian
2021-11-27 15:19 ` Denis 'GNUtoo' Carikli
2021-11-30 15:22 ` raid5atemyhomework
2021-11-30 21:22 ` Denis 'GNUtoo' Carikli
2021-11-24 1:24 ` ZFS part of Guix? RFC? (Re: Effectively force all GNOME users to locally compile ZFS?) zimoun
2021-11-24 17:24 ` Leo Famulari
2021-11-21 22:18 ` Effectively force all GNOME users to locally compile ZFS? zimoun
2021-07-04 20:11 ` Mark H Weaver
2021-07-05 10:21 ` Giovanni Biscuolo
2021-07-05 17:59 ` Mark H Weaver
2021-07-07 12:20 ` Tobias Geerinckx-Rice
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=20211126210216.15e408dc@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=ds815@gmx.com \
--cc=guix-devel@gnu.org \
--cc=raid5atemyhomework@protonmail.com \
--cc=vagrant@debian.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.