linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: netdev + callout rules
Date: Thu, 01 Apr 2004 10:13:31 +0000	[thread overview]
Message-ID: <406BEB4B.5030805@suse.de> (raw)

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.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke			hare@suse.de
SuSE Linux AG				S390 & zSeries
Maxfeldstraße 5				+49 911 74053 688
90409 Nürnberg				http://www.suse.de


-------------------------------------------------------
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Ìk
_______________________________________________
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

             reply	other threads:[~2004-04-01 10:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 10:13 Hannes Reinecke [this message]
2004-04-01 13:31 ` netdev + callout rules Kay Sievers
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=406BEB4B.5030805@suse.de \
    --to=hare@suse.de \
    --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).