Phase 1
Phase 1 Requirements:
- A standard Solaris loadable filesystem module must be provided
- A tool must be provided to list CIFS shares
- A tool must be provided to perform NetBIOS name resolution
- The standard Solaris mount utility must be able to mount CIFS shares
- It must be possible to add an entry to an automounter map to mount a CIFS share
- It must be possible to unmount a CIFS share, including by force ('umount -f')
- It must be possible to create and access a file larger than 2Gb on a server which supports the capability and the CIFS dialect
- The standard file utilities 'tar', 'cpio', 'cp' and 'mv' must be supported on CIFS files and directories, with expected failures for ACLs, extended attributes, hard links and symbolic links
- statvfs(2) must report used and free space on a CIFS share
- It must be possible to place byte-range locks on a file which are visible to other processes on the same client
- It must be possible to authenticate to a CIFS server with password-based authentication using NTLM style password hashing
- It should be possible to authenticate to a CIFS server without a password prompt by using credentials from a pre-existing Active Directory authentication
Phase 1 Limitations:
- No Gnome integration (smbfs mounts via Nautilus)
- No browsing of CIFS servers (i.e. /net for CIFS)
- No mmap or execute support
- No caching of file data or directory entries
- No Oplocks (cache delegation)
- No ACL display or manipulation
- No Packet signing (cryptographic integrity)
- No CIFS Extensions for Unix
- No DFS referrals
- No Printing via CIFS
Phase 2
(coming soon)