From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43257@debbugs.gnu.org
Subject: [bug#43257] [PATCH] services: nfs: Require file-systems to be mounted before starting NFS shepherd service.
Date: Fri, 11 Sep 2020 09:02:09 +0200 [thread overview]
Message-ID: <87h7s4vlse.fsf@gnu.org> (raw)
In-Reply-To: <20200910152042.4b33a84f@scratchpost.org> (Danny Milosavljevic's message of "Thu, 10 Sep 2020 15:20:42 +0200")
Howdy,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Thu, 10 Sep 2020 09:42:58 +0200
> Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I just realized that these services should just all depend on
>> ‘user-processes’ (which depends on ‘file-systems’). So you should
>> probably just do that.
>
> Okay. Thanks.
>
>> You can double-check with ‘guix system shepherd-graph’ that the
>> dependency graph looks good.
>
> $ ./pre-inst-env guix system shepherd-graph -e '(@@ (gnu tests nfs) %nfs-os)'
> gnu/tests/nfs.scm:162:4: error: missing root file system
>
> I can probably work around it somehow--but just logging this not-nice user
> interface here.
Any suggestions? :-)
The only think I could think of is transparently adding a dummy root
file system for the purposes of ‘shepherd-graph’, but it’s not
necessarily a good idea either.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-09-11 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 16:47 [bug#43257] [PATCH] services: nfs: Require file-systems to be mounted before starting NFS shepherd service Danny Milosavljevic
2020-09-09 8:27 ` Ludovic Courtès
2020-09-09 10:13 ` Danny Milosavljevic
2020-09-10 7:42 ` Ludovic Courtès
2020-09-10 13:20 ` Danny Milosavljevic
2020-09-11 7:02 ` Ludovic Courtès [this message]
2020-09-11 8:23 ` Danny Milosavljevic
2020-09-11 14:47 ` Ludovic Courtès
2020-09-11 17:50 ` Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7s4vlse.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=43257@debbugs.gnu.org \
--cc=dannym@scratchpost.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).