In message: <[EMAIL PROTECTED]>
Robert Watson <[EMAIL PROTECTED]> writes:
:
: On Tue, 29 Jul 2003, Daniel C. Sobral wrote:
:
: > > You could add kevents for interface arrival and departure, and
: > > add a kqueue to the dhcpd to catch the arrival/departure events,
: > > and then just act on them.
: >
: > Instead of just adding the stuff to devd?
:
: Currently, devd is in the business of dealing with attachment and removal
: from the hardware management subsystem.
currently, that's true.
: Network subsystem events, such as
: "interface has arrived" are semantically different, but "close enough" in
: many cases.
I've been pondering making devd grok such events, as well as other
power events. Eg, it will be a place that acpi could route acpi
events to replace apm.
: In the past, routing sockets have been the means by which
: topology-relevant changes are announced to the user processes. More
: recently, kqueue has permitted monitoring of a plethora of event types. I
: think there's a decent argument for a neteventd, perhaps integrated as a
: thread into devd, listening on network events rather than device
: attach/detach events.
I think that would be a good idea.... Don't know if there's a
'thread' or a virtual thread-like thing.
: The only real problem is that it would be very nice
: if the DHCP client code were available in a library so it could be linked
: into a network event manager.
It would make things a lot easier.
Warner
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
