all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: Morgan Arnold <morgan.arnold@proton.me>, guix-devel@gnu.org
Subject: Re: Status of ZFS support on Guix
Date: Wed, 02 Oct 2024 17:18:50 -0700	[thread overview]
Message-ID: <87ikuahvpt.fsf@meson> (raw)
In-Reply-To: <Mhb6sWzDS2N_9G3yl020kKXIWEoEvRR-Y1NcTZb4k8mVJRKKsDUB7dvIpg6FbZatgASiMXGLoy9EHspoKgLlG2LsM4CRlH6VIW7-GmAHMuI=@protonmail.com>

Hi Kaelyn, Morgan,

Kaelyn <kaelyn.alexi@protonmail.com> writes:

> On Tuesday, October 1st, 2024 at 1:23 PM, Morgan Arnold 
> <morgan.arnold@proton.me> wrote:
>
> I'd love to know where any opposition may be at as well. At this 
> point
> I have a private channel which actually replaces much of the
> bootloader and initrd functionality (in part to support ZFS in 
> the
> initrd using https://issues.guix.gnu.org/55231). In the past 
> year, I
> actually took advantage of having basically replicated much of 
> the
> initrd functionality in my channel to create a simple bootloader 
> based
> on the Linux kernel (with the EFI stubloader) and a custom 
> initrd that
> uses kexec to boot the actual system. It still needs a lot of 
> polish,
> but has been good enough that combined with a few other small 
> hacks
> and workarounds, I have several systems now booting with ZFS 
> roots
> (some unencrypted, some using native encryption). I have done 
> little
> to upstream most of it, or even to share what I've done, because 
> of
> the seeming resistance to ZFS.
>

I don’t think there’s resistance to ZFS.  I do think there are 
some legitimate open questions around licensing[1], but the main 
issue seems to be that the contributor of #45692 chose to express 
their frustration with the slow pace of Guix patch review[2] in 
counterproductive and borderline abusive ways[3][4].

Personally, I’d very much like to see improved support for ZFS in 
Guix.  I have one machine with a cobbled-together Guix ZFS setup, 
but proper support is a blocker for moving my primary ZFS-using 
system off Debian.

Thanks,

  — Ian

[1]: https://issues.guix.gnu.org/45692#75
[2]: Which I *extremely* sympathize with.
[3]: https://issues.guix.gnu.org/45692#72
[4]: https://issues.guix.gnu.org/45692#78


  reply	other threads:[~2024-10-03  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-01 20:23 Status of ZFS support on Guix Morgan Arnold
2024-10-02 22:07 ` Kaelyn
2024-10-03  0:18   ` Ian Eure [this message]
2024-10-03 17:23     ` Kaelyn

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=87ikuahvpt.fsf@meson \
    --to=ian@retrospec.tv \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=morgan.arnold@proton.me \
    /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.