From: "Ludovic Courtès" <ludo@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>
Cc: guix-devel@gnu.org
Subject: Re: Value in adding Shepherd requirements to file-systems entries?
Date: Thu, 02 May 2024 11:15:43 +0200 [thread overview]
Message-ID: <87ikzwzi9s.fsf@gnu.org> (raw)
In-Reply-To: <87le54hhfu.fsf@freakingpenguin.com> (Richard Sent's message of "Mon, 22 Apr 2024 23:43:49 -0400")
Hi!
Richard Sent <richard@freakingpenguin.com> skribis:
> Before hacking away at this myself, I'd like to get other people's
> thoughts on the best way to proceed. Do others agree that (file-system)
> entries should support networked devices? Should this be transparent
> depending on the type, or require explicit configuration?
>
> e.g.
>
> (file-system
> (device "//192.168.1.102/share")
> (options "guest")
> (mount-point "/mnt/share")
> (type "cifs")
> ;; Should we explicitly require network, or implicitly add it from
> ;; the type? If the latter, what to do about Avahi?
> (requirement 'networking)
> (mount-may-fail? #t)
> (create-mount-point? #t))
I think this makes sense.
The other option would be to allow for symbols in the ‘dependencies’
field, because it’s really the same thing. That would only require a
new clause in the ‘dependency->shepherd-service-name’ procedure.
HTH!
Ludo’.
next prev parent reply other threads:[~2024-05-02 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 3:43 Value in adding Shepherd requirements to file-systems entries? Richard Sent
2024-04-23 4:31 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-24 0:45 ` Richard Sent
2024-04-26 19:31 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-27 0:16 ` Attila Lendvai
2024-05-02 9:15 ` Ludovic Courtès [this message]
2024-05-02 12:45 ` Richard Sent
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=87ikzwzi9s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=richard@freakingpenguin.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).