mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Andrew Morton <akpm@digeo.com>
Cc: davej@codemonkey.org.uk, linux-kernel@vger.kernel.org,
	jgarzik@pobox.com, aeb@cwi.nl
Subject: Re: NICs trading places ?
Date: Sat, 29 Mar 2003 00:20:22 +0100	[thread overview]
Message-ID: <20030328232022.GA12005@win.tue.nl> (raw)
In-Reply-To: <20030328150234.7f73d916.akpm@digeo.com>

On Fri, Mar 28, 2003 at 03:02:34PM -0800, Andrew Morton wrote:
> Andries Brouwer <aebr@win.tue.nl> wrote:
>
> > +	if (retval == 0) {
> > +		int i;
> > +		printk("%s: 3c59x, address", dev->name);
> > +		for (i = 0; i < 6; i++)
> > +			printk("%c%2.2x", i ? ':' : ' ', dev->dev_addr[i]);
> > +		printk("\n");
> >  		return 0;
> > +	}
> 
> hm.  typing `ifconfig' shows this information.

I like uniformity.
Either all eth cards should have their address in dmesg, or none.
Almost all do.

And: ifconfig does not give the card types.
So presently one needs both boot messages and ifconfig.

And: in some situations the system does not boot because of
eth numbering mixup, and one never gets the opportunity to
ask ifconfig.

Andries


  reply	other threads:[~2003-03-28 23:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 22:10 Dave Jones
2003-03-28 22:14 ` Jeff Garzik
2003-03-28 22:15 ` jjs
2003-03-28 22:25 ` Joel Becker
2003-03-28 22:27   ` Randy.Dunlap
2003-03-28 22:34   ` Dave Jones
2003-03-28 22:48 ` Andries Brouwer
2003-03-28 23:02   ` Andrew Morton
2003-03-28 23:20     ` Andries Brouwer [this message]
2003-03-28 23:41       ` Greg KH
2003-03-28 23:56         ` Jeff Garzik
2003-03-29  0:03           ` Greg KH
2003-03-29  9:20   ` Marc Zyngier
2003-03-28 23:30 ` Dax Kelson
2003-03-28 23:42   ` Sean Neakums
     [not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29  4:47 ` Andi Kleen

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=20030328232022.GA12005@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=aeb@cwi.nl \
    --cc=akpm@digeo.com \
    --cc=davej@codemonkey.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®