Bereits angekündigt, aber heute über openafs-announce gekommen.
- Production Version for Windows
- Test Version for other platforms
1.5.62 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.62 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.62 Windows client is fully compatible with all AFS server versions.
[Quelle: Jeff via openafs-annouce]
OpenAFS
Releases of OpenAFS for Windows prior 1.5.62 may fail to store data
to file servers. There are two issues that are addressed in the
1.5.62 release.
[Quelle: Jeff via openafs-info]
Es handelt sich um zwei Probleme, die allerdings im 1.5.62-Release behoben wurden:
- Failure to Store Portions of Unaligned Writes
- Failure to Store Data to File Servers Lacking Large File Support
There are no workarounds to these problems other than upgrading:
- the Windows client to the OpenAFS 1.5.62 or later release, or
- upgrading all file servers to the OpenAFS 1.3.70 or later release
[Quelle: Jeff via openafs-info]
Mehr Informationen im Archiv der Mailing-Liste.
OpenAFS, Windows
Secure Endpoints is now offering a Microsoft Symbol Server for OpenAFS for Windows symbols and executables.
The address is http://www.secure-endpoints.com/symbols/.
This symbol server contains binaries and symbol files for every release of OpenAFS for Windows from 1.4.0 to present (including beta builds). To use the symbol server include it the URL in the symbol search path just as you do with Microsoft’s Symbol Server.
[Quelle: Jeff via openafs-win32-devel]
OpenAFS, Windows
Zur besseren Übersicht – wenn ich meine Logs richtig interpretiere wird zu viel nach der Thematik gesucht – hier meine drei Artikel zum Thema IPv6 auf Clients aktivieren nochmals als Übersicht:
Vielleicht erspare ich so dem ein oder anderen Besucher die Suche. 
Apple, IPv6, Windows
Please advise your help desk staff to be on the lookout for a sudden
increase in complaints about OpenAFS for Windows not working.
The symptoms are that \\AFS is inaccessible and an examination of the
%windir%\temp\afsd_init.log file indicates a memory mapping failure when
attempting to load the AFSCache file. This problem is likely to affect
any user of OpenAFS for Windows on 32-bit Windows with iTunes installed
that set their cache size to be larger than 500mb.
The problem:
Apple updated the Bonjour distribution as part of the most recent iTunes
update. Included in the distribution is a file called mdnsNSP.dll which
is inserted into the process memory space of every application on the
system that makes use of the WinSock APIs. This DLL permits Bonjour
discovery services to be used as a DNS replacement automatically. Apple
set an image base of (16080000 to 160A4FFF) which is smack in the middle
of the 32-bit process data range instead of using a value around
60000000 as recommended by Microsoft.
The work around:
The Microsoft SDK provides a tool called rebase.exe which is used by
developers to modify the base address of a DLL. The following
operations can be used to move mdnsNSP.dll to the correct location in
memory.
cd to c:\program files\bonjourrename mdnsNSP.dll to mdnsNSP.dll.inusecopy mdnsNSP.dll.inuse to mdnsNSP.dllrebase -d -b 0x60000000 mdnsNSP.dll
The next time the OpenAFS for Windows service is started the dll will be
loaded into the correct range in memory.
Unfortunately, it is likely that the next iTunes update will break this
again. End users are also unlikely to have access to the rebase.exe
command.
The command “dumpbin /headers mdnsNSP.dll” can be used to determine the
image base.
The affected version of mdnsNSP.dll is 1.0.6.2.
[Quelle: Jeff via openafs-info]
Apple, OpenAFS, Windows
Linux, MacOS X – bleibt ja eigentlich nur noch Windows.
Teredo ist bei Vista bereits installiert, jedoch abgeschaltet. Bei Windows XP muß der Dienst erst installiert werden, aber das ist auch kein Problem und die zwei Minuten sind weiterhin schaffbar.
Der Weg auf Windows XP:
ipv6 install
netsh interface ipv6
set teredo type=client
Der Weg auf Vista und Windows 7 (nicht getestet):
netsh interface ipv6
set teredo type=client
Bitte bedenken: Ihr hängt damit ein Windows ungefiltert ans Internet. Anti-Virus, Firewalls – Ihr kennt das ja, bitte nicht vernachlässigen. Wir haben schon mehr als genug Spam-Schleudern im Netz.
IPv6, Windows
