From: Tommi Virtanen <tommi.virtanen@dreamhost.com>
To: Fyodor Ustinov <ufm@ufm.su>
Cc: ceph-devel@vger.kernel.org
Subject: Re: cfuse and ceph.conf
Date: Tue, 31 May 2011 16:11:55 -0700 [thread overview]
Message-ID: <20110531231155.GC12733@dreamer> (raw)
In-Reply-To: <4DE5613E.4010602@ufm.su>
On Wed, Jun 01, 2011 at 12:44:30AM +0300, Fyodor Ustinov wrote:
> As I understand with -m key cfuse should not require ceph.conf.
It does need a config, to even know whether it should attempt
cryptographic authentication or not (and where to find the key, etc).
It could be changed to do things more like the kernel client,
but as is, it always requires a config file.
> root@st8:~# cfuse -c /dev/null -m 10.5.51.230:6789 /stor01
...
> root@st8:~# ls -al /stor01/
> total 1
> drwxr-xr-x 1 root root 0 2011-06-01 00:22 .
> drwxr-xr-x 1 root root 0 2011-05-31 01:27 bbb
> root@st8:~#
>
> P.S. BTW, where ".." directory?
Oh, heh, that's interesting.
It seems "." and ".." are optional, according to POSIX:
http://sourceforge.net/mailarchive/forum.php?thread_name=E1O3s82-0008BY-MW%40pomaz-ex.szeredi.hu&forum_name=fuse-devel
--
:(){ :|:&};:
next prev parent reply other threads:[~2011-05-31 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 21:44 cfuse and ceph.conf Fyodor Ustinov
2011-05-31 23:11 ` Tommi Virtanen [this message]
2011-06-01 4:18 ` 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=20110531231155.GC12733@dreamer \
--to=tommi.virtanen@dreamhost.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ufm@ufm.su \
/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.