From: Padraig@Linux.ie
To: jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: ok, which wise guy did this?
Date: Wed, 22 Jan 2003 12:15:50 +0000 [thread overview]
Message-ID: <3E2E8B76.5000805@Linux.ie> (raw)
In-Reply-To: <20030122064047.D41405@shell.cyberus.ca>
jamal wrote:
> I just booted my spanking new P4 HT PC last night using 2.5.58
> and to my dissapointment the enumeration of the ethx devices is
> reversed. I have 5 ethernet ports on this; eth0-4 on 2.4.x are now listed
> as eth4-0. This is rude.
If you depend on the order then you must explicitly name the devices
like you want. I've done something like this in the past.
ip link set dev eth0 name interface-1
ip link set dev eth1 name interface-2
I guess you could use a temp name and keep the eth[0-4]
naming if you prefer.
Pádraig.
next prev parent reply other threads:[~2003-01-22 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 11:47 ok, which wise guy did this? jamal
2003-01-22 12:15 ` Padraig [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-22 16:19 Larry Sendlosky
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=3E2E8B76.5000805@Linux.ie \
--to=padraig@linux.ie \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).