public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Clark <jclark@metricsystems.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Strange ethN numbering problem.
Date: Tue, 09 Jan 2007 10:22:08 -0800	[thread overview]
Message-ID: <45A3DD50.7040302@metricsystems.com> (raw)
In-Reply-To: <20070109040616.ED8C460BE75@tzec.mtu.ru>

Andrey Borzenkov schrieb:
> John Clark wrote:
>
>   
>
> Then quite likely it remembered lower numbers for "old" interfaces and
> starts renaming with next available.
>
>   
>> The kernel is 2.6.19.1 the at-that-moment current linux kernel.
>>
>> What should I look for in terms of interface renaming.
>>     
>
> I guess in udev rules; look also if you have /etc/iftab. The best you can do
> is asking in lists/groups dedicated to your distribution.
>
> -andrey

Thanks.

It was 'udev rules' that were messing things up, left over from using 
the disk on a different
piece of hardware. To date I've been making only 'embedded'  systems 
using busybox, and other
similarly limited root environments and never really dealt with a  
pretty much full up distribution
outside of my host development systems. Hence, never really had gotten 
in to 'udev'. I've been
using devfs mostly till recently... However, in anticipation of large 
capacity flash systems, I've moved
to making my embedded systems almost as full up as most host systems.

Is there some startup command line option for the linux kernel to force 
the 'udev' management
program to basically 'ignore and refresh' device names?


John Clark.



      reply	other threads:[~2007-01-09 18:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  0:28 Strange ethN numbering problem John Clark
2007-01-09  1:15 ` Bernd Eckenfels
2007-01-09  1:38   ` John Clark
2007-01-09  4:06     ` Andrey Borzenkov
2007-01-09 18:22       ` John Clark [this message]

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=45A3DD50.7040302@metricsystems.com \
    --to=jclark@metricsystems.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-kernel@vger.kernel.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