[OpenAFS-announce] OpenAFS 1.5.64 released (Production Version for Windows; Test Version for other platforms)

[Derrick J Brashear]

1.5.64 is the recommended production-ready release of OpenAFS for
Microsoft Windows users.  It supports all Microsoft Windows operating
systems from Windows 2000 through Windows Vista SP1 and Windows Server
2008 including both 32-bit and 64-bit architectures.  The 1.5.63
release continues the recent efforts at optimizing the performance of
the Windows client and improving its scalability.

For UNIX, Linux, and MacOS X (including Snow Leopard) the recommended
production-ready release of OpenAFS is 1.4.11.  The 1.5.64 Windows
client is fully compatible with all AFS server versions.

Please visit http://www.openafs.org/windows.html for up to date
information on the status of the OpenAFS for Windows client.

Changes for Microsoft Windows

  * Restores Windows 2000 compatibility.

  * Fixes a data consistency error between the output of
   NetWkstaGetInfo and NetServerGetInfo RPCs, specify the Lan
   workstation group name "AFS", and report server name as
   "AFS" instead of "\\AFS" when the caller asks for "\\AFS".

  * Enables executables to be run from \\AFS on Windows 7.
   Returns "Name not found" instead of "File not found" when
   a directory or file name cannot be found.  This avoids
   loader errors when system dlls cannot be located in the
   executable directory.

  * Prevents cache manager from marking the file server "down" when
   the data returned in response to either RXAFS_FetchData64
   or RXAFS_StoreData64 is invalid.

  * Adds pioctl data validation to the AFS Explorer Shell extension.

Special note regarding Microsoft Windows 7 and OpenAFS:

Windows 7 and Server 2008 R2 experience a bug that can prevent
access to \\AFS.  If the IP addresses assigned to the machine
change after boot or are assigned after user logon (e.g. when
connecting to a wifi network or switching networks), attempts
to resolve the registered NetBIOS name "\\AFS" will fail with
a ERROR_BAD_NETPATH ("The network path was not found") error.
This will be reported by afscreds, aklog, fs, symlink, and
other commands as "The service may not have started."

Please reproduce this error and file a bug report with Microsoft.
It is important that this error receive reports from a broad range
of organizations in order to ensure that a fix will be released
by Microsoft in time for the public release of Windows 7.

All UNIX platforms:

  * A bug which could cause a kernel panic in 1.5.63 has been corrected.
    This would manifest as a GetDCache panic or oops.

All server platforms:

  * The demand attach fileserver now puts back volume references
    gotten via the fssync interface.

  * The demand attach fileserver had a structure reference error, which
    has been correected.

Linux:

  * aklog -setpag works again with recent kernels when keyring is in use.

MacOS:

  * When Fast User Switch is in use, AFS login is now handled correctly
    by the integration tool included with the preferences pane.

  * Several packaging bugs have been corrected.

This release is the recommended production release for all
Microsoft Windows environments.

Source code and binaries can be downloaded from

      http://www.openafs.org/windows.html
      http://www.openafs.org/release/openafs-1.5.64.html

Please send reports of successful deployments to
openafs-info@openafs.org and report problems to openafs-bugs@openafs.org.

Derrick Brashear
for the OpenAFS Gatekeepers