From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 01 Apr 2004 13:31:43 +0000 Subject: Re: netdev + callout rules Message-Id: <20040401133143.GA14725@vrfy.org> List-Id: References: <406BEB4B.5030805@suse.de> In-Reply-To: <406BEB4B.5030805@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Apr 01, 2004 at 12:13:31PM +0200, Hannes Reinecke wrote: > Hi all, > > I'm not sure whether I'm following the netdev change for udev. AFAIK > udev has been changed to also handle net requests, so that the interface > name of a new interface can be changed nameif-like within udev. > Ok so far. > > But: What if one assumed that the add net device event will also setup > the interface itself via a call to 'ifconfig' or 'ifup'? > Do we have a callout rule in udev which is run _after_ the device node > (or, in this case, the nameif call) has been run? Yes, there is the /etc/dev.d/ directory. You may look at docs/RFC-dev.d in the current tree. > Otherwise I don't really see much point in running udev for net events, > as our current ifup already uses nameif to rename the interface ... > But who knows, maybe there is something totally obvious which I'd > overlooked. Yes, we do a similar thing, but nameif can only handle MAC addresses while udev can match _any_ attribute along the chain, the device is located. thanks, Kay ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ 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