FYI also, for when it makes it into a release - the byte range locking support should work against ANY server version, it's only a change to the client-side code.
-- Nathan ------------------------------------------------------------ Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-6679 UMR Information Technology Fax: (573) 341-4216 > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Altman > Sent: Tuesday, August 30, 2005 10:07 AM > To: Lars Schimmer > Cc: [email protected] > Subject: Re: [OpenAFS] ByteRangeLocking in 1.4RC2 > > No. Byte range locking is not in the 1.4 release. > Byte range locking exists on the CVS HEAD and will be released > in a future 1.4 release once it is stable. > > Apparently the CVS HEAD version of the afs-changes file was > published instead of the 1.4 version. > > The correct version is available at > > > /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/afs-change > s-since-1.2.txt > > Jeffrey Altman > > > > > Lars Schimmer wrote: > > Hi! > > > > Just studied the release notes to the 1.4 release. > > There is written: > > Byte-range locking as described in cm_vnodeops.c has been > implemented. > > > > Does that mean, we can now safely edit MS Office Files IN AFS Space > > while all servers/clients are 1.4 versions? > > *hoooray* > > > > Cya > > Lars > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
