Looks like there's more confusion than I have time to clear up (sorry!),
but to recap, I arrived here wanting to mount a filesystem that can expose
and modify on-disk paths beneath its mount point. I'm equally thankful for
the solution (openat et al) as I am for the help in articulating the goal.
If you're curious *why* I want such a thing, well, as I've said, I'd like
to write user-space filesystems that leave their contents "in place" after
the FUSE process terminates.
> > Are you confusing the localfs root with its mount point? The former is
> the
> > on-disk directory tree it manages.
>
> The second sentence doesn't make sense to me. "The mount point is the
> on-disk directory tree it manages"? What's "it" here?
"The former" refers to the first of two mentioned things, in this case the
root. ("The latter" could be used to refer to the second.) "It" is the
localfs.
Cheers,
Cameron
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
