From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: Efraim Flashner <efraim@flashner.co.il>, 42036@debbugs.gnu.org
Subject: bug#42036: Failed to mount fuse sshfs
Date: Sun, 28 Jun 2020 13:49:26 +0200 [thread overview]
Message-ID: <87r1tzquk9.fsf@nckx> (raw)
In-Reply-To: <877dvujrha.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
Oleg Pykhalov 写道:
> Tobias Geerinckx-Rice <me@tobias.gr> writes:
>> However, Oleg: are you sure it looks *only* in /bin?
[…]
> Here is a ‘mount -t‘ strace:
> --8<---------------cut
> here---------------start------------->8---
> oleg@guixsd ~$ mount -t fuse -o rw,allow_other
> sshfs#oleg@workstation:/home/oleg /tmp/f
> /gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh:
> sshfs: command not found
>
> execve("/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh",
> ["/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/sh",
> "-c", "'sshfs' 'oleg@workstation:/home/oleg' '/tmp/f' '-o'
> 'rw,allow_other,dev,suid'"], 0x961430 /* 74 vars */) = 0
> ...
> stat(".", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
> stat("/usr/local/bin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No
> such file or directory)
> stat("/usr/local/sbin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No
> such file or directory)
> stat("/usr/bin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No such
> file or directory)
> stat("/usr/sbin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No such
> file or directory)
> stat("/bin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No such
> file or directory)
> stat("/sbin/sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No such
> file or directory)
> stat(".", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
> stat("./sshfs", 0x7ffed0ac1c90) = -1 ENOENT (No such
> file or directory)
> --8<---------------cut
> here---------------end--------------->8---
Thanks! This part comes from mount.fuse, right?
mount calls mount.fuse with $PATH unset. mount.fuse calls
<bash-minimal>/bin/sh -c sshfs …, which uses
/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:.
by default. Not very useful on Guix Systems.
I'm considering the best place to fix this: util-linux (probably),
fuse (it would only affect mount.fuse, but maybe we want that kind
of control), or bash (almost certainly not).
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-06-28 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 20:36 bug#42036: Failed to mount fuse sshfs Oleg Pykhalov
2020-06-25 10:27 ` Efraim Flashner
2020-06-25 12:46 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-06-26 6:01 ` Oleg Pykhalov
2020-06-28 11:49 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-05-16 6:51 ` Michael Rohleder
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=87r1tzquk9.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=42036@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=go.wigust@gmail.com \
--cc=me@tobias.gr \
/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.