Recent Features
| |||||||||||||
Unioning file systems: Architecture, features, and design choicesUnioning file systems: Architecture, features, and design choicesPosted Mar 19, 2009 9:07 UTC (Thu) by michaeljt (subscriber, #39183)Parent article: Unioning file systems: Architecture, features, and design choices
Is it possible to provide a generic layer in the kernel that union filesystems/stacking filesystems/logical volume management could be built on top of? It seems to me that any two implementations of one of these are likely to have quite a bit in common, not least the problems that they have to deal with, as pointed out by this article. That would also fit in with the *nix "separate mechanism and policy" approach.
(Log in to post comments)
Unioning file systems: Architecture, features, and design choices Posted Mar 20, 2009 17:06 UTC (Fri) by arnd (subscriber, #8866) [Link]
The "union mounts" approach by Jan Blunck et.al. does the implementation
in the common vfs code and requires only minimal changes in the top mounted file systems that get used for writable branches, in order to implement features like whiteouts.
|
|||||||||||||