public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Carter <eli.carter@inet.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Russell King <rmk@arm.linux.org.uk>,
	"Randy.Dunlap" <rddunlap@osdl.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: The magical mystical changing ethernet interface order
Date: Thu, 08 May 2003 16:43:57 -0500	[thread overview]
Message-ID: <3EBACF9D.5070501@inet.com> (raw)
In-Reply-To: 20030508193245.GA26721@bougret.hpl.hp.com

Jean Tourrilhes wrote:
[snip]
> Randy.Dunlap wrote :
> 
>>An alternative is to use 'nameif' to associate MAC addresses with
>>interface names.  See here for mini HOWTO:
>>
>>  http://www.xenotime.net/linux/doc/network-interface-names.txt
> 
> 
> 	Currently this feels like a kludge, because not fully
> inegrated, but goes in the right direction.
> 	Actually, it's pretty funny that the original Pcmcia package
> got it right since the beggining (and Win2k as well), but
> distributions took a step backward from that when integrating Pcmcia.
> 	My belief is that configuration scripts should be specified in
> term of MAC address (or subset) and not in term of device name. Just
> like the Pcmcia scripts are doing it.
> 	And let's go the extra mile : ifconfig should accept a MAC
> address as the argument instead of a device name. And in the long
> term, just get rid of device name from the user view.

Some network devices do not have a mac address on power-up and must be 
supplied one.

Eli
--------------------. "If it ain't broke now,
Eli Carter           \                  it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------


  reply	other threads:[~2003-05-08 21:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 19:32 The magical mystical changing ethernet interface order Jean Tourrilhes
2003-05-08 21:43 ` Eli Carter [this message]
2003-05-08 22:19   ` Jean Tourrilhes
2003-05-08 21:46 ` Alan Cox
2003-05-08 23:23   ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  7:42 Thomas Hood
2003-05-08 23:38 Ray Lee
2003-05-09 12:41 ` Dick Streefland
2003-05-09 14:33 ` Mr. James W. Laferriere
2003-05-07 13:14 Russell King
2003-05-07 15:18 ` Dick Streefland
2003-05-07 15:38   ` Jeff Garzik
2003-05-07 15:24 ` Randy.Dunlap
2003-05-07 17:14   ` Russell King
2003-05-07 22:04     ` Andrew Morton
2003-05-07 22:28       ` Dave Hansen
2003-05-08 12:05         ` David S. Miller
2003-05-08 14:55           ` Alan Cox
2003-05-08 14:54             ` David S. Miller
2003-05-08 16:24               ` Arnaldo Carvalho de Melo
2003-05-08 16:26               ` Jeff Garzik
2003-05-08 16:30                 ` Randy.Dunlap
2003-05-11 18:41                   ` Jeff Garzik
2003-05-08 17:56               ` Kai Germaschewski
2003-05-08 17:36           ` Linus Torvalds
2003-05-09  6:51           ` Richard Henderson

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=3EBACF9D.5070501@inet.com \
    --to=eli.carter@inet.com \
    --cc=jgarzik@pobox.com \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=rmk@arm.linux.org.uk \
    /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