From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: write_net_rules all_interfaces
Date: Sun, 19 Aug 2007 13:22:08 +0000 [thread overview]
Message-ID: <20070819132208.GA22173@bongo.bofh.it> (raw)
In-Reply-To: <46C83E1E.6060100@kadzban.is-a-geek.net>
On Aug 19, Bryan Kadzban <bryan@kadzban.is-a-geek.net> wrote:
> So this was removed in udev-114, in favor of a manual loop like:
>
> for i in /sys/class/net/* ; do
> echo "add" >$i/uevent
> done
>
> or something similar. At least, that's what I gather from the commit
> message; I'm not quite sure if it's right or not.
>
> This is fine, mostly.
Not so fine actually, because this will cause spurious events which may
have unwanted side effects.
I agree that trying to duplicate the rules in the shell script is not
going to work in the long period, but the proposed solution has its own
set of problems as well.
So far my plan is to create temporary rules which will disable the RUN
rules while these events are triggered, but I still need to think about
the details.
> The problem comes in when installing another
> system into (and inside) a chroot from a running host, as we do in LFS.
Debian has a similar problem, but I have not found a solution yet.
I do not consider starting a second udevd a valid solution.
--
ciao,
Marco
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-08-19 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 12:57 write_net_rules all_interfaces Bryan Kadzban
2007-08-19 13:22 ` Marco d'Itri [this message]
2007-08-20 0:02 ` Kay Sievers
2007-10-28 22:20 ` Marco d'Itri
2007-10-28 23:32 ` Bryan Kadzban
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=20070819132208.GA22173@bongo.bofh.it \
--to=md@linux.it \
--cc=linux-hotplug@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).