all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se>
Cc: 21142@debbugs.gnu.org
Subject: bug#21142: Sshfs-fuse requires fuse
Date: Sun, 29 Nov 2015 15:58:04 +0100	[thread overview]
Message-ID: <87k2p0luo3.fsf@gnu.org> (raw)
In-Reply-To: <CAGv_=Bp4E=sVg_aKap3QGnsHS1fGqX89zfHu3f2Fn89BuBCpRQ@mail.gmail.com> ("Claes Wallin \=\?utf-8\?B\?KOmfi+WYieiqoCkiJ3M\=\?\= message of "Sun, 29 Nov 2015 12:52:26 +0100")

"Claes Wallin (韋嘉誠)" <gnu@clacke.user.lysator.liu.se> skribis:

> On 29-Nov-2015 12:19 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.
>>
>> On foreign distros, there’s not much we can do: Users have to set add a
>> setuid ‘fusermount’ in their PATH.
>>
>> Closing this bug as “wontfix.”
>
> 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?

Thanks,
Ludo’.

  reply	other threads:[~2015-11-29 14:59 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 [this message]
2015-11-29 16:41           ` Claes Wallin
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=87k2p0luo3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=21142@debbugs.gnu.org \
    --cc=gnu@clacke.user.lysator.liu.se \
    /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.