linux-kernel - Re: origin of __tmp1930643048 network device name: kernel-space or user-space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0709061448390.25942@fbirervta.pbzchgretzou.qr>
Date:	Thu, 6 Sep 2007 14:49:17 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	davide rossetti <davide.rossetti@...il.com>
cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: origin of __tmp1930643048 network device name: kernel-space or
 user-space


On Sep 4 2007 19:14, davide rossetti wrote:
>
>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.



	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/