From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] which NIC is which
Date: Wed, 10 Jul 2002 06:37:39 +0000 [thread overview]
Message-ID: <marc-lartc-102628310710032@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102624934518788@msgid-missing>
On Tue, 9 Jul 2002, Michael T. Babcock wrote:
> Arthur van Leeuwen wrote:
>
> >Unfortunately, in systems with identical cards that are configured using
> >plug-and-play methods such as those used by PCI random is the best shot you
> >have...
> >
> >
> 'Deterministic' is more accurate. It seems to be random, on first boot.
> But it will almost never change after that unless you make hardware
> changes, in my experience.
Not in mine. Every time the PCI bus settings (can't recall the name right
now, have been playing with a fixed hardware platform for quite a while)
get reset there will probably be a different assignation. Yeah, it'll
probably be deterministic *somehow*, but you'll be hard pressed to come up
with any rules.
Doei, Arthur.
--
/\ / | arthurvl@sci.kun.nl | Work like you don't need the money
/__\ / | A friend is someone with whom | Love like you have never been hurt
/ \/__ | you can dare to be yourself | Dance like there's nobody watching
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-07-10 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 21:14 [LARTC] which NIC is which John Telford
2002-07-09 21:56 ` Arthur van Leeuwen
2002-07-09 22:06 ` Michael T. Babcock
2002-07-10 6:37 ` Arthur van Leeuwen [this message]
2002-07-10 8:34 ` bert hubert
2002-07-10 12:38 ` Vladimir B. Savkin
2002-07-10 12:42 ` bert hubert
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=marc-lartc-102628310710032@msgid-missing \
--to=arthurvl@sci.kun.nl \
--cc=lartc@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 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.