|
From: Jeroen G. <jer...@ya...> - 2006-04-11 11:33:54
|
> > This is never called. In fact, after some debugging I found that instead
> > fuse_mount_compat22() is called.
>
> Ahh, this must be the cause of the problem.
>
> This looks like a bug in the dynamic linker. A similar bug can be
> observed on FreeBSD, maybe they are related. The workaround, which is
> already incorporated into 2.6.0-pre2 should work in your case too.
>
> Can you try this version, to see if it works any better?
2.6.0-pre2 gives the same problem. However, when I statically link fusermount
and the examples, fuse_mount is called.
mo.kernel_opts in fuse_mount after fuse_opt_parse is given has the following
value:
fsname=hello
On my embedded target, I do not have an /etc/passwd file, so I hard-coded
user_id and group_id to be 0.
When I now run the the hello example, I get the following output:
DEBUG fusermount: optbuf = fd=4,rootmode=40000,user_id=0,group_id=0
unique: 1, opcode: ??? (0), nodeid: 0, insize: 56
unique: 1, error: -5 (Input/output error), outsize: 16
fuse: writing device: Invalid argument
I assume this is the infamous ARM problem?
--
Best regards,
Jeroen
|