From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Manage network links with hotplug?
Date: Mon, 22 Mar 2004 17:44:21 +0000 [thread overview]
Message-ID: <20040322174421.GA15589@kroah.com> (raw)
In-Reply-To: <slrnc5qu32.1f2.joerg@alea.gnuu.de>
On Mon, Mar 22, 2004 at 06:24:24PM +0100, Marco d'Itri wrote:
> On Mar 22, Greg KH <greg@kroah.com> wrote:
>
> > > The major problem is that there is no good way to assign an interface
> > > name to a specific hardware device (but this happens also without
> > > hotplug...).
> > What is wrong with using nameif for this?
> In my experience it just does not work: not all tools recognize the
> modified names.
In my experience, and in Red Hat's and SuSE's experience, nameif works
just fine to bind network adapters to specific MAC address of devices.
As I personally know loads of people using it, and I know of some
developers working on adding some udev-like functions to nameif to
handle pci device names and stuff, I'm pretty sure this is the proper
tool.
thanks,
greg k-h
-------------------------------------------------------
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-03-22 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 11:11 Manage network links with hotplug? Joerg Sommer
2004-03-21 12:39 ` Marco d'Itri
2004-03-22 15:35 ` Greg KH
2004-03-22 17:24 ` Marco d'Itri
2004-03-22 17:44 ` Greg KH [this message]
2004-03-24 11:53 ` Joerg Sommer
2004-03-24 23:14 ` Greg KH
2004-03-25 16:25 ` Gioele Barabucci
2004-03-26 23:02 ` 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=20040322174421.GA15589@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).