Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.30 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.31 *** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.13.2.30 Mon May 30 00:13:42 2005 --- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt Sun Jun 5 10:47:08 2005 *************** *** 1,3 **** --- 1,8 ---- + Since 1.3.83: + + * Changes to the algorithms used to wake threads when they are + put to sleep because of conflicts over buffer operations. + Since 1.3.82: * The OpenAFS integrated logon obtains Kerberos 5 tickets as part of the process of producing AFS tokens. The tokens are stored within Index: openafs/doc/txt/winnotes/afs-install-notes.txt diff -c openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.21 openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.22 *** openafs/doc/txt/winnotes/afs-install-notes.txt:1.11.2.21 Mon May 30 00:13:42 2005 --- openafs/doc/txt/winnotes/afs-install-notes.txt Sun Jun 5 10:47:08 2005 *************** *** 1,4 **** ! OpenAFS for Windows 1.3.8300 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the --- 1,4 ---- ! OpenAFS for Windows 1.3.8400 Installation Notes --------------------------------------------- The OpenAFS for Windows product was very poorly maintained throughout the Index: openafs/doc/txt/winnotes/afs-issues.txt diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.13 openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.14 *** openafs/doc/txt/winnotes/afs-issues.txt:1.8.2.13 Tue Apr 19 01:12:19 2005 --- openafs/doc/txt/winnotes/afs-issues.txt Sun Jun 5 10:47:08 2005 *************** *** 1,4 **** ! This file is a rough list of known issues with the 1.3.81 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,4 ---- ! This file is a rough list of known issues with the 1.3.84 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. *************** *** 18,42 **** (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. - - Things are not quite this bad anymore. We are 10% slower than OpenAFS on - Linux but we could still be doing quite a bit faster if we were using an - IFS. - - (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: --- 18,23 ---- *************** *** 76,86 **** [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 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 --- 57,62 ---- *************** *** 129,134 **** --- 105,111 ---- or by the new AFS Client Service Administration tool when executed by an authorized user. + (27) No support for byte range locking. ------------------------------------------------------------------------- List of unfunded projects: *************** *** 173,178 **** --- 150,157 ---- 11. Large File support (> 2GB) in SMB/CIFS client 12. Integrate KFW installation into the NSIS and MSI installers 13. Add support for byte range locking to AFS (requires changes to the servers) + 13a. Simulate support for byte range locking at the client; use full locks + on the server. 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 *************** *** 201,204 **** 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 - --- 180,182 ----