all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: raid5atemyhomework <raid5atemyhomework@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: ZFS on Guix, again
Date: Mon, 22 Feb 2021 09:57:12 +0100	[thread overview]
Message-ID: <87mtvweazb.fsf@gnu.org> (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")

Hi,

Sorry for the delay; this isn’t as simple as it looks!

I agree with 宋文武 regarding ‘file-system-service-type’.

raid5atemyhomework <raid5atemyhomework@protonmail.com> skribis:

> However, for the case where the user expects the "typical" ZFS style of managing file systems, we need to mount all the ZFS file systems and ensure that they aer all already mounted by the time `file-systems` Shepherd service is started.  This means we need to be able to extend the `requirement` of the `file-systems` Shepherd service.  And we need to do that without putting any extra `/etc/fstab` entries since for "typical" ZFS style of managing file systems, they are required to ***not*** be put in `/etc/fstab`.

Looks like this fstab issue is the main reason why you felt the need to
define an extra service type.  Why is it important that ZFS not be
listed in /etc/fstab?

Thanks,
Ludo’.


  parent reply	other threads:[~2021-02-22  8:57 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 ` 宋文武
2021-02-22  8:57 ` Ludovic Courtès [this message]
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=87mtvweazb.fsf@gnu.org \
    --to=ludo@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.