From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: netdev + callout rules
Date: Thu, 01 Apr 2004 13:31:43 +0000 [thread overview]
Message-ID: <20040401133143.GA14725@vrfy.org> (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?
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_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
next prev parent reply other threads:[~2004-04-01 13:31 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 [this message]
2004-04-01 21:42 ` Greg KH
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=20040401133143.GA14725@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.