On Mon, 16 Feb 2004, Alan Altmark wrote: > Your exclusive-write copy does not become the "real" copy until you save > it (per the book) by writing to /save, wherein Linux will issue the DEFSEG > and SAVESEG for you when you subsequently close the DCSS file.
By writing *what* to /save? Random bytes? A "1"? The text "save"? And when you say "subsequently close the DCSS file", do you mean unmount the mounted FS that I happen to have there? The "file" is a block device, right? So does closing of that constitute the signal to the driver to re-save the segment? These are probably FAQs which would be in the doc. I don't at all mean to complain that the code is there before the doc. I'm *awfully* glad to have the code now! ;-) > Everyone using the segment must then reload it to get the updated copy. > Until they do, they will be looking at the old copy (which is now class P, > pending purge). Reloading is by re-IPLing or by purging and adding the > segment again. Does the v-machine need Class E privs or NAMESAVE? (Or will either of those suffice?) -- R;
