mirror of
https://git.openafs.org/openafs.git
synced 2025-01-31 13:38:01 +00:00
STABLE14-windows-notes-20051008
latest updates
This commit is contained in:
parent
7b5ebd2f69
commit
7162367f5c
@ -1,3 +1,24 @@
|
||||
Post 1.4.0 revisions:
|
||||
* Byte Range Locking support has been added. Architectural documentation
|
||||
is located within src/WINNT/afsd/cm_vnodeops.c. Best efforts are
|
||||
made to enforce Windows mandatory locking model using locally managed
|
||||
byte range locks with full file locks obtained from the file server.
|
||||
Read-only volumes provide the user with an implied locking privilege.
|
||||
Read-write volumes require that a user be granted the locking privilege
|
||||
in order for a lock to be obtained. As most Windows applications use
|
||||
Shared file access modes, they require the ability to obtain locks in
|
||||
order to access files.
|
||||
|
||||
Since 1.4.0 rc6: 1.4.0 rc7 released (8 Oct 2005)
|
||||
* The MSI installer now has a new Product ID for each build. This
|
||||
is to allow for automated upgrades. The Upgrade ID is remaining
|
||||
constant.
|
||||
|
||||
* Volumes that were cached and then subsequently were salvaged,
|
||||
moved or otherwise taken temporarily offline (as opposed to being
|
||||
busy) would become unreachable. A distinction is now made between
|
||||
a volume being offline and a server being down.
|
||||
|
||||
Since 1.4.0 rc5: 1.4.0 rc6 released (2 Oct 2005)
|
||||
|
||||
* Fixed several AFS Shell Extension issues:
|
||||
|
Loading…
x
Reference in New Issue
Block a user