Hans Reiser wrote:
I am just coming into the middle of this, so forgive me, but why are
you implementing this above the filesystem layer? It seems like
virtual files should be plugins that the filesystem calls while
resolving its lookups and finding links to the plugin. This means
anyway.
I don't think that making a directory from a file is necessarily a
good idea:
- Some programs will probably break by this (i.e. will not let you cd
into a non-directory
- You cannot distinguish virtual and non-virtual files in this way
(e.g. how do you represent the gunzipped version
Hi,
Here's a new version of the virtual file patch (against 2.4.0-test5),
and the kernel module for avfs/podfuk.
It now does:
- Clean up automatic mounts when parent is umounted
- Clear dcache upon module insert, so virtual files are always found
- Correctly handle virtual files
Hi!
It looks much cleaner than my previous approaches. There seems to be
something strange with usage counts:
pavel@bug:/tmp/cz1_mbrola.tgz#utar$ ls -al
total 88
drwxr-xr-x 2 pavelusers3586 Mar 26 18:43 ./
drwxrwxrwt 38 root root81920 Jul 24 09:57 ../
Miklos Szeredi wrote:
Problems:
- The filesystem will be littered with these loopback mounts. This
should be cleared upon unmount, and possibly when the dcache is
shrunk. There was a similar requirement for new autofs IIRC.
- Creation/removal of virtual files are not handled
Hi!
I've been looking at the possibility of cleanly implementing virtual
files (podfuk/avfs style) with the multiple mount thing in 2.4
kernels. Here is how it would work:
1) There needs to be a global lookup hook in VFS. If a real lookup
fails, the global lookup is invoked. The cached
On Mon, 24 Jul 2000, Pavel Machek wrote:
Hi!
I've been looking at the possibility of cleanly implementing virtual
files (podfuk/avfs style) with the multiple mount thing in 2.4
kernels. Here is how it would work:
1) There needs to be a global lookup hook in VFS. If a real lookup
Hi!
I've been looking at the possibility of cleanly implementing virtual
files (podfuk/avfs style) with the multiple mount thing in 2.4
kernels. Here is how it would work:
1) There needs to be a global lookup hook in VFS. If a real lookup
fails, the global lookup is invoked. The cached lookup
