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-changes-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
begin:vcard fn:Jeffrey Altman n:Altman;Jeffrey org:Secure Endpoints Inc. adr:;;255 W 94TH ST PHB;NEW YORK;NY;10025;United States email;internet:[EMAIL PROTECTED] title:President tel;work:+1 212 769-9018 x-mozilla-html:TRUE url:http://www.secure-endpoints.com version:2.1 end:vcard
smime.p7s
Description: S/MIME Cryptographic Signature
