On 17 October 2012 18:04, Jakub Jermar <[email protected]> wrote: > On 15.10.2012 22:07, Jiří Zárevúcky wrote: >> Also, right-hand part of the picture was my attempt to explain how >> bindings (my replacement for mount points) work. I ran out of space on >> that one, so it’s not really helpful, sorry. > > Does your bind tree reflect the entire topology of all bound file > systems and is it locally stored in VFS? I am just curious because > currently, this information is distributed across VFS and the > participating file systems. >
Yes to both. The bind tree is a "backbone" for the tasks namespace. Since tasks are intended to have independent namespaces (and thus private mounts), it is not possible to let participating file systems manage mount points. Which also means the "mounts" are not really true mounts, but rather overlays that bind the filesystem root (actually an arbitrary node) to a textual path (rather than a directory in a filesystem). When you combine that with unionfs style handling, it's actually quite neat I think. _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
