From: David Goodenough <david.goodenough@btconnect.com>
To: linux-wireless@vger.kernel.org
Subject: does the creation of a mesh interface trigger a udev event?
Date: Thu, 27 Oct 2011 10:46:04 +0100 [thread overview]
Message-ID: <201110271046.04592.david.goodenough@btconnect.com> (raw)
When I create a mesh interface:-
iw dev wlan0 interface add mesh0 type mp ...
does a device creation event appear through udev? Similarly while
the creation of wlan0 for a wireless card does create such an event,
do the monitor interfaces and phy's also create such events?
As far as I can see they do not, but I may be wrong - I may just be
listening for them wrongly. If they do, any clues as to how to spot
them?
I ask for two reasons:-
1) It would seem consistent if they did.
2) For a configuration system like the one Debian uses, it is those
events that cause configuration to happen and so it would be easier
to configure things like a mesh network if the events occur.
David
reply other threads:[~2011-10-27 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201110271046.04592.david.goodenough@btconnect.com \
--to=david.goodenough@btconnect.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).