From: Dale Amon <amon@vnl.com>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Dale Amon <amon@vnl.com>, linux-kernel@vger.kernel.org
Subject: Re: A return to PCI ordering problems...
Date: Tue, 20 Nov 2001 21:20:55 +0000 [thread overview]
Message-ID: <20011120212055.A22590@vnl.com> (raw)
In-Reply-To: <20011120190316.H19738@vnl.com> <Pine.LNX.3.95.1011120144925.14138A-100000@chaos.analogic.com>
In-Reply-To: <Pine.LNX.3.95.1011120144925.14138A-100000@chaos.analogic.com>
On Tue, Nov 20, 2001 at 03:03:23PM -0500, Richard B. Johnson wrote:
> FYI, if you care about the name of your ethernet device, your
> configuration is probably broken. The IEEE station address can
> be used to identify a device and it's accessible from `ifconfig`
> without setting any network parameters. So, given this, you
> can set any number of boards found, to anything you need to
> configure, including complicated servers and routers, with a
> simple shell-script.
I presume IEEE station address == MAC...
I haven't really much choice. I can't use modules for
security reasons; I have to assign the motherboard MAC
to eth0 because a commercial package we are installing
licenses on the MAC address of eth0.
Ifconfig cannot, to my knowledge, swap the identify of
eth0 and eth1. However I the iproute2 calls, if they are
available, might do the trick. I will have to see.
The only thing I really have control over is the kernel
itself, not the dist even.
Has the pci=reverse option been removed? That might
have done the trick.
Also, I don't really see anything inherently wrong with
being able to force some of these things at the boot
command line.
--
------------------------------------------------------
Nuke bin Laden: Dale Amon, CEO/MD
improve the global Islandone Society
gene pool. www.islandone.org
------------------------------------------------------
next prev parent reply other threads:[~2001-11-20 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 19:03 A return to PCI ordering problems Dale Amon
2001-11-20 20:03 ` Richard B. Johnson
2001-11-20 19:51 ` Tim Hockin
2001-11-20 20:13 ` Faux Pas III
2001-11-20 21:20 ` Dale Amon [this message]
2001-11-20 21:58 ` Andreas Dilger
2001-11-20 21:49 ` David Woodhouse
2001-11-20 22:02 ` Dale Amon
2001-11-20 22:04 ` Richard B. Johnson
2001-11-20 21:27 ` David Woodhouse
2001-11-20 21:47 ` Dale Amon
2001-11-21 9:27 ` Helge Hafting
2001-11-21 12:52 ` Christer Weinigel
2001-11-21 8:57 ` James A Sutherland
2001-11-21 9:20 ` Alan Cox
2001-11-21 11:29 ` Henning P. Schmiedehausen
2001-11-21 11:53 ` Christoph Hellwig
2001-11-21 12:10 ` Henning P. Schmiedehausen
2001-11-21 13:51 ` James A Sutherland
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=20011120212055.A22590@vnl.com \
--to=amon@vnl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.