Scott Aitchison wrote:
Thanks Darren.
How is this being addressed? Are hooks going to be prioritized when
queued? Any idea when this will be included in a full Solaris release?
A simple priority mechanism has already been rejected by the
Solaris architecture committee (PSARC) so that won't be what
is implemented. We thought about doing a dependency style
solution (including prototype) but at the time we believed
that this would just lead to further delays with PSARC so it
was scrapped.
Instead, you should expect to see something that works using
a model based on defining an order or relationship between who
gets called when for a particular event.
When will it appear in a full Solaris release? Well, at this
point in time there are no plans for it to even appear in a
developer release so I can't even begin to speculate about when
it will appear in a main release.
The type of architecture I'm thinking of using will involve
putting all of the dependency information in SMF (no config
files), some programs/scripts to manage that (rather than
require people to use svc*) and build a new SMF service that
runs early in the boot sequence to apply this to the kernel.
If you need to change the hooks infrastructure sooner rather
than later to support what you want to do, the way to go would
be to use Solaris Express and source code from Open Solaris
and develop your own mechanism. At some point if/when you're
happy with that, you could present that work here and we could
discuss if/how to include that in Solaris. If I can, I'd be
happy to sponsor your work on that.
Darren
On 11/23/06, *Darren Reed* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Scott Aitchison wrote:
>Hi all.
>
>I have a question about something I read in the pfhooks design
specification.
>
>I'm looking into using pfhooks for a project, however I noticed
under Section 3.5 (Packet Interception), it mentions that the
implementation will only support a single callback being
registered at a single time.
>
>I'm interested in NH_PHYSICAL_IN and NH_PHYSICAL_OUT, but if I'm
using IPFilter as well (which I believe is being ported to use the
same hooks), am I out of luck? If IPFilter hooks onto the same
events, if my module going to fail when calling net_register_hook()?
>
>
Correct :(
This will be addressed in the new year.
Darren
--
Scott Aitchison
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
http://www.flickr.com/photos/scottaitchison
_______________________________________________
networking-discuss mailing list
[email protected]
