From: Pierre Neidhardt <ambrevar@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: encfs: fusermount: mount failed: Operation not permitted
Date: Sat, 02 Jun 2018 12:59:36 +0200 [thread overview]
Message-ID: <871sdpzc6f.fsf@gmail.com> (raw)
In-Reply-To: <87wovlnf2x.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
Got it!
`fusermount` needs the setuid bit to run properly, but I had installed
`fuse` in my user-profile which put a fusermount link in
~/.guix-profile/bin which has precedence over /run/setuid-programs in my
PATH.
Removing `fuse` from my user-profile fixed it.
That said, shouldn't setuid-programs have precedence over user-installed
programs?
What do you think?
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-06-02 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:49 encfs: fusermount: mount failed: Operation not permitted Pierre Neidhardt
2018-05-10 9:05 ` Pierre Neidhardt
2018-05-14 9:14 ` Ludovic Courtès
2018-05-14 9:21 ` Pierre Neidhardt
2018-05-14 17:39 ` Pierre Neidhardt
2018-05-30 19:00 ` Pierre Neidhardt
2018-06-02 10:59 ` Pierre Neidhardt [this message]
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=871sdpzc6f.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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.
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).