[openbeos] Re: Status of the Kits

François Revol <revol@xxxxxxx> wrote:
> En réponse à Tyler Dauwalder <tyler@xxxxxxxxxxxxx>:
> 
> 
> > Probably 90-95% of the Storage Kit API as described in the BeBook 
> > is 
> > implemented via POSIX calls. The remaining 10-5% requires support 
> > from
> > 
> > our own kernel. We'll also rewrite the backend of everything we 
> 
> What system calls did it need already ?
> I had once to guess some, I put them in:
> http://wiki.bebits.com/page/UndocumentedSyscalls

Node locking was one of the missing things. _k[un]lock_node_() were 
brought up on bedevtalk some time ago. I wonder if their return value 
is int (+ errno) though. Node locking is still not implemented, but 
it's not really a pressing issue.

Then there's:

#define         WFSSTAT_NAME    0x0001
int _kwfsstat_(dev_t device, fs_info *info, long mask);
 
I'm not sure whether the prototype is correct, but at least, setting 
volume names works fine.

I still don't know, how _kstart_watching_vnode_() and 
_kstop_watching_vnode_() look like. watch_node() and stop_watching() 
are mapped to them, so I have a rough idea, but my x86 assembler skills 
are rather rudimentary, so I had to go with try and error, which I 
weren't really motivated to do. Node monitoring is a bit more of an 
issue, since we can't use the libbe version of watch_node()/
stop_watching(), when we also link against libopenbeos. Currently it is 
only needed in one place in the registrar (I crudely worked around by 
running a separate application), which is going to go away soon, 
anyway. Don't know about the app server, though.

CU, Ingo

Other related posts: