There are tons of FUSE client implementations for all sorts of odd things.

Some operations, if not implement at some level, would simply fail.įUSE is not tied to FTP. The finder should not know the difference between sitting on top of a FUSE mounted directory or file and a local file. Remember that ftp goes back to prehistoric days. And, even if modern ftp does, the ftp server being used may not implement them. For example, ftp may not have a chown or chmod facility (I haven't checked). Some functions may be not implemented in the underlying protocol. Mount points using FUSE would work the same as other mount points. So, just as you can mix various file systems on a Mac and the finder does not really know or care, FUSE would simply be a new file system type. For a read on file foo on mount point bar of type cdr, uses the read entry point in the cdr entry in the VFS table. A mount point in the file system points to one of the entries in the VFS table. To back up briefly, each of the basic Mac file system types such as 'Mac Extended', ZFS, DOS, etc, sit in one slot of the virtual file system table. It implements a complete set of virtual file system entry points (which is a lot of entry points).

It ties into the virtual file system level inside the kernel and then sends the requests up to application level processes. I was / am doing a port of it to AIX but that project has not progressed very far.įUSE appears as a file system type in the virtual file system table. I've not used it so take what I say with a grain of salt.

Mac terminal ftp client