From: Dave Jones <davej@redhat.com>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first
Date: Fri, 8 Sep 2006 11:56:39 -0400 [thread overview]
Message-ID: <20060908155639.GJ28592@redhat.com> (raw)
In-Reply-To: <20060908031422.GA4549@lists.us.dell.com>
On Thu, Sep 07, 2006 at 10:14:22PM -0500, Matt Domsch wrote:
> Problem:
> New Dell PowerEdge servers have 2 embedded ethernet ports, which are
> labeled NIC1 and NIC2 on the chassis, in the BIOS setup screens, and
> in the printed documentation. Assuming no other add-in ethernet ports
> in the system, Linux 2.4 kernels name these eth0 and eth1
> respectively. Many people have come to expect this naming. Linux 2.6
> kernels name these eth1 and eth0 respectively (backwards from
> expectations). I also have reports that various Sun and HP servers
> have similar behavior.
This came up years back when 2.6 was something new, and the answer
then was 'bind the interface to the MAC address'.
Whilst your patch will fix the case that's currently broken (2.4->2.6),
doesn't it offer equal possibility to break existing setups when people move
from <=2.6.18 -> 2.6.19 ?
Dave
next prev parent reply other threads:[~2006-09-08 15:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 3:14 [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first Matt Domsch
2006-09-08 15:56 ` Dave Jones [this message]
2006-09-08 16:18 ` Matt Domsch
2006-09-08 16:55 ` Arjan van de Ven
2006-09-11 19:36 ` Bill Davidsen
2006-09-12 3:08 ` Matt Domsch
2006-09-12 21:06 ` Bill Davidsen
2006-09-08 16:45 ` Greg KH
2006-09-08 18:20 ` Andrew Morton
2006-09-08 18:52 ` Matt Domsch
2006-09-08 18:59 ` Alexey Dobriyan
2006-09-09 9:05 ` Jeff Garzik
2006-09-09 12:11 ` Pavel Machek
2006-09-10 11:26 ` Stefan Richter
2006-09-10 13:02 ` Greg KH
2006-09-15 3:53 ` Dan Carpenter
2006-09-15 13:02 ` Matt Domsch
2006-09-16 2:39 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2006-09-08 3:18 Matt Domsch
2006-09-08 19:34 Matt Domsch
2006-09-09 14:37 Ragnar Kjørstad
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=20060908155639.GJ28592@redhat.com \
--to=davej@redhat.com \
--cc=Matt_Domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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.