From: Sam Lang <sam.lang@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: mounting fuse from fstab
Date: Mon, 10 Dec 2012 11:57:18 -1000 [thread overview]
Message-ID: <50C65ABE.5010102@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212101229540.28411@cobra.newdream.net>
On 12/10/2012 10:33 AM, Sage Weil wrote:
> We put together a simple helper script for mounting ceph-fuse via fstab
> (below). Some of man pages indicate that the # syntax is deprecated,
> however, and it's not clear to me that whatever replaces it (mount.fuse)
> will let us accomplish the same thing (pass something along the mount,
> control command line options). Also, it's unclear *when* it was
> deprecated; if we want this to work on, say, RHEL, the replacement
> might not be there.
Would the fuse options fsname and subtype be more portable?
-sam
>
> Anybody know if doing something like the below is a bad idea?
>
> Thanks!
> sage
>
> ---
>
> #!/bin/sh
> #
> # Helper to mount ceph-fuse from /etc/fstab. To use, add an entry
> # like:
> #
> # # DEVICE PATH TYPE OPTIONS
> # /sbin/ceph-fuse-mount#admin /mnt/ceph ceph defaults 0 0
> #
> # where 'admin' can be replaced with the client id to use when
> # authenticating (if it is not client.admin). This will also control
> # which section of ceph.conf will be applied to the ceph-fuse process.
>
> set -e
> id="$1"
> shift
> exec ceph-fuse -i $id $@
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-12-10 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 20:33 mounting fuse from fstab Sage Weil
2012-12-10 21:57 ` Sam Lang [this message]
2012-12-11 0:33 ` Sage Weil
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=50C65ABE.5010102@inktank.com \
--to=sam.lang@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.