From: "Claes Wallin" <gnu@clacke.user.lysator.liu.se>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 21142@debbugs.gnu.org
Subject: bug#21142: Sshfs-fuse requires fuse
Date: Sun, 29 Nov 2015 17:41:20 +0100 [thread overview]
Message-ID: <CAGv_=Br4Mv_Wfg+pF1VFT=+9Q-wiWydOkPwZsYqwj1Wq=0MjMw@mail.gmail.com> (raw)
In-Reply-To: <87k2p0luo3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Nov 29, 2015 3:58 PM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> >> However, we explicitly patch it because in practice the ‘fusermount’
> >> binary must be at least set-user-gid to fuse, per mount.fuse(8):
> > [ . . . ]
> >> On GuixSD, this is addressed by having ‘fusermount’ setuid-root in
> >> /run/setuid-programs, so things just work.
You mean under GuixSD this works automagically? Or only if fuse is
installed globally and indicated as setuid? (I forget how that works, but
I'll look into it, no need to describe in detail here)
> > Ok, that's pretty clear then. Is this clear somewhere in the
documentation?
> > Otherwise I suppose we should fix that.
>
> Regarding foreign distros, I suppose we could add a paragraph about FUSE
> under “Application Setup”? Would you like to submit a patch against
> guix.texi?
I would like to. I'll see when I get around to it, hopefully around New
Year's.
--
/c
[-- Attachment #2: Type: text/html, Size: 1220 bytes --]
next prev parent reply other threads:[~2015-11-29 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:05 bug#21142: Sshfs-fuse requires fuse Andreas Enge
2015-07-27 17:23 ` Claes Wallin
2015-07-28 14:20 ` Mark H Weaver
2015-07-28 19:27 ` Claes Wallin
2015-11-29 11:18 ` Ludovic Courtès
2015-11-29 11:52 ` Claes Wallin
2015-11-29 14:58 ` Ludovic Courtès
2015-11-29 16:41 ` Claes Wallin [this message]
2015-11-29 17:01 ` Ludovic Courtès
2015-11-29 17:24 ` Claes Wallin
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='CAGv_=Br4Mv_Wfg+pF1VFT=+9Q-wiWydOkPwZsYqwj1Wq=0MjMw@mail.gmail.com' \
--to=gnu@clacke.user.lysator.liu.se \
--cc=21142@debbugs.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.
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.