From: Bruno Victal <mirai@makinata.eu>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
bjc@kublai.com, "Ludovic Courtès" <ludo@gnu.org>
Subject: Plan for NFS (was: Herding file-systems)
Date: Tue, 26 Sep 2023 19:35:52 +0100 [thread overview]
Message-ID: <e50e93fc-b73b-41cb-8106-2106e1e1d72f@makinata.eu> (raw)
In-Reply-To: <d10dfe77-ead5-30ae-a0b6-94018a482853@makinata.eu>
Hi all,
I've been thinking on a plan to address this old NFS question.
The plan:
1. Allow the file-system `dependencies' field to accept arbitrary
shepherd symbols as well.
This can be done by having the `dependency->shepherd-service-name'
in (gnu services base) also accept matching against a symbol object.
2. Allow excluding some file-system objects from being dependencies
of the `file-systems' shepherd service.
This is to avoid a cycle scenario where a (NFS) mount requires
'networking (that depends on 'file-systems) which in turn requires
a mount on some device that has the credentials stored for the network
connection. Another scenario to consider is loop mounts.
WDYT?
--
Furthermore, I consider that nonfree software must be eradicated.
Cheers,
Bruno.
next prev parent reply other threads:[~2023-09-26 18:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 14:54 Herding file-systems Bruno Victal
2023-03-10 14:49 ` Maxim Cournoyer
2023-03-25 5:47 ` Liliana Marie Prikler
2023-09-26 18:35 ` Bruno Victal [this message]
2023-09-26 19:39 ` Plan for NFS (was: Herding file-systems) Liliana Marie Prikler
2023-10-04 15:44 ` Plan for NFS Ludovic Courtès
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=e50e93fc-b73b-41cb-8106-2106e1e1d72f@makinata.eu \
--to=mirai@makinata.eu \
--cc=bjc@kublai.com \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.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 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).