Hi,

I am preparing to porting NTFS-3G for my embedded project base on ucos.
As my understanding so far, it seems that the FUSE API such as fuse_lib_read, fuse_lib_write and so on are not needed.
And I can use NTFS-3G API such as ntfs_fuse_mkdir, ntfs_fuse_unlink and so on directly.
The VFS interface is the wrapper of the NTFS-3G API.
For example, the VFS layer function of my platform VFS_opendir can call ntfs_fuse_opendir directly instead of calling fuse_lib_opendir.
Am I right?
Thanks for any advice.

Regards,
Ryan

I mean, what should I do to deal with FUSE?
For I don't need the user space file system, and I don't need the realization of the kernel FUSE module.
But I found the ntfs-3g API and fuse functions are mixed together, do I have the chance to extract the ntfs-3g api for my purpose?

Hi,


So, throw them away.

You probably can, but you have to fill the gap between your vfs and ntfs-3g. Also note there are two api's to ntfs-3g (ntfs-3g and lowntfs-3g), select the one which is the most similar to what your vfs expects.

Regards

Jean-Pierre

Thanks for your reply, jean. I probably know how to do.