All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Peter Staubach <staubach@redhat.com>
Cc: nfs@lists.sourceforge.net, Steve Dickson <SteveD@redhat.com>
Subject: Re: [PATCH 06/11] nfs-utils: mount:  AUTH_NONE mounts
Date: Thu, 15 Mar 2007 09:47:35 +1100	[thread overview]
Message-ID: <17912.31623.829635.980750@notabene.brown> (raw)
In-Reply-To: message from Peter Staubach on Tuesday March 13

On Tuesday March 13, staubach@redhat.com wrote:
> 
> The small update to the patch is to add the line:
> 
>     data.flags |= NFS_MOUNT_SECFLAVOUR;
> 
> after setting data.pseudoflavor to flavor[i].

Thanks... That implies that I don't need the (rather ugly) -1 value to
say "nothing requested".  I can just test this flag and set
data.pseudoflavor to flavor[i] if it isn't set.

Thanks.


> 
> Anyone know why, off hand, the NFS client needs to make two FSINFO calls?
> 

Not me, know...

NeilBrown

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-03-14 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 11:18 [PATCH 06/11] nfs-utils: mount: AUTH_NONE mounts Steve Dickson
2007-02-27  6:14 ` Neil Brown
2007-02-27 14:13   ` Peter Staubach
2007-02-28 23:08     ` Neil Brown
2007-03-01 16:10       ` Peter Staubach
2007-03-02  4:01         ` Neil Brown
2007-03-02 15:27           ` Peter Staubach
2007-03-13  5:49             ` Neil Brown
2007-03-13 16:13               ` Peter Staubach
2007-03-14 22:47                 ` Neil Brown [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=17912.31623.829635.980750@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=staubach@redhat.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.