[Design] NS Future Storage: A WinFS-Inspired FS with Dual-Mode Semantics and Pseudo-VFS

[NeuroSamaOS]

(I'm sorry, I have difficulty communicating with people)
(This topic uses Google Translate)
NSFS (Neuro-Sama Future Storage) is a Future Storage application inspired by WinFS.
It uses tags/metadata/attributes or paths to search for files, solving WinFS's path compatibility issues.
It combines the pseudo-VFS functionality of FDFD (Freedom Disk Four Dimensions – I don't know why it has such a catchy name, lol) (ln creates an lnk file(Symlink/Shortcut) whose content is a path, lol; you can also use ln for drive letters (FDFD uses numbers 0-255 for drive letters)).
That's all I can think of for now. Bye!

[iansjack]

Talk is cheap. Show me the code.

[NeuroSamaOS]

So I'm going to start writing the implementation code for NSFS. While talk is cheap, I think I still need to plan and talk.

[AnotherIdiot]

(I'm sorry, I have difficulty communicating with people)
(This topic uses Google Translate)
NSFS (Neuro-Sama Future Storage) is a Future Storage application inspired by WinFS.
It uses tags/metadata/attributes or paths to search for files, solving WinFS's path compatibility issues.
It combines the pseudo-VFS functionality of FDFD (Freedom Disk Four Dimensions – I don't know why it has such a catchy name, lol) (ln creates an lnk file(Symlink/Shortcut) whose content is a path, lol; you can also use ln for drive letters (FDFD uses numbers 0-255 for drive letters)).
That's all I can think of for now. Bye!

Could you explain in more detail how it works, so it uses symlinks/shortcuts which are just .lnk which just contain the path to the file, which makes enough sense I suppose. And each file has a "tag" which makes it easier to search for files solving indexing/path compatibility issues with WinFS, but how does it actually store files and what does its structs (in theory) look like? Would you version structs just to make things easier to mount and develop with?