Whole document tree
Chapter 6. Virtual File System (VFS)
A VFS describes a tree structure of files and directories. An example of VFS is a zip file : a zip file contains files in organized directories.
Each VFS file type needs a program in order to retrieve its content. For the ".zip" files, this program could be "unzip" or any other one which is able to understand the file format.
Scanning the content of VFS is longer because GTKtalog must call an external program. Once scanned (either in "Scan VFS" or "Full scan VFS" mode), the VFS is shown as a normal directory. You can notice it's a VFS by the color of the icon (green by default). You can browse the subdirectories, of the VFS and interact with them. After a scan, the information field of a file inside a VFS is empty.
In the case of a nested VFS, the VFS inside the first one is not scanned and is stored as a normal file.
Right clicking on a directory within a VFS on the left frame of GTKtalog pops up a special VFS menu :
Edit VFS : Same as edit directory or edit file.
VFS mode :
If the archive file was scanned in "Scan VFS" mode, you'll get the question : "Erase the virtual file system and only keep the archive file" ?.
Answering yes will delete the VFS and only keep the archive file as a standard file in your catalog.
Answering no makes no changes.
If the archive file was scanned in "Full scan VFS" mode, you will get the question : "Convert this virtual file system and keep only the names".
Answering yes will convert the "Full scanned" VFS to a "Scanned VFS" (the file size and dates are dropped).
Answering no will delete the VFS and only keep the archive file as a standard file in your catalog.
Answering cancel backs out. No changes.