From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Mon, 18 Oct 2004 18:44:23 +0000 Subject: Re: cleanup netif handling and netif-dev.d/ events Message-Id: <20041018184423.GC7487@vrfy.org> List-Id: References: <20041018181713.GA7487@vrfy.org> In-Reply-To: <20041018181713.GA7487@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Mon, Oct 18, 2004 at 11:28:06AM -0700, Greg KH wrote: > On Mon, Oct 18, 2004 at 08:17:13PM +0200, Kay Sievers wrote: > > Here we supress the dev.d/ execution if we didn't change a network > > interface's name with a rule. This should solve the issue of two > > running dhclients for the same interface, cause the > > /etc/dev.d/net/hotplug.dev script that fakes the hotplug event runs > > with every udevstart for every interface and fakes a second identical > > hotplug event on bootup. > > Huh? /etc/dev.d/net/hotplug.dev should contain the following three > lines at the beginning to prevent this: > # See if we really did rename this device. > if [ "$INTERFACE" = "$DEVNAME" ]; then > exit 0 > fi I don't think that $INTERFACE is available to the dev.d/ scripts. I will look into the hotplug "rename" event, if the uevent patches reached the mainline kernel :) > right? What distro doesn't do this? > > Do we want to hardcode this logic inside udev itself now? No, if we don't create a node, or don't rename a netif, we just don't call dev.d/ now. Kay ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ 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