In message <[EMAIL PROTECTED]>, Josef Sipek writes: > > I did consider this issue of someone reading the file after someone > > modified it but before it was committed and I wasn't quite sure how to > > deal with it. You essentially have this problem with any psudofs unless > > they commit every change to a file. You could do something along the > > lines of having a file in there which is a lock and when a person wants > > to modify the fs they cat something to the file (PID,1,...?) and then > > its restricted to access from that person for the time being. > > Nah. Just have the user specify the branch directory, mode and position at > the same time into a special file "add" and have the kernel create the > branch directory with the appropriate contents.
Your method doesn't allow for multiple ops at the same time: what if a user wants to add two branches, delete one, and swap two others, all at once? Erez. _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
