On Dec 17, 2007, at 5:56 AM, Miklos Szeredi wrote:
>> I think I have what it takes to get fuse working on AIX. I plan to
>> start on it this weekend. It seems like I should have it limping
>> along by the end of the holidays.
>> Much of it will be from scratch but I want to keep the user level
>> API. So far, I have not seen that documented. I may be looking in
>> the wrong place(s).
> Which API? The kernel/user interface is rather poorly documented. On
> the other hand the library API used by most apps is pretty well
> documented in the header files.
> Also the low-level library API is quite close to the kernel interface,
> so that can give hints about the raw kernel API.
> Leaving out the raw API and just implementing one of the libray API's
> is also an option, and it's that the NetBSD guys did (librefuse).
The API I want to keep is the one that sshfs, etc, uses which I assume
is the same API that the Perl, Ruby, etc sit on top of.
Keeping what I think you are calling the raw API would be nice too but
I think AIX is so different, that that may not be possible.
I'm making slow progress in understanding all this. Plus, I got side
tracked this weekend so I didn't dig as deep in to it as I wanted to.
I don't have a Linux machine and I know nothing about Linux. I think
I'm going to pull over the Mac stuff and at least get a feel for how
it works from a user's perspective.
There are concepts which are not defined yet (to me). Why is /dev/
fuse needed? And what is the "control file system" (I may have
screwed up that term) used for?