All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: autofs@linux.kernel.org, fedfs-utils-devel@oss.oracle.com
Subject: Re: [PATCH] FedFS file system client support
Date: Mon, 30 May 2011 12:15:20 +0800	[thread overview]
Message-ID: <1306728920.3292.3.camel@perseus.themaw.net> (raw)
In-Reply-To: <20110526163545.3676.52586.stgit@dali.1015granger.net>

On Thu, 2011-05-26 at 12:39 -0400, Chuck Lever wrote:
> Hi-
> 
> The next release of fedfs-utils will provide all necessary components
> for a Linux NFS client to participate in a FedFS domain as a file
> system client.  This new utility is intended to be a part of the
> upcoming release.
> 
> I'm interested in comments on this approach.  Ian had suggested a new
> lookup module, but a program map looked simpler to prototype and has
> the great advantage of no dependencies between fedfs-utils and autofs.
> If program maps have some nasty problem that require the use of a
> lookup module, we can take that next step.

The only difficulty with using a program map is that to use it you need
to know the name of the of the <key> (aka. /nfs4/<key>) since, at the
moment, autofs can't enumerate program map keys.

Ian

  parent reply	other threads:[~2011-05-30  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 16:39 [PATCH] FedFS file system client support Chuck Lever
2011-05-26 16:39 ` [PATCH] mount: Add automounter program map for FedFS Chuck Lever
2011-05-30  4:15 ` Ian Kent [this message]
2011-05-31 15:14   ` [PATCH] FedFS file system client support Chuck Lever
2011-06-01  5:24     ` Ian Kent

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=1306728920.3292.3.camel@perseus.themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=fedfs-utils-devel@oss.oracle.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.