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]

Date:	Tue, 4 Sep 2007 22:50:43 +0200
From:	"Kay Sievers" <kay.sievers@...y.org>
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 9/4/07, davide rossetti <davide.rossetti@...il.com> wrote:
> 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
>
> it is a Fedora Core 6, fully updated (kernel-2.6.22.2-42.fc6
> udev-095-17.fc6.x86_64)

I don't think any of the mentioned tools is to blame. Please use the
distro's bugtracker.

Thanks,
Kay
-
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/