From: Petr Uzel <petr.uzel@suse.cz>
To: Miklos Szeredi <mszeredi@suse.cz>
Cc: Karel Zak <kzak@redhat.com>, util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH] umount: allow non-root umount of FUSE even if not in fstab
Date: Tue, 29 Mar 2011 10:56:01 +0200 [thread overview]
Message-ID: <20110329085601.GD26819@foxbat.suse.cz> (raw)
In-Reply-To: <1301388690.22846.88.camel@tucsk.pomaz.szeredi.hu>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Tue, Mar 29, 2011 at 10:51:30AM +0200, Miklos Szeredi wrote:
> On Tue, 2011-03-29 at 10:46 +0200, Petr Uzel wrote:
> > > Wouldn't be better to always call /sbin/umount.fuse for non-roots (except
> > > umount -i)?
> >
> > Yes, that's what I meant by umount helpers. The problem is that AFAICS
> > fuse does not provide this helper.
> >
> > @Miklos: what do you think? Would it make sense to have umount.fuse
> > (most likely as symlink to /sbin/mount.fuse)? I could look into it.
>
> Could umount.fuse allow umount of fuse filesystem even if not in fstab?
Yes, as far as I understand.
> If so, then I don't see any problem with providing /sbin/umount.fuse.
OK, I'll try to look into it.
>
> Thanks,
> Miklos
Thanks,
Petr
--
Petr Uzel
IRC: ptr_uzl @ freenode
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-29 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 14:04 [PATCH] umount: allow non-root umount of FUSE even if not in fstab Petr Uzel
2011-03-28 14:23 ` Miklos Szeredi
2011-03-29 8:08 ` Petr Uzel
2011-03-29 8:28 ` Karel Zak
2011-03-29 8:48 ` Miklos Szeredi
2011-03-29 10:13 ` Karel Zak
2011-03-28 22:03 ` Karel Zak
2011-03-29 8:46 ` Petr Uzel
2011-03-29 8:51 ` Miklos Szeredi
2011-03-29 8:56 ` Petr Uzel [this message]
2011-03-29 10:03 ` Karel Zak
2011-03-29 10:36 ` Karel Zak
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=20110329085601.GD26819@foxbat.suse.cz \
--to=petr.uzel@suse.cz \
--cc=kzak@redhat.com \
--cc=mszeredi@suse.cz \
--cc=util-linux@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox