Re: [nfsv4] ethereal and NFSv4 support.

Next message: Bryce Harrington: "Re: [nfsv4] ethereal and NFSv4 support."
Previous message: Manish Agarwal: "Re: [nfsv4] ethereal and NFSv4 support."
In reply to: Manish Agarwal: "Re: [nfsv4] ethereal and NFSv4 support."
Next in thread: Manish Agarwal: "Re: [nfsv4] ethereal and NFSv4 support."
Reply: Manish Agarwal: "Re: [nfsv4] ethereal and NFSv4 support."

spencer.shepler@sun.com

Date: Thu, 3 Feb 2005 15:33:05 -0600
From: Spencer Shepler <spencer.shepler@sun.com>
Subject: Re: [nfsv4] ethereal and NFSv4 support.
Message-ID: <20050203213305.GC111400@nfsclient.central.sun.com>

Attached are the diffs between 1.103 and 1.122.

On Thu, Manish Agarwal wrote:
> Hi All,
> 
> Is the file nfs4_prot.x under some kind of source control to track
> delta? Does any one know how to get older versions of this file? I'm
> interested in version 1.103.
> 
> Thanks and regards,
> -Manish
> 
> On Wed, 2 Feb 2005 12:52:37 -0500, J. Bruce Fields <bfields@fieldses.org> wrote:
> > On Wed, Feb 02, 2005 at 12:40:42PM -0500, William A.(Andy) Adamson wrote:
> > >
> > > bfields@fieldses.org said:
> > > >  At citi we certainly do this every day and I haven't noticed it parsing
> > > > NFSv4 incorrectly lately.
> > >
> > > Delegation callbacks (CB_NULL, CB_RECALL, CB_GETATTR) are not parsed. OPEN
> > > repy's with a granted READ or WRITE delegation are not parsed.
> > 
> > Yes, it'd be nice if Ethereal handled that stuff.  These are examples of
> > unimplemented features, though, rather than out-of-date xdr.
> > 
> > --b.
> > 
> 
> 
> -- 
> -Manish
> 
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www1.ietf.org/mailman/listinfo/nfsv4