'Twas brillig, and Lennart Poettering at 01/10/13 01:41 did gyre and gimble:
> On Mon, 30.09.13 17:42, Thomas Bächler (tho...@archlinux.org) wrote:
>
>> Any application that listens on netlink for new network interfaces may
>> start using the interface before udev has finished processing the ueven
On Mon, 30.09.13 17:42, Thomas Bächler (tho...@archlinux.org) wrote:
> Any application that listens on netlink for new network interfaces may
> start using the interface before udev has finished processing the uevent.
>
> IMO, this needs to be fixed in the kernel and udev, so that udev can
> have
On Mon, 30.09.13 16:14, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> Hi,
>
> Just trying to debug the problem mentioned in the subject. I'm wanting
> to use the new device names in stage 2 of our installer (some closing
> config routines write the interface name into some conf files etc), but
>
'Twas brillig, and Thomas Bächler at 30/09/13 16:42 did gyre and gimble:
> Am 30.09.2013 17:14, schrieb Colin Guthrie:
>> Hi,
>>
>> Just trying to debug the problem mentioned in the subject. I'm wanting
>> to use the new device names in stage 2 of our installer (some closing
>> config routines writ
Am 30.09.2013 17:14, schrieb Colin Guthrie:
> Hi,
>
> Just trying to debug the problem mentioned in the subject. I'm wanting
> to use the new device names in stage 2 of our installer (some closing
> config routines write the interface name into some conf files etc), but
> when udev rules kick in,
Hi,
Just trying to debug the problem mentioned in the subject. I'm wanting
to use the new device names in stage 2 of our installer (some closing
config routines write the interface name into some conf files etc), but
when udev rules kick in, the device is already up and in use... is there
any way
