[OpenAFS-win32-devel] 1.3.66 packaged but not announced - 1.3.70 to
follow in a few daysif no major issues
Douglas E. Engert
deengert@anl.gov
Tue, 27 Jul 2004 11:08:47 -0500
One question, does the freelance support the access to the RW path via
the .cellname yet?
If not this is the one missing feature we would still like as we have users
updating web pages in AFS that are replicated volumes.
Jeffrey Altman wrote:
> 1.3.66 installers can be found at:
>
> /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/
> \\afs\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\
> http://web.mit.edu/~jaltman/Public/OpenAFS/
>
> OpenAFS for Windows release 1.3.66 is a release candidate distribution.
> 1.3.66 is the culmination of eight months of significant effort which has
> has resulted in the most stable and functional AFS client for the Windows
> operating systems in the history of AFS. While the last five months have
> produced a new stable build every month, it is now time to slow things
> down for a while. Assuming the 1.3.66 is found to contain no significant
> bugs in the couple of days it will be re-released as 1.3.70. 1.3.70 will be
> a long term stable build. The OpenAFS Gatekeepers do not anticipate
> releasing another stable build for the Windows platform before the end
> of the year. In the meantime, development will continue to focus on
> functionality which is expected to be destabilizing in the near term but
> which in the long term will produce an even better product for the
> subsequent year.
>
> The 1.3.66/1.3.70 release is a departure from previous releases and is
> not fully backward compatible. In particular, not all configuration data
> will be re-used from previously installed releases. In this release all
> OpenAFS configuration data is moved out of the WINDOWS directory
> and stored either within the registry or the OpenAFS Client installation
> directory. The location of information is documented within the
> afs-install-notes.txt and registry.txt files associated with the release.
> It is hoped that this is the only time that OpenAFS.org will have to
> make such an incompatible change.
>
> Active development of OpenAFS for Windows installation and configuration
> documentation is underway within the OpenAFS Wiki. It is hoped the
> wider community will continue the efforts of a small few in extending
> the collective knowledge.
>
> http://grand.central.org/twiki/bin/view/AFSLore/NewWindowsDocumentation
>
> The following is a summary of major features added to OpenAFS for
> Windows since the 1.2.10 release:
>
> * Kerberos 5 support is provided via integration with the MIT
> Kerberos for Windows 2.6.x distribution. This supports token
> retrieval via Kerberos 5 without the use of krb524d; automatic
> token renewal; tokens for multiple cells from a single Kerberos 5
> principal; a built in aklog command line client; support for use
> of Windows Active Directory issued tickets; and more.
> * The Microsoft Loopback Adapter is automatically installed by
> the OpenAFS for Windows installers. With the MSA installed
> OpenAFS will use a common "AFS" server name on all machines
> simplifying the use of AFS paths within login scripts
> * AFS UNC paths are now supported throughout the operating
> system. \\AFS\cellname\directory
> * SMB/CIFS connections are now authenticated thereby closing a
> security hole.
> * OpenAFS will now by default utilize a locally defined root.afs
> volume. Now longer is network connectivity to the root.afs
> volume of the default cell a requirement for starting the AFS
> Client Service. (This feature is known as "freelance" or
> "dynamic root" mode.)
> * Cell server lookups via DNS are now active by default without
> any additional configuration.
> * The integration logon functionality has been significantly enhanced
> to support different behavior based upon the domain used to
> logon to the machine. Tokens are automatically destroyed upon
> logoff (except when a roaming profile is being loaded from an
> AFS volume.)
> * The AFS Systray tool has been enhanced with new command line
> options used to automatically restore drive mappings from previous
> sessions. This is particularly useful with roaming profiles.
> * The AFS Client Service configuration may only be altered via
> Administrator accounts.
> * OpenAFS for Windows will be compatible with both Windows XP SP2
> and Windows 2003 SP1 (when they are released)
> * Old style profile (.ini) files are no longer used. All configuration
> information is now stored in the registry with proper separation of
> user and machine specific data. This allows individual users to
> maintain their own drive mappings as well as be able to roam from
> machine to machine and keep their settings.
> * Integration with the Windows Explorer has been significantly improved.
> * OpenAFS is now compatible with Windows Terminal Server.
> * Large numbers of resource leaks and other coding errors have been
> corrected.
>
> For a complete summary of all changes since the 1.2.10 release see the file:
> afs-changes-since-1.2.txt.
>
> For a list of known open issues see the file: afs-issues.txt
> For information on configuring the MSI installer for local distribution see
> the file: msi-deployment-guide.txt
>
> ------------------------------------------------------------------------
>
> Reporting Bugs:
>
> Bug reports should be sent to openafs-bugs@openafs.org. Please include as
> much information as possible about the issue. If you are reporting a crash,
> please install the debugging symbols by re-running the installer. If a dump
> file is available for the problem include it along with the AFS Client Trace
> file %WINDIR%\TEMP\afsd.log. The AFS Client startup log is
> %WINDIR%\TEMP\afsd_init.log. Send the last continuous block of log
> information from this file.
>
> ------------------------------------------------------------------------
>
> How to Contribute to the Development of OpenAFS for Windows:
>
> Contributions to the development of OpenAFS for Windows are needed.
> Contributions may take many forms including cash donations, support
> contracts,
> donated developer time, donated tech writer time, and even testing time
> is appreciated.
>
> -------------------------------------------------------------------------
>
> Mailing Lists:
>
> If you wish to be involved in OpenAFS for Windows development please
> join the
> openafs-win32-devel@openafs.org mailing list.
>
> https://lists.openafs.org/mailman/listinfo/openafs-win32-devel
>
> User questions should be sent to the openafs-info@openafs.org mailing list.
>
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
> You must join mailing lists if you wish to post to the list without
> incurring
> a moderation delay.
--
Douglas E. Engert <DEEngert@anl.gov>
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444