Re: selrecord/selwakeup now unusable ?
Re: selrecord/selwakeup now unusable ?
- Subject: Re: selrecord/selwakeup now unusable ?
- From: Terry Lambert <email@hidden>
- Date: Thu, 28 Jul 2005 15:08:34 -0700
On Jul 28, 2005, at 2:26 PM, Christer Bernérus wrote:
Hi.
I'm finally trying to port the Coda file system kernel extension to
Tiger.
Can anyone enlighten me how I'm supposed to do instead of using
selrecord/selwakeup ?
It doesn't seem to be supported anymore. At least the necessary
selinfo structure is not defined in the kernel framework, and if I
try the ugly trick of copying the definition from the xnu source,
that just leads to undefined wait queue structures. This suggests
to me that I should follow another path.
I looked at the fsevents code, but cannot figure out how to use it.
I can't find any documentation or coding example. Help!
Hi Christer;
What problem are you trying to solve that makes you think you need to
directly access selrecord/selwakeup? This is basically the select
mechanism internals.
If you can define the problem, someone can probably give you a way to
solve it that fits into the context of the KPI.
For example, if you are attempting a read-with-timeout, you should
probably llok at the changes that were made to the published SMB
implementation when smb/kernel/netsmb/smb_trantcp.c lost access to
the select internals.
That was only intended as an example - if it's not applicable, and
you can tell us what you are doing, we could probably come up with a
better example of code for you.
-- Terry _______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden