all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: fsdfsdfsd3 <fsdfsdfsd3@protonmail.com>
To: "47706@debbugs.gnu.org" <47706@debbugs.gnu.org>
Subject: bug#47706: Acknowledgement (nfs mount in file-system works only if "nfs4" type is used for "mount" syscall)
Date: Wed, 14 Apr 2021 06:56:04 +0000	[thread overview]
Message-ID: <96F_Fhjta4ncSy_Q4W4RJ8uf9KdXT0aW-9tjbzFonXM8IncbpdISgkoMfuN9k3FJgHqig4ke8fxWm33LoDWLrhcT19xuxri4of9f4TXhu8w=@protonmail.com> (raw)
In-Reply-To: <Pgu6TXk6QaPqp_auy-Dl-BoHVRLiG4_00wVM_mPwSTaqUwEWRQ3-ur68EFQci8CaI8FZEw_X5h4clktJLvIDpMt81388osAVNL9idTUJk-Y=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

Hello,

I ended up testing my config file with nfs4 and that part did work fine. I had earlier errors unrelated to this that threw me off thinking that would not work.

To clarify then, the issue here only seems to be with the mount function in the (guix build syscalls) module. This results in a "No route to host" error even though mount.nfs works fine on the command line.

However perhaps I am assuming that mount.nfs does not make use of nfs4 behind the scenes, even without nfs-utils installed, when it does.

Thank you!

[-- Attachment #2: Type: text/html, Size: 660 bytes --]

  reply	other threads:[~2021-04-14 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11  8:33 bug#47706: nfs mount in file-system works only if "nfs4" type is used for "mount" syscall fsdfsdfsd3 via Bug reports for GNU Guix
2021-04-14  6:56 ` fsdfsdfsd3 [this message]
2021-08-08  3:19 ` Maxim Cournoyer

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='96F_Fhjta4ncSy_Q4W4RJ8uf9KdXT0aW-9tjbzFonXM8IncbpdISgkoMfuN9k3FJgHqig4ke8fxWm33LoDWLrhcT19xuxri4of9f4TXhu8w=@protonmail.com' \
    --to=fsdfsdfsd3@protonmail.com \
    --cc=47706@debbugs.gnu.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 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.