From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530
Date: Mon, 14 Jul 2008 18:30:57 +0200 [thread overview]
Message-ID: <200807141830.57335.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20080714112554.793bd9cf@zaphod.digimed.co.uk>
On Monday 14 July 2008, Neil Bothwick wrote:
> On Mon, 14 Jul 2008 09:43:21 +0300, Daniel Iliev wrote:
> > > It's hardly new, it's been around for some years. It is helpful
> > > if you have two NICs because it means they are named
> > > consistently, which is better than having your private network
> > > connected to the Internet because the kernel decided to load the
> > > modules in a different order.
> >
> > 1) You can explicitly tell the kernel the order in which load the
> > modules
>
> And if the module for eth0 fails to load, the other card becomes eth0
> instead of eth1. Using udev rules, the second card is always eth1,
> whatever happens elsewhere in the system.
Consider this: if we could have assigned arbitrary names to interfaces
since day one, we would have the exact same behaviour udev gives,
everyone would agree this is a truly excellent thing and this thread
would not exist.
The single minor difference is that you can't call the interface
whatever you want directly, it just gets named the equally arbitrary
name of "eth1"
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-07-14 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 3:21 [gentoo-user] Network chip always comes up eth1 on 1-year-old Dell Inspiron 530 waltdnes
2008-07-09 7:44 ` Neil Bothwick
2008-07-12 23:55 ` Walter Dnes
2008-07-13 8:37 ` Alan McKinnon
2008-07-13 10:30 ` Neil Bothwick
2008-07-14 6:43 ` [gentoo-user] [OT] " Daniel Iliev
2008-07-14 10:25 ` Neil Bothwick
2008-07-14 16:30 ` Alan McKinnon [this message]
2008-07-14 22:17 ` Neil Bothwick
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=200807141830.57335.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.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