That workaround worked in 2014, but now "libfuse" seems to search under
"/usr/bin" and not "/run/setuid-programs". The `DFUSERMOUNT_DIR` modification
doesn't seem to work anymore. I think to reproduce all what is needed is
`strace` with follow forks to see the software seeking "/usr/bin." And
p
That workaround worked in 2014, but now "libfuse" seems to search under
"/usr/bin" and not "/run/setuid-programs". The `DFUSERMOUNT_DIR` modification
doesn't seem to work anymore. I think to reproduce all what is needed is
`strace` with follow forks to see the software seeking "/usr/bin." And
p
On Nov 29, 2015 6:01 PM, "Ludovic Courtès" wrote:
> >> >> 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?
>
> Yes. ‘fusermount’ is part of ‘%setuid-programs’:
Still, fus
"Claes Wallin (韋嘉誠)" skribis:
> On Nov 29, 2015 3:58 PM, "Ludovic Courtès" 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 ‘fuser
On Nov 29, 2015 3:58 PM, "Ludovic Courtès" 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-
"Claes Wallin (韋嘉誠)" skribis:
> On 29-Nov-2015 12:19 pm, "Ludovic Courtès" 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’ setui
On 29-Nov-2015 12:19 pm, "Ludovic Courtès" 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 thi
Mark H Weaver skribis:
> Claes Wallin (韋嘉誠) writes:
>
>> On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote:
>>>
>>> Hello,
>>>
>>> when trying to execute sshfs from the sshfs-fuse package, I obtain
>>> fuse: failed to exec fusermount: No such file or directory
>>>
>>> I think that fuse should be a p
On Jul 28, 2015 4:21 PM, "Mark H Weaver" wrote:
> Claes Wallin (韋嘉誠) writes:
> > On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote:
> >>
> >> Hello,
> >>
> >> when trying to execute sshfs from the sshfs-fuse package, I obtain
> >> fuse: failed to exec fusermount: No such file or directory
> >>
> >> I
Claes Wallin (韋嘉誠) writes:
> On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote:
>>
>> Hello,
>>
>> when trying to execute sshfs from the sshfs-fuse package, I obtain
>> fuse: failed to exec fusermount: No such file or directory
>>
>> I think that fuse should be a propagated input of sshfs-fuse.
>
> M
On 27-Jul-2015 5:06 pm, "Andreas Enge" wrote:
>
> Hello,
>
> when trying to execute sshfs from the sshfs-fuse package, I obtain
>fuse: failed to exec fusermount: No such file or directory
>
> I think that fuse should be a propagated input of sshfs-fuse.
Maybe it's less intrusive toward the us
Hello,
when trying to execute sshfs from the sshfs-fuse package, I obtain
fuse: failed to exec fusermount: No such file or directory
I think that fuse should be a propagated input of sshfs-fuse.
Andreas
12 matches
Mail list logo
