public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Iliev <daniel.iliev@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 09:43:21 +0300	[thread overview]
Message-ID: <20080714094321.7c92ee0b@ilievnet.com> (raw)
In-Reply-To: <20080713113056.2ffce7f0@zaphod.digimed.co.uk>

On Sun, 13 Jul 2008 11:30:56 +0100
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Sat, 12 Jul 2008 19:55:56 -0400, Walter Dnes wrote:
> 
> > > Udev is doing this. If you have removed the second card,
> > > delete /etc/udev/rules.d/70-persistent-net.rules, otherwise edit
> > > the file to switch the assignments for the two NICs.  
> > 
> >   Thanks.  A "new and improved helpfull feature" that could've done
> > without.
> 
> 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.
> 
> 


IIRC:

1) You can explicitly tell the kernel the order in which load the
modules
2) If you build the the drivers in-kernel the the order is determined
by the PCI slot numbers



-- 
Best regards,
Daniel
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-07-14 10:19 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       ` Daniel Iliev [this message]
2008-07-14 10:25         ` [gentoo-user] [OT] " Neil Bothwick
2008-07-14 16:30           ` Alan McKinnon
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=20080714094321.7c92ee0b@ilievnet.com \
    --to=daniel.iliev@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