Re: Using devd to automate wireless | wired network connections

In message: <04C71268DFDAA8499EC1A248A44B6A2B34C132_at_Exchange21.EDU.epsb.ca>
            Kirk Davis <Kirk.Davis_at_epsb.ca> writes:
:  
: 
: > -----Original Message-----
: > From: owner-freebsd-current_at_freebsd.org 
: > [mailto:owner-freebsd-current_at_freebsd.org] On Behalf Of Brooks Davis
: > Sent: September 14, 2005 9:54 AM
: > To: Jochen Gensch
: > Cc: freebsd-current_at_freebsd.org
: > Subject: Re: Using devd to automate wireless | wired network 
: > connections
: > 
: > On Wed, Sep 14, 2005 at 11:54:45AM +0200, Jochen Gensch wrote:
: > > Am Mittwoch 14 September 2005 02:41 schrieben Sie:
: > > 
: > > > Have you tried those changes?  If so, are your devices
: > > > actually generating media events?  If not, that has to be 
: > fixed and
: > > > that's a kernel issue.
: > > 
: 
:     Is there any diagnostic tools that can show the messages that get passed
: from the kernel to devd?

devd republishes everything it gets via /var/run/devd.pipe.

: I have though of some other uses for devd where I
: would like to run a script on a device up/down or new device insert but I'm
: not sure if there is an event sent to devd for that.

*ALL* devices that are added to or removed from the system get a devd
event.  It isn't like other systems where you have to add support to
each bus.

: It would be nice to
: have a tool that would show if devd was getting an even for that device.
: This might also help show the devices that do not yet generate media events.

Many don't, that's true :-(.

Warner