The VFS component contains a set of executable files, libraries and description files that let you use file systems and/or a network stack combined into a separate Virtual File System (VFS) process. If necessary, you can build your own VFS implementations.
VFS libraries
The vfs CMake package contains the following libraries:
vfs_fs – contains the defvs, ramfs and romfs implementations, and lets you add implementations of other file systems to VFS.vfs_net – contains the defvs implementation and network stack.vfs_imp – contains the sum of the vfs_fs and vfs_net components.vfs_remote – client transport library that converts local calls into IPC requests to VFS and receives IPC responses. vfs_server – server transport library of VFS that receives IPC requests, converts them into local calls, and sends IPC responses.vfs_local – used for statically linking the client to VFS libraries.VFS executable files
The precompiled_vfs CMake package contains the following executable files:
VfsRamFsVfsSdCardFsVfsNetThe VfsRamFs and VfsSdCardFs executable files include the vfs_server, vfs_fs, vfat and lwext4 libraries. The VfsNet executable file includes the vfs_server, vfs_imp and dnet_imp libraries.
Each of these executable files have their own default values for arguments and environment variables.
If necessary, you can independently build a VFS executable file with the necessary functionality.
VFS description files
The directory /opt/KasperskyOS-Community-Edition-<version>/sysroot-aarch64-kos/include/kl/ contains the following VFS files:
VfsRamFs.edl, VfsSdCardFs.edl, VfsNet.edl and VfsEntity.edl, and the header files generated from them, including the transport code.Vfs.cdl and the generated Vfs.cdl.h.Vfs*.idl and the header files generated from them, including the transport code.