Re: [nfsv4] Minor Versioning.

Next message: Robert Gordon: "Re: [nfsv4] Minor Versioning."
Previous message: Robert Gordon: "Re: [nfsv4] Minor Versioning."
In reply to: Mike Eisler: "RE: [nfsv4] Minor Versioning."
Next in thread: Robert Gordon: "Re: [nfsv4] Minor Versioning."

brent.callaghan@sun.com

Message-ID: <42000020.9090302@sun.com>
Date: Tue, 01 Feb 2005 14:18:08 -0800
From: Brent Callaghan <brent.callaghan@sun.com>
Subject: Re: [nfsv4] Minor Versioning.

Mike Eisler wrote:
> For what is worth, many years ago, we had similar discussion about
> minor version and asking the server for a detailed description of
> what it supported, and the discussion was no less lively or
> contentious. I think we came to Trond's conclusion:
> 
>  > A protocol with large numbers of optional features doesn't make sense
>  > from an interoperability perspective.

Though presumably one would have to make an exception
for the following list of "recommended" features  :-)

         ACL
         aclsupport
         archive
         cansettime
         case_insensitive
         case_preserving
         chown_restricted
         fileid
         files_avail
         files_free
         files_total
         fs_locations
         hidden
         homogeneous
         maxfilesize
         maxlink
         maxname
         maxread
         maxwrite
         mimetype
         mode
         no_trunc
         numlinks
         owner
         owner_group
         quota_avail_hard
         quota_avail_soft
         quota_used
         rawdev
         space_avail
         space_free
         space_total
         space_used
         system
         time_access
         time_access_set
         time_backup
         time_create
         time_delta
         time_metadata
         time_modify
         time_modify_set
         mounted_on_fileid

-------------

	  Brent

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4