Using devd to automate wireless | wired network connections
brooks at one-eyed-alien.net
Wed Sep 14 12:46:54 PDT 2005
On Wed, Sep 14, 2005 at 01:38:44PM -0600, Kirk Davis wrote:
> > -----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? 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. 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.
I typicaly just run devd in debugging mode for that. There's also a
named pipe in /var/run/devd.pipe with the input to devd on it so if you
wanted to write a dumping tool, that would be a good target.
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20050914/98852078/attachment.bin
More information about the freebsd-current