From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: netdev + callout rules
Date: Thu, 01 Apr 2004 21:42:58 +0000 [thread overview]
Message-ID: <20040401214258.GA30479@kroah.com> (raw)
In-Reply-To: <406BEB4B.5030805@suse.de>
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?
> 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.
You are correct. Here's a tiny script that I placed in
/etc/dev.d/network/ that will call the hotplug scripts again with the
new network name, if udev renames the device. I'll be adding it to the
udev tree for it to install, as it is pretty useful.
Even tested it on my laptop, so now I can run with renamed network
devices all of the time :)
thanks,
greg k-h
#!/bin/sh
#
# Script to ensure that any network device that udev renames
# still gets the hotplug script run with the proper name.
#
# Released under the GPL v2
#
# Copyright (C) 2004 Greg Kroah-Hartman <greg@kroah.com>
#
# See if we really did rename this device.
if [ "$INTERFACE" = "$DEVNAME" ]; then
exit 0
fi
# ok, we have renamed this device, so let's set $INTERFACE to the new name
# and call the network hotplug script to handle it properly...
INTERFACE=$DEVNAME
export INTERFACE
if [ -f /etc/hotplug.d/default/default.hotplug ]; then
/etc/hotplug.d/default/default.hotplug net
fi
-------------------------------------------------------
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_id\x1470&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
prev parent reply other threads:[~2004-04-01 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 10:13 netdev + callout rules Hannes Reinecke
2004-04-01 13:31 ` Kay Sievers
2004-04-01 21:42 ` Greg KH [this message]
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=20040401214258.GA30479@kroah.com \
--to=greg@kroah.com \
--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).