unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@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: Fri, 07 Jun 2024 18:22:00 -0700	[thread overview]
Message-ID: <87bk4cns93.fsf@lease-up.com> (raw)
In-Reply-To: <87le3gj1w0.fsf@freakingpenguin.com>

Hi Richard,

On Fri, Jun 07 2024, Richard Sent wrote:

> I did have to reboot

So did I. In fact, my issue is now that the file system fails to mount
on boot.

> You could try invoking mount-file-system from (gnu build file-systems)
> directly to try and narrow down what exactly is breaking.

How would I go about doing that, please?

> To confirm, you are using avahi-daemon as a shepherd-requirements

Yes, I am. [1]

Thanks!

Kind regards
Felix

P.S. Did you clear up the confusion about "requirements" being in the
plural?

[1] https://codeberg.org/lechner/system-config/src/commit/4d1f42cf1fc2d4ec6e8dd0434e1567e0d0bbfbf6/host/lechner-desktop/operating-system.scm#L134


  reply	other threads:[~2024-06-08  1:22 UTC|newest]

Thread overview: 11+ 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-06-07 11:11     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-06-07 13:52       ` Richard Sent
2024-06-08  1:22         ` Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2024-06-08  2:21           ` Richard Sent
2024-05-02  9:15 ` Ludovic Courtès
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=87bk4cns93.fsf@lease-up.com \
    --to=guix-devel@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --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).