| Document | Description |
|---|---|
| ../README.md | Project overview, features, quick start, build instructions, benchmarks |
| ARCHITECTURE.md | Internal architecture, design decisions, I/O path, backend interface, QEMU details |
| lkl-servers.md | LKL file servers (anyfs-ksmbd + anyfs-nfsd): usage, kernel config, NFSv4, pynfs |
| anyfs-fuse.md | Native Linux LKL build and anyfs-fuse debugging notes |
| anyfs-winfsp-plan.md | WinFSP port: feasibility analysis and gap survey |
| winfsp-windows-fuse-plan.md | WinFSP port: step-by-step implementation plan |
| win32-cross-compile.md | Cross-compiling the whole stack for Windows i386 from Linux |
| distribution.md | Build, packaging, and runtime-dependency matrix for Linux/Win32/Win64 releases |
| ts-packages.md | TypeScript / browser packages (@anyfs/core, react, trees, native) and demos |
All documentation is in English.
- LKL (Linux Kernel Library): runs actual Linux kernel filesystem code as a userspace library.
- Backends: pluggable block I/O layers (
raw/gio/qemu) behind a singleanyfs_backend_opsinterface. - Synchronous I/O only: every backend
request()runs on the LKL virtio request path; async was evaluated and rejected (see ARCHITECTURE.md §7). - Thin C API:
include/anyfs.hexposes four functions (init/halt + disk add/remove); higher-level frontends use LKL syscalls directly. host_proxydata path: the ksmbd/nfsd servers do not route client traffic through libslirp; a host-side userspace TCP splice connects each accepted host connection to an LKL socket on127.0.0.1.