Etienne Robillard granted14 at
Wed Aug 20 03:53:07 CEST 2003

Hi Hackers,

on implementing the auth module (currently running on
mach_port_t and all) in idl4 grammar with L4
ipc/syscalls. Question is how the relationship between
mach_port_t would affect l4_threadid_t and folks ?

The following is not currently appropriate for any of
the Hurd/Mach RPC device or L4 syscalls:

module auth { /* this is the generic auth module
implementation for Hurd */ 
interface auth_getids /* generic api for _ids */ 
int l4_ids_t([out] static l4_threadid_t ids_t, [out]
&idarray_t /* some foo here je je */);

This is only a partial implementation of the auth.def
interface - but since the module is so small; it may
be easier to port with l4_* components. It does use
the idl4 fast compiler and is expected to be loaded as
a root_task/clan_ipc ;)

The brackets are for compatibility with DCE/DICE.  



Post your free ad now!
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: auth.idl
URL: <>

More information about the l4-hackers mailing list