From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Tero Roponen <tero.roponen@gmail.com>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
linux-kernel@vger.kernel.org, Daniel Phillips <lkml@phunq.net>
Subject: Re: Tux3 report: New news for the new year
Date: Fri, 04 Jan 2013 19:04:33 +0900 [thread overview]
Message-ID: <87wqvtl0we.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <alpine.LFD.2.03.1301021144280.10305@gmail.com> (Tero Roponen's message of "Wed, 2 Jan 2013 11:45:29 +0200 (EET)")
Tero Roponen <tero.roponen@gmail.com> writes:
>> martin@merkaba:~[…]> sudo ./tux3fuse tux3.img /mnt/zeit
>> [sudo] password for martin:
>>
>> martin@merkaba:~[…]> mount | grep fuse
>> fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
>> tux3.img on /mnt/zeit type fuse.tux3.img (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
>>
>>
>>
>> But I am stuck with accessing it:
>>
>> martin@merkaba:~[…]> LANG=C ls -l /mnt/zeit
>> ls: cannot access /mnt/zeit: Permission denied
>>
>> martin@merkaba:~[…]> LANG=C sudo chown martin:martin /mnt/zeit
>> chown: cannot access '/mnt/zeit': Transport endpoint is not connected
>> martin@merkaba:~[…]> LANG=C sudo ls -l /mnt/zeit
>> ls: cannot access /mnt/zeit: Transport endpoint is not connected
>> martin@merkaba:~[…]>
>
> Hi,
>
> I have not looked at Tux3 for a long time, but there seems to be
> a simple fix for at least this problem, and two workarounds:
>
> 1) Run the program in foreground (-f):
>
> sudo ./tux3fuse tux3.img /mnt/zeit -f
>
> 2) Use absolute path for image file:
>
> sudo ./tux3fuse $(pwd)/tux3.img /mnt/zeit
>
> The following patch should hopefully fix this for good.
Thanks for report, Martin. Thanks for fixing, Tero.
Applied with free() for make valgrind happy to temp-atomic-commit branch
(will be merged to master soon).
Thanks!
> commit efc0cf49f6dd00dfbb84e88336d2c5d147a09ed0
> Author: Tero Roponen <tero.roponen@gmail.com>
> Date: Wed Jan 2 11:20:46 2013 +0200
>
> Use absolute path for volume name
>
> If fuse_daemonize() puts us into background it also switches our
> working directory to '/', breaking the use of relative paths.
>
> This patch fixes the problem by converting the relative path to
> an absolute one.
>
> Signed-off-by: Tero Roponen <tero.roponen@gmail.com>
>
> diff --git a/user/tux3fuse.c b/user/tux3fuse.c
> index 6401204..5047cab 100644
> --- a/user/tux3fuse.c
> +++ b/user/tux3fuse.c
> @@ -993,7 +993,7 @@ int main(int argc, char *argv[])
> goto error;
>
> struct tux3fuse tux3fuse = {
> - .volname = argv[1],
> + .volname = canonicalize_file_name(argv[1]),
> };
> fs = fuse_lowlevel_new(&args, &tux3_ops, sizeof(tux3_ops), &tux3fuse);
> if (fs) {
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2013-01-04 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 11:52 Tux3 report: New news for the new year Daniel Phillips
2013-01-01 13:06 ` Martin Steigerwald
2013-01-01 13:28 ` Daniel Phillips
2013-01-01 14:37 ` Martin Steigerwald
2013-01-01 21:49 ` Daniel Phillips
2013-01-02 6:58 ` Shentino
2013-01-02 11:03 ` Daniel Phillips
2013-01-02 9:45 ` Tero Roponen
2013-01-02 11:15 ` Daniel Phillips
2013-01-04 10:04 ` OGAWA Hirofumi [this message]
2013-01-05 9:35 ` Shentino
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=87wqvtl0we.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=Martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@phunq.net \
--cc=tero.roponen@gmail.com \
/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