Index: openafs/doc/man-pages/pod8/fileserver.pod
diff -c openafs/doc/man-pages/pod8/fileserver.pod:1.5.2.11 openafs/doc/man-pages/pod8/fileserver.pod:1.5.2.14
*** openafs/doc/man-pages/pod8/fileserver.pod:1.5.2.11	Sun Aug 24 21:15:03 2008
--- openafs/doc/man-pages/pod8/fileserver.pod	Tue Nov 11 21:31:12 2008
***************
*** 198,210 ****
  
  The File Server stores volumes in partitions. A partition is a
  filesystem or directory on the server machine that is named C</vicepX>
! or C</vicepXX> where XX is "a" through "z" or "aa" though "zz". The
! File Server expects that the /vicepXX directories are each on a
! dedicated filesystem. The File Server will only use a /vicepXX if it's
! a mountpoint for another filesystem, unless the file
! C</vicepXX/AlwaysAttach> exists. The data in the partition is a
! special format that can only be access using OpenAFS commands or an
! OpenAFS client.
  
  The File Server generates the following message when a partition is nearly
  full:
--- 198,210 ----
  
  The File Server stores volumes in partitions. A partition is a
  filesystem or directory on the server machine that is named C</vicepX>
! or C</vicepXX> where XX is "a" through "z" or "aa" though "iv". Up to
! 255 partitions are allowed. The File Server expects that the /vicepXX
! directories are each on a dedicated filesystem. The File Server will
! only use a /vicepXX if it's a mountpoint for another filesystem,
! unless the file C</vicepXX/AlwaysAttach> exists. The data in the
! partition is a special format that can only be access using OpenAFS
! commands or an OpenAFS client.
  
  The File Server generates the following message when a partition is nearly
  full:
***************
*** 232,248 ****
  option only on the relevant system type.
  
  Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
! and the maximum size of a /vicepX partition on a fileserver is 2^64 
! kilobytes.  (The maximum partition size in releases 1.5.34 and earlier
! is 2^31 kilobytes.)
! 
! The maximum number of directory entries is 64,000 if all of the
! entries have names that are 15 characters or less in length. A name
! that is 15 characters long requires the use of only one block in the
! directory. Additional sequential blocks are required to store entries
! with names that are longer than 15 characters. Each additional block
! provides an additional length of 32 characters for the name of the
! entry.
  
  In real world use, the maximum number of objects in an AFS directory
  is usually between 16,000 and 25,000, depending on the average name
--- 232,249 ----
  option only on the relevant system type.
  
  Currently, the maximum size of a volume is 2 terabytes (2^31 bytes)
! and the maximum size of a /vicepX partition on a fileserver is 2^64
! kilobytes. The maximum partition size in releases 1.4.7 and earlier is
! 2 terabytes (2^31 bytes). The maximum partition size for 1.5.x
! releases 1.5.34 and earlier is 2 terabytes as well.
! 
! The maximum number of directory entries is 64,000 if all of the entries
! have names that are 15 octets or less in length. A name that is 15 octets
! long requires the use of only one block in the directory. Additional
! sequential blocks are required to store entries with names that are longer
! than 15 octets. Each additional block provides an additional length of 32
! octets for the name of the entry. Note that if file names use an encoding
! like UTF-8, a single character may be encoded into multiple octets.
  
  In real world use, the maximum number of objects in an AFS directory
  is usually between 16,000 and 25,000, depending on the average name
***************
*** 271,278 ****
  the maximum possible number, the File Server automatically uses five 
  of the threads for its own purposes).
  
! The maximum number of threads can differ in each release of AFS.  Consult
! the I<IBM AFS Release Notes> for the current release.
  
  =item B<-spare> <I<number of spare blocks>>
  
--- 272,279 ----
  the maximum possible number, the File Server automatically uses five 
  of the threads for its own purposes).
  
! The maximum number of threads can differ in each release of OpenAFS.
! Consult the I<OpenAFS Release Notes> for the current release.
  
  =item B<-spare> <I<number of spare blocks>>
  
