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] [day] [month] [year] [list]

Date:	Sat, 8 Sep 2007 09:21:35 +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 7 2007 18:44, davide rossetti wrote:
>
>> > 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.
>>
>> yes, it's FC6.
>>
>> > 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.
>>
>> seems like HWADDR is incompatible with bonding.... there is some
>> message using HWADDR as well as MASTER=bond0 and SLAVE=yes.
>
>for the records I worked-around it:
>- problem seems to be the interface 'bond0', which is started first,
>stops the ability to create another device named 'eth0' (WHY?)
>- so I shifted all of the interface names: 0->1, 1->2,...
>now it is ok. still I do not understand why bond0 seems to interfere
>with eth0...

Fedora says it all.
-
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/