Aucb.606
fa.editor-p
utcsrgv!utzoo!decvax!ucbvax!C70:editor-people
Fri Mar 5 16:42:00 1982
File locking with NLS
>From KLH@MIT-AI Thu Mar 4 12:05:37 1982
The NLS (now AUGMENT) system on 10X/20X handles the file locking
problem rather well. Basically, NLS files are always readable
(subject to usual protection bits, etc); if someone else is working on
a file that you want to read, you are allowed to look at it, but you
are also notified that "File FOO.NLS is being modified by HACKER", and
you are not allowed to see the mods that HACKER is making, until that
user has explicitly "updated" the file, at which point everything is
merged in. From the viewpoint of HACKER, nothing unusual is going on;
the file is not considered to be modified until a user actually makes
some change to it, and the modifier is always looking at the modified
version. One unusual aspect of the implementation is that the
"partial copy" (containing mods) can stay around as long as HACKER
wants (weeks or months, across logouts/crashes/etc), thus
write-locking the original file until the updates are finished.
Note that the mechanism is implemented in a single user program,
rather than the operating system. It does depend on shared
page mapping.
I don't have time to explain the workings in more detail, so if people
have questions I hope that there is another AUGMENT user on this list
who will volunteer to answer them.
-----------------------------------------------------------------
gopher://quux.org/ conversion by John Goerzen <
[email protected]>
of
http://communication.ucsd.edu/A-News/
This Usenet Oldnews Archive
article may be copied and distributed freely, provided:
1. There is no money collected for the text(s) of the articles.
2. The following notice remains appended to each copy:
The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996
Bruce Jones, Henry Spencer, David Wiseman.
