-This file is a rough list of known issues with the 1.3.80 release of OpenAFS
-on Windows. This list is not complete. There are probably other issues
-which can be found in the RT database or on the mailing list.
+This file is a rough list of known issues with the 1.4.0000 release of OpenAFS
+on Windows. This list is not complete. There are probably other issues which
+can be found in the RT database or on the mailing list.
(1) File/Directory access is not integrated with windows security
(iii) the list of hack adapters is incomplete (VMWare, MS TV/Video, ...)
(iv) incompatible with Windows 2000 and earlier
-(4) Performance of the AFS Client Service code simply sucks. The average
-read, write, and delete times for AFS are more than ten times slower than
-the equivalent Windows File Share operations. The Window File Share operations
-are not all that fast. It has been claimed that the Windows AFS functions are
-one hundred times slower than the equivalent operations on Linux. I would not
-be at all surprised. The best we can do without rewriting AFS as a IFS would
-be to match the Windows File Share performance. I believe the threading model
-is imposing significant delays in the movement of data from between the SMB
-and RX protocol operations. There was also an issue with large numbers of
-page faults which have since been fixed.
-
-(7) File termination differences between Win9x and nt/w2k/xp (Jim Peterson)
-
-(8) How to silence "Explorer" when the mapped drive is not available?
-
(9) Convert to IFS!!!!!!
(10) Kerberos 5 integration:
(12c) If network is not available must store the username and password
somewhere until such time as the network starts.
-(13) Loopback adapter is not always installed without bindings to "File and
- Printer Sharing for Microsoft Networks" and with bindings to "Client for Microsoft
- Networks". If these are not bound correct then SMB names will successfully
- be published to a list of zero which causes the AFS not to function.
- We need a way to test whether the Loopback adapter is properly bound
- so we know if it is safe to use. Actually, it is worse. Even with
- the bindings on Win2000 the loopback adapter frequently fails to publish
- SMB names. Of course, the error messages report nothing.
-
-(14) If a drive mapping is "in use", then afscreds cannot be used to Modify
+(13) If a drive mapping is "in use", then afscreds cannot be used to Modify
or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with
description "home" is modified to point to \afs\cell\bar, then the
description must be unique. "home" cannot be reused. We need a way
[Actually, an end user should not be able to modify the submount list]
-(15) Drive mappings are lost on WinXP after return from Standby. (This could
- be because the AFS Client Service fails OR because the RX protocol is
- temporarily unable to access the Cell due to network restore timing
- issues.)
-
-(16) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
+(14) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
the use of interoperable file names; force the use of paths no longer
than 256 characters; force share names to be no longer than 13
characters; restrict authentication to ASCII only names and passwords;
etc.
-(17) No auto-restart on service failure
-
-(18) Better EventLog handling
+(15) No auto-restart on service failure
-(19) Named Pipes Support [requires modifications to AFS servers to support]
+(16) Better EventLog handling
-(20) Memory Mapped File support
+(17) Named Pipes Support [requires modifications to AFS servers to support]
-(21) Large file support [both SMB/CIFS and AFS]
+(18) Memory Mapped File support
-(22) Implement persistent disk based cache which survives restarts
+(19) Large file support [both SMB/CIFS and AFS]
-(23) NSIS Installer issues
+(20) NSIS Installer issues
(a) integration with KFW install script
(b) Optional removal of AFS Server volumes
-(24) The User Interface needs to be re-designed to separate the per-user
+(21) The User Interface needs to be re-designed to separate the per-user
and per-machine settings. All of the new registry items need to
be added to the UI
-(25) CIFS Remote Administration Protocol implementation is incomplete.
+(22) CIFS Remote Administration Protocol implementation is incomplete.
Notifications are not made to requestors when the view of a file
or folder changes due to token acquisition; token expiration; or
token destruction
-(26) Remove submount creation as a side effect of AFS drive mapping.
+(23) Remove submount creation as a side effect of AFS drive mapping.
The AFS Submount is effectively a server side alias for a path
located in the AFS space. This alias is exported by the AFS
or by the new AFS Client Service Administration tool when executed
by an authorized user.
+(24) No support for byte range locking (or locking at all)
-------------------------------------------------------------------------
List of unfunded projects:
10. Documentation Documentation Documentation
11. Large File support (> 2GB) in SMB/CIFS client
12. Integrate KFW installation into the NSIS and MSI installers
- 13. Add support for record locking to AFS (requires changes to the servers)
+ 13. Add support for byte range locking to AFS (requires changes to the servers)
14. Unicode enable the SMB/CIFS server. OEM Code Pages:
1. prevent the use of interoperable file names
2. force the use of paths no longer than 256 characters
22. Add support for storing Windows ACLs on files
23. Remove submount creation as a side effect of drive creation
24. Finish conversion from string.h to strsafe.h for VS.NET 2005
-
git://git.openafs.org / openafs.git / blobdiff