I believe there does need to be a Linux NCP client, but I do not think it has to so slavishly imitate the Windows client as the previous iteration did (i.e. no auto-mapping to drive letters in the users home, providing a task bar icon, etc.). What it SHOULD do is provide authentication and user information integrated with the OS (i.e. like namcd but better -- not using LDAP and able to provide a richer attribute set, group info, etc.) and it should allow generalized NCP access at the CLI level as well as the ability to see and map NCP volumes as if they were NFS or other remote parts of the Linux file system. It is very sad that SLES and SLED have much better AD/SMB integration out of the box than they have OES/NCP/eDirectory integration.
I believe there does need to be a Linux NCP client, but I do not think it has to so slavishly imitate the Windows client as the previous iteration did (i.e. no auto-mapping to drive letters in the users home, providing a task bar icon, etc.). What it SHOULD do is provide authentication and user information integrated with the OS (i.e. like namcd but better -- not using LDAP and able to provide a richer attribute set, group info, etc.) and it should allow generalized NCP access at the CLI level as well as the ability to see and map NCP volumes as if they were NFS or other remote parts of the Linux file system. It is very sad that SLES and SLED have much better AD/SMB integration out of the box than they have OES/NCP/eDirectory integration.