From: 宋文武 <iyzsong@outlook.com>
To: raid5atemyhomework <raid5atemyhomework@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, 45692@debbugs.gnu.org
Subject: Re: ZFS on Guix, again
Date: Sat, 20 Feb 2021 19:44:34 +0800 [thread overview]
Message-ID: <OS3P286MB066003E371477FEA2063411EA3839@OS3P286MB0660.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ZoNE4PohkbyOLRF1wZSubnkSSDbNh3dUZAO-n5RXe6yZ3wx8xZvbEiHBU9B5D1i_tpdCrHBpjE-8Jy1pz5i9E-rh5X6IjsZQ0_1jmUJgp_s=@protonmail.com> (raid5atemyhomework@protonmail.com's message of "Sat, 20 Feb 2021 08:48:04 +0000")
raid5atemyhomework <raid5atemyhomework@protonmail.com> writes:
> Hi guix-devel,
>
> I had some questions on the big ZFS guix bugpatches a week ago, and
> did not find any response, so I am back here pestering everyone.
Hello, thank you for working on ZFS for guix!
>
> [...]
> There are two alternatives:
>
> * Go with what I already proposed which I think is more general-purpose and cleaner (there is a separate service type that accepts symbols, and a separate service type that accepts `<file-system>` records, and the latter just extends the former).
> * Don't make a separate service type, but now we need to add some kind of `fstab?` field to `file-system` so that the ZFS shepherd service that mounts ZFS file systems will not be included in the `/etc/fstab`.
>
> I think overall that having lots of tiny service types that are then
> combined together fits the functional design of Guix better. So I
> would strongly propose my original design rather than hacks on top of
> `file-system-service-type`.
Well, I think the 'file-system-service-type' should handle all file
systems related configurations, but my opion is not strong. Waiting
ludo to decide...
next prev parent reply other threads:[~2021-02-20 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 8:48 ZFS on Guix, again raid5atemyhomework
2021-02-20 11:44 ` 宋文武 [this message]
2021-02-22 8:57 ` Ludovic Courtès
2021-02-23 1:11 ` raid5atemyhomework
2021-02-25 5:08 ` raid5atemyhomework
2021-03-09 2:34 ` raid5atemyhomework
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=OS3P286MB066003E371477FEA2063411EA3839@OS3P286MB0660.JPNP286.PROD.OUTLOOK.COM \
--to=iyzsong@outlook.com \
--cc=45692@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=raid5atemyhomework@protonmail.com \
/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.