This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Apr 24 08:30, Andrew DeFaria wrote:I don't have access to the AD DC.On 04/24/2012 08:00 AM, Corinna Vinschen wrote:No, but on the AD DC.I don't think there's an MMC snap-in on a Netapp...And make sure the uid/gid mapping is set up correctly (Windows 2008 AD mapping works fine, see the "UNIX Attributes" tab in the user/group properties dialog in the "Active Directory Users and Computers" MMC Snap-in).
I just reinstalled SFU on my XP laptop. I'm not seeing provider order options at all. I see a snapin for SFU which has Client for NFS which only has a File Permissions tab and a Performance tab. There is also Telnet Server and User name mapping selections.
And make sure the security settings in the NFS client (starting with W7) are correct. If the NFS server doesn't support krb5 authentication, you should explicitly switch them off in the "Services for Network File System" MMC Snap-in. Also, make sure that "reserved ports" is enabled for best interoperability.As I said, I don't have Win 7 - just XP. I had uninstalled SFU because I saw no way to solve this problem. Perhaps some of your settings above are transferable to the Netapp and they will set them and then I can try again.I was talking about the *client* options. For XP all I said can be ignored, except the provider order.
There appears to be a username mapping for NIS.On XP you can simply use a passwd and group file (NOT the Cygwin passwd and group files!) for identity mapping on the client machine.
I thought it might be able to contain this within the cygwin1.dll but apparently not.
Still, an NFS client isn't just some arbitrary piece of software, it's a filesystem driver, like ntfs.sys. There's no OSS code available which provides this kind of FS driver for Windows.I admit that NFS client is involved, a driver, in the kernel, etc. But isn't there SFU already coded? I guess the source isn't readily available if at all. I think that having an NFS client would be beneficial to all as NFS protocol seems to be way faster than SMB and more conducive to the "Linux/Cygwin" environment.SFU *is* the NFS client. You seem to expect that there's some user space executable which constitutes the NFS client, but that's not the case. The OS driver *is* the NFS client. Full stop.
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |