On Thu, Dec 07, 2006 at 11:20:20AM -0600, Spencer Shepler wrote: > On Thu, Chris Gerhard wrote: > > My laptop lives in two separate environments, work and home, both have NFS > > services but the name spaces are not the same. My login name at home is not > > the same as my login name at work. > > > > With NFS versions 2 & 3 I could get a good approximation to a working NFS > > system by using the same UID for me at home as I have at work. > > > > With NFS v4 that no longer works however I think I should now be able map > > one user to another so that my laptop knows that when it is on one network > > it maps work_login at sun.com to be home_login at home.network so that NFS > > will work. However I can see no way to actually achieve this. > > > > Is there a way? > > No, there isn't. The current design of the Solaris NFSv4 client is > not targeted at a nomadic client. So, the first step would be to > have a reasonable method to easily change the NFSv4 damain at the > client when the change in context occurs. Actually, it may be interesting > to think about a method of specifying domain per server for cases > such as yours; hard to manage but possible.
Although not applicable to this particular problem, this project: http://www.opensolaris.org/os/project/winchester/ could be extended to support nomadic systems that have a unique local UID/GID namespace and map to other domains as appropriate. E.g., laptop <-> domain A, map user foo at domainA to local UID 5001 laptop <-> domain B, map user foo at domainB to local UID 5002 Nico --