Index: openafs/doc/txt/winnotes/afs-changes-since-1.2.txt
diff -c openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.63 openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.64
*** openafs/doc/txt/winnotes/afs-changes-since-1.2.txt:1.72.2.63	Fri Nov  7 14:24:12 2008
--- openafs/doc/txt/winnotes/afs-changes-since-1.2.txt	Mon Dec 29 18:21:01 2008
***************
*** 1,5 ****
--- 1,73 ----
+ Since 1.5.55
+ 
+  * Fix a race in rxi_WriteProc which could result
+    in a freed or in use packet being passed to 
+    rxi_PrepareSendPacket if the call is currently
+    in a transmit wait state.  Passing a freed packet
+    will result in a panic.  Passing an in use packet
+    might result in a call failure or perhaps data
+    corruption.
+ 
+  * Kerberos referrals broke the NIM AFS provider 
+    logic for automated configuration of the workstation
+    cell with a new identity.  Now if a referrals 
+    response is returned, assume the cell belongs to the
+    new identify.
+ 
+  * The interface to buf_CleanAsync() and 
+    buf_CleanAsyncLocked() has been changed to permit 
+    errors to be propagated to the caller.  
+ 
+  * During an enumeration of a directory, if the btree
+    has not yet been generated, return an error.
+ 
+  * When mapping CM_ERROR values to NTSTATUS values
+    do not treat 0 as an error.
+ 
+  * Avoid a cm_scache_t object reference count underflow
+    when renaming via the SMB interface.
+ 
+  * smb_IsMask() can be called with a non-8.3 input buffer.
+    Separate smb_IsMask() into smb_Is8Dot3Mask() for 8.3
+    input buffers and smb_IsMask() for non-8.3 input buffers.
+ 
+  * Add cm_buf_t error state to the "fs memdump" output.
+ 
+  * pioctl drive mapping checks need to take into account
+    Global Drive Mappings and SUBST assignments.
+ 
+  * Rename operations should not be permitted if the 
+    destination name collides with an existing name that
+    differs only by case UNLESS the collision is the object
+    that is being renamed.
+ 
+  * Increase the maximum number of background daemon threads
+    to 64.  Leave the default at 4.
+ 
+  * Set the FILE_UNICODE_ON_DISK flag when reporting the 
+    file system characteristics.
+ 
+  * Report the maximum component name length as 255 even
+    for Unicode as part of the file system characteristics.
+ 
+  * Add RX debugging information to "fs memdump" output
+    in checked builds.
+ 
+  * Refcount the cm_server_t objects returned by
+    cm_FindServerByIP()
+ 
+  * Fix the UAC manifest applied to afs_config.exe
+ 
+  * rxdebug now indicates if any RX_CONN flag is set
+    not just some of them
+ 
+  * Change the mapping of CM_ERROR_WOULDBLOCK from 
+    NTSTATUS_LOCK_NOT_GRANTED to NTSTATUS_CANT_WAIT
+ 
  Since 1.5.54
  
+  * Includes #GCO Public CellServDB 07 Nov 2008
+ 
   * Prevent separate cell entries from being created for
     "foobar.org" and "foobar.org." which can happen if
     an AFSDB record is found instead of a CellServDB 
Index: openafs/doc/txt/winnotes/afs-integration.txt
diff -c openafs/doc/txt/winnotes/afs-integration.txt:1.4.2.2 openafs/doc/txt/winnotes/afs-integration.txt:1.4.2.3
*** openafs/doc/txt/winnotes/afs-integration.txt:1.4.2.2	Fri Dec 28 15:25:41 2007
--- openafs/doc/txt/winnotes/afs-integration.txt	Mon Dec 29 18:21:01 2008
***************
*** 1,4 ****
! ...(This document is current as of release 1.5.29)
  
  How to determine if OpenAFS is installed?
  
--- 1,4 ----
! ...(This document is current as of release 1.5.55)
  
  How to determine if OpenAFS is installed?
  
Index: openafs/doc/txt/winnotes/afs-issues.txt
diff -c openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.10 openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.11
*** openafs/doc/txt/winnotes/afs-issues.txt:1.28.2.10	Wed Jul 16 01:59:58 2008
--- openafs/doc/txt/winnotes/afs-issues.txt	Mon Dec 29 18:21:01 2008
***************
*** 1,4 ****
! This file is a rough list of known issues with the 1.5.50 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.5.55 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.
  
***************
*** 14,24 ****
    (i)   prevents use of AFS Gateway 
    (ii)  requires installation of loopback adapter
  
- (9) Convert to a native file system implementation built upon:
-      - a file system redirector
-      - a file system filter
-      - a network provider
- 
  (12) AFS Integrated Logon:
  (12c) If network is not available must store the username and password 
        somewhere until such time as the network starts.
--- 14,19 ----
***************
*** 27,34 ****
  
  (17) Named Pipes Support [requires modifications to AFS servers to support]
  
- (18) Memory Mapped File support
- 
  (20) NSIS Installer issues
       (a) integration with KFW install script
       (b) Optional removal of AFS Server volumes
--- 22,27 ----
***************
*** 110,116 ****
    21. Add support for storing Extended Attributes on files
    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
    25. Implement RX Statistics gathering interfaces and reporting tools
        (necessary to obtain profiling data)
    26. Implement RX Connection Pools in the Cache Manager allowing more than
--- 103,109 ----
    21. Add support for storing Extended Attributes on files
    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 2005/2008
    25. Implement RX Statistics gathering interfaces and reporting tools
        (necessary to obtain profiling data)
    26. Implement RX Connection Pools in the Cache Manager allowing more than
