From: Andi Kleen <ak@suse.de>
To: bert hubert <ahu@ds9a.nl>
Cc: netdev@oss.sgi.com, Dave Jones <davej@codemonkey.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: NIC renaming does not rename /proc/sys/net/ipv4 Was: Re: NICs trading places ?
Date: 29 Mar 2003 13:29:19 +0100 [thread overview]
Message-ID: <1048940960.2176.86.camel@averell> (raw)
In-Reply-To: <20030329121755.GA17169@outpost.ds9a.nl>
On Sat, 2003-03-29 at 13:17, bert hubert wrote:
> On Sat, Mar 29, 2003 at 05:47:17AM +0100, Andi Kleen wrote:
> > Dave Jones <davej@codemonkey.org.uk> writes:
> >
> > > I just upgraded a box with 2 NICs in it to 2.5.66, and found
> > > that what was eth0 in 2.4 is now eth1, and vice versa.
> > > Is this phenomenon intentional ? documented ?
> >
> > Just assign mac addresses to names and run nameif early in boot.
>
> A slight problem with that is that not all parts of /proc/sys get renamed
> this way:
Just rename at early boot before IP is set up. That is what i usually
do - set up /etc/mactab and run it very early at boot.
Running it later is usually flakey. e.g. it can also give confusing
effects with old style named ip aliases.
-Andi
next prev parent reply other threads:[~2003-03-29 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29 4:47 ` NICs trading places ? Andi Kleen
2003-03-29 12:17 ` NIC renaming does not rename /proc/sys/net/ipv4 Was: " bert hubert
2003-03-29 12:29 ` Andi Kleen [this message]
2003-03-29 14:25 ` Wichert Akkerman
[not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel.suse.lists.linux.kernel>
[not found] ` <p73isu2zsmi.fsf@oldwotan.suse.de.suse.lists.linux.kernel>
[not found] ` <20030329121755.GA17169@outpost.ds9a.nl.suse.lists.linux.kernel>
[not found] ` <1048940960.2176.86.camel@averell.suse.lists.linux.kernel>
[not found] ` <20030329142519.GG2078@wiggy.net.suse.lists.linux.kernel>
2003-03-29 17:50 ` Andi Kleen
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=1048940960.2176.86.camel@averell \
--to=ak@suse.de \
--cc=ahu@ds9a.nl \
--cc=davej@codemonkey.org.uk \
--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 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.