From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>,
Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Subject: Re: [PATCH] mount.nilfs2: add "uhelper=" option
Date: Fri, 23 Jul 2010 16:42:57 +0900 [thread overview]
Message-ID: <87eieuej9a.wl%jir@sekiba.com> (raw)
In-Reply-To: <876306y7ha.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
Grr I'm sorry. please ignore this patch.
I sent the wrong one.
I'll resend the correct one soon.
--
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
At Fri, 23 Jul 2010 16:37:05 +0900,
Jiro SEKIBA wrote:
>
> Hi,
>
> This is a patch against mount.nilfs2.
>
> I'm trying to add nilfs2 support on several software stack to control
> nilfs2 partition from palimpsest(gnome-disk-utility). And found
> that the option is required to handled properly.
>
> Standard mount command takes uhelper=<helper_name> option to tell the mount
> is under <helper_name> control. When this option is specified,
> umount.<helper_name> is called on unmount time.
>
> This option is used when mount is triggered by udisks. udisks is a dbus
> service daemon. The service is used by Palimpsest. To controll nilfs2
> partition from palimpsest, interpret the option is required.
>
> Signed-off-by: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
> ---
> sbin/mount/mount_opts.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/sbin/mount/mount_opts.c b/sbin/mount/mount_opts.c
> index 9db599f..0c6ca79 100644
> --- a/sbin/mount/mount_opts.c
> +++ b/sbin/mount/mount_opts.c
> @@ -98,7 +98,7 @@ static const struct opt_map opt_map[] = {
> };
>
> static const char *opt_loopdev, *opt_vfstype, *opt_offset, *opt_encryption,
> - *opt_speed, *opt_comment;
> + *opt_speed, *opt_comment, *opt_uhelper;
>
> static struct string_opt_map {
> char *tag;
> @@ -111,6 +111,7 @@ static struct string_opt_map {
> { "encryption=", 0, &opt_encryption },
> { "speed=", 0, &opt_speed },
> { "comment=", 1, &opt_comment },
> + { "uhelper=", 1, &opt_uhelper },
> { NULL, 0, NULL }
> };
>
> --
> 1.5.6.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-23 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 7:37 [PATCH] mount.nilfs2: add "uhelper=" option Jiro SEKIBA
[not found] ` <876306y7ha.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-07-23 7:42 ` Jiro SEKIBA [this message]
[not found] <87d3ueej51.wl%jir@sekiba.com>
[not found] ` <87d3ueej51.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-07-23 14:33 ` Ryusuke Konishi
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=87eieuej9a.wl%jir@sekiba.com \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.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