From: Johannes Berg <johannes@sipsolutions.net>
To: Alexey Toptygin <alexeyt@freeshell.org>
Cc: netdev@vger.kernel.org
Subject: Re: sysfs vs. d80211 configuration
Date: Tue, 15 Aug 2006 09:41:09 +0200 [thread overview]
Message-ID: <44E17A95.2040006@sipsolutions.net> (raw)
In-Reply-To: <Pine.NEB.4.64.0608142302560.21364@otaku.freeshell.org>
Alexey Toptygin wrote:
> Why not have the tool create a monitor interface, open it, and fork;
> the child drops privileges and does the reading, and the parent
> wait(2)s for the child and removes the interface once it has collected
> the child?
Good point, that'll work. Then again, I want this to run on really tiny
architectures and I'm thinking some of them might not have fork(), just
vfork(). Hmm.
johannes
next prev parent reply other threads:[~2006-08-15 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 13:10 sysfs vs. d80211 configuration Johannes Berg
2006-08-14 23:05 ` Alexey Toptygin
2006-08-15 0:07 ` Mike Kershaw
2006-08-15 7:41 ` Johannes Berg [this message]
2006-08-15 10:02 ` Johannes Berg
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=44E17A95.2040006@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexeyt@freeshell.org \
--cc=netdev@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).