Re: [AVFS] Problems with fork, Questions about avfs

Hi,

On 12-Feb-2005 Miklos Szeredi wrote:
> My feeling is that making it work for local and virtual files should
> make it less complex not more so.  But of course I may be wrong.

I changed the code so segment_len will now check with another function
is the next segment describes a local file. This way parse_path is
almost untouched. I currently trying to add the test to virtual files
to only enter the next avfs hierarchy if a file containing the magic
char is not present in the current avfs mount.
Is there a easy way to call av_file_getattr? It looks like I need a
vfile which itself needs a ventry which the function currently tries to
build.

If it is possible to call some stat function for the current avfs
(ps->ve->mnt->avfs) and only giving the rest of ps->path then it is
easy to add this test to the new function segment_islocal.

If this is not possible then I would go with your solution and just
testing at the beginning of parse_path for local files. Although we
cannot test for symlinks (remember followsymlinks code in parse_path)
the lstat will fail for the first symlink to a virtual file. Of course
this way we cannot support the magic char in virtual files.
MC itself also doesn't support magic characters in virtual filename
although it requires complete vfs name (#utar... instead of # shortcut).

If we can find a way to call avfs->stat we can support this but it
wouldn't hurt much if not.

Best Regards,

Ralf Hoffmann

-- 
Homepage: http://www.boomerangsworld.de
E-Mail: Ralf Hoffmann <[email protected]>
  english or german



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click