All of lore.kernel.org
 help / color / mirror / Atom feed
From: "'Bruce Fields'" <bfields@fieldses.org>
To: Frank Filz <ffilzlnx@mindspring.com>
Cc: "'Kernel NFS List'" <linux-nfs@vger.kernel.org>,
	"'Ganesha NFS List'" <nfs-ganesha-devel@lists.sourceforge.net>
Subject: Re: pynfs updates
Date: Tue, 1 Oct 2013 14:45:12 -0400	[thread overview]
Message-ID: <20131001184512.GN26382@fieldses.org> (raw)
In-Reply-To: <009a01cebed2$fcdacb50$f69061f0$@mindspring.com>

On Tue, Oct 01, 2013 at 02:21:01PM -0400, Frank Filz wrote:
> > > > 		- SECNN4: is env.home necessarily unequal to "/"?  Would
> > > > 		  seem better to do the lookup in a subdirectory just to
> > > > 		  be certain.
> > >
> > > Env.home is the directory you specify on the command line, I think the
> > > presumption is that it is a writeable file system. Pynfs creates tmp
> > > and tree directories in home (and maybe some files also?). Guess if /
> > > was writeable, you could specify /, so yea, maybe it should go into tmp.
> > 
> > Sounds good.
> 
> env.home does actually include traversing into tmp, so I will leave this
> test alone.

OK!

--b.

      reply	other threads:[~2013-10-01 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 18:17 pynfs updates Frank Filz
2013-09-30 22:11 ` Bruce Fields
2013-09-30 23:54   ` Frank Filz
2013-10-01 14:26     ` 'Bruce Fields'
2013-10-01 14:30       ` 'Bruce Fields'
2013-10-01 15:42         ` Frank Filz
2013-10-01 19:05         ` Frank Filz
2013-10-02 11:36           ` 'Bruce Fields'
2013-10-02 15:58             ` Frank Filz
2013-10-01 18:21       ` Frank Filz
2013-10-01 18:45         ` 'Bruce Fields' [this message]

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=20131001184512.GN26382@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=ffilzlnx@mindspring.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfs-ganesha-devel@lists.sourceforge.net \
    /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.