On Wed, Jul 05, 2006 at 02:12:04PM -0400, Erez Zadok wrote:
> 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?
There are two posibilities:
1) say: "too bad, that's not supported" (which is basically what we do now)
2) add more code to unionfs to handle the case
This makes me wonder how frequently do people want to do these kind of
complex operations?
Jeff.
--
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like
that.
- Linus Torvalds
_______________________________________________
unionfs mailing list
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
