From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Sun, 19 Aug 2007 13:22:08 +0000 Subject: Re: write_net_rules all_interfaces Message-Id: <20070819132208.GA22173@bongo.bofh.it> List-Id: References: <46C83E1E.6060100@kadzban.is-a-geek.net> In-Reply-To: <46C83E1E.6060100@kadzban.is-a-geek.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Aug 19, Bryan Kadzban 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