From: Andi Kleen <ak@suse.de>
To: Wichert Akkerman <wichert@wiggy.net>
Cc: 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 18:50:41 +0100 [thread overview]
Message-ID: <p73adfeyscu.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20030329142519.GG2078@wiggy.net.suse.lists.linux.kernel>
Wichert Akkerman <wichert@wiggy.net> writes:
> > 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.
>
> How does that solve the problem of /proc/sys/net/*/conf/* not being
> renamed?
They are only set up when the inet device structure is created.
That happens at the first ifconfig/ip, not on driver init.
As for non ethernet devices - if you find a reliably way to identify/number
them then the same principle can be used for them too.
-Andi
next parent reply other threads:[~2003-03-29 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[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
2003-03-29 14:25 ` Wichert Akkerman
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=p73adfeyscu.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wichert@wiggy.net \
/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.