In message <E1Jp4m0-0004UU-3G@xxxxxxxxxxxxxxxxxxx>, Miklos Szeredi writes: > > Sure, unionfs already does some of it now (and some of it can be recoded > > more cleanly), but I'd like to get rid of much of it if I could -- these new > > path_* helpers make me have to maintain vfsmounts even moreso than before. > > With the words of Al: "that is hogwash". Stacks either maintain > vfsmounts or they don't. There's no middle ground. So, if I wanted to not maintain vfsmounts at all in unionfs, how can I use the proposed new path_* helpers which require vfsmounts? Will there be some other helpers available to perform lower-filesystem operations (e.g., mkdir, create, unlink, etc.) which won't require passing vfsmounts? The "or they don't" is not much of an option when I'm forced to use an API that requires a vfsmount... > Miklos Thanks, Erez. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
