MS Windows ClientWe have contributed a native MS Windows client to OpenAFS. The client connects to MS Windows through the I/O manager (using the Installable Filesystem kernel driver interface), rather than the abstracted SMB layer. This should, in the end, allow faster access, more functionality, and better integration with MS Windows, in general. Its placement into the kernel gives more flexibility for security and earler loading at boot time. The IFS-layer kernel driver directly receives any I/O requests, so this prevents SMB networking layer from affecting afs. OpenAFS's standard cache manager code runs in userspace (as usual), for security reasons. The events in userland are dispatched much like the usual vnode ops, so developers do not need to understand the IFS interface completely to be comfortable working with the code. Code is available in the OpenAFS source tree. It is experimental code; testing and feedback to nativeafs @ { citi.umich.edu. } is appreciated. Links
DownloadsPorts contributed to OpenAFS by CITI.
openafs-1.4.5-i386_obsd41.tar.gz
openafs-1.4.2-fbsd61.tgz
openafs-1.4.2-obsd39.tar.gz
openafs-1.4.1-obsd38.tar.gz
openafs-1.4.1-obsd36.tar.gz
openafs-1.4.0-fbsd60.tar.gz
openafs-1.4.0-obsd37.tar.gz
openafs-1.4.0-obsd36.tar.gz
i386_obsd36.tar.gz (7186771 bytes)
i386_obsd35.tar.gz (7091234 bytes)
i386_obsd33.tar.gz (1472420 bytes)
|