netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: is it a backwards compatability catch-22?
Date: Mon, 24 Apr 2006 17:38:16 -0700	[thread overview]
Message-ID: <444D6F78.9080309@hp.com> (raw)
In-Reply-To: <20060424165407.202a86f4@dxpl.pdx.osdl.net>


> The udev stuff runs after the device has already chosen it's default name.
> It has to, it's part of the hotplug infrastructure, and we don't want
> to depend on usermode to define the name.  Just choose some other
> convention "eth_0"  or something like that.

Is that because adding another NIC at a later time might cause it to 
grab ethN out from under what I'm trying to do with udev?

rick jones

  reply	other threads:[~2006-04-25  0:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24 23:47 is it a backwards compatability catch-22? Rick Jones
2006-04-24 23:54 ` Stephen Hemminger
2006-04-25  0:38   ` Rick Jones [this message]
2006-04-25 16:09     ` Jesse Brandeburg
2006-04-25 18:34       ` Rick Jones
2006-04-25 19:10 ` Michal Schmidt

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=444D6F78.9080309@hp.com \
    --to=rick.jones2@hp.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.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).