| S. Shafer and M. R. Thompson. The SUP Software Upgrade Protocol. Unpublished notes available by ftp from mach.cs.cmu.edu:/mach3/doc/unpublished/sup/sup.doc |
....file being updated 8 while being read exists independently of our work, and our work does not increase the danger. 6 That is, they are exported as read only to some hosts, although they might be exported as read write to others. 7 An example of careful update is provided by the SUP utility [22]. 8 That is, updated by a host to which the file system is exported read write. We allow for a replacement file system to be itself replaced. This raises the possibility of creating a chain of replacement file systems. Switching vnodes from the old file system to its replacement limits this ....
S. Shafer and M. R. Thompson. The SUP Software Upgrade Protocol. Unpublished notes available by ftp from mach.cs.cmu.edu:/mach3/doc/unpublished/sup/sup.doc
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC