mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bill Nottingham <notting@redhat.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: davide rossetti <davide.rossetti@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: origin of __tmp1930643048 network device name: kernel-space or user-space
Date: Thu, 6 Sep 2007 09:35:51 -0400	[thread overview]
Message-ID: <20070906133551.GA25155@nostromo.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709061448390.25942@fbirervta.pbzchgretzou.qr>

Jan Engelhardt (jengelh@computergmbh.de) said: 
> >dear all,
> >I'm trying to track down a problem on a Sun V40Z server with 4 network
> >devices grabbing random ethX device names. now, trying to force the
> >device names to what I want, I got a __tmpXXXXX form of device name,
> >which I think is a half-configured device... but which piece of
> >software is to blame ??? kernel, udev, hotplug
> 
> Look into dmesg. If the device was once known as ethX or similar,
> then it is userspace to blame.

It's userspace.

<off-topic for l-k, but while I'm here...>

I'm assuming you're running some sort of Fedora/RHEL/
derivative; this is what you get when you have a device that starts
out named ethX, but which needed to be renamed so that an already
configured ethX could be changed to that name.

For the new device, either add a HWADDR in a ifcfg-ethX file for
that interface, add something to /etc/mactab, or add a udev rule.

Bill

  reply	other threads:[~2007-09-06 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 17:14 davide rossetti
2007-09-04 20:50 ` Kay Sievers
2007-09-06 12:49 ` Jan Engelhardt
2007-09-06 13:35   ` Bill Nottingham [this message]
2007-09-06 15:02     ` davide rossetti
2007-09-07 16:44       ` davide rossetti
2007-09-08  7:21         ` Jan Engelhardt

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=20070906133551.GA25155@nostromo.devel.redhat.com \
    --to=notting@redhat.com \
    --cc=davide.rossetti@gmail.com \
    --cc=jengelh@computergmbh.de \
    --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

all inboxes | Powered by JetHome®