From: Boris Z. (boris@conley.com)
Date: 08/19/98-03:59:41 PM Z
Message-ID: <01BDCB79.9D41ABD0.boris@conley.com> From: "Boris Z." <boris@conley.com> Subject: RE: NFSv4: Identifying users & groups Date: Wed, 19 Aug 1998 13:59:41 -0700 On Tuesday, August 18, 1998 11:10 AM, Carl Beame [SMTP:beame@mail1.tinet.ie] wrote: > On Tue Aug 18 04:02:49 1998, Brent Callaghan wrote: > > Hello, > > > > Currently the NFS version 2 and 3 protocols identify users > > and groups by the use of a binary UID and GID attribute. > > There's an implicit assumption that clients and servers > > share the same UID/GID space. > > > > This is acceptable within a workgroup or small organization > > but impractical on the Internet. We cannot expect IANA > > to dispense UIDs and folks will want to continue using their > > existing UID/GIDs anyway. > > > > So what are the requirements for NFS v4 of a user > > or group "identity" ? I think they look a bit > > like this: > ... > > > > There may be some more - though that's all I can think of for > > now. > > > > I'd be grateful for any comments, proposals or insights. > > > > In the PC world we actually are working without a local UID/GID > mapping on the client. Maybe examining what we do could help... > > We treat the UID/GIDs as Local IDs which only have meaning on the > server. Using PCNFSD or HCLNFSD we have a call available which > translates a String into Local IDs (Unix calls these > UID/GIDs). The "ls" program calls either NIS(+) or HCLNFSD which has > routines which translate Local Ids into text strings which are used > for display. Also the chgrp and chown use these same routines to > translate names to Local Ids. Some other PC clients used UID/GID to construct some PC file attributes (ex: Read-only). We should add somewhere an answer for the question "what rights do I have regarding this file?". One of possible solutions is to extend file attributes, another to add a new procedure.
This archive was generated by hypermail 2.1.2 : 03/04/05-01:46:11 AM Z CST