[systemd-devel] Network Interface Names: solution for a desktop OS

[Xen]

Reindl Harald schreef op 15-04-16 17:55:
> 
> 
> Am 15.04.2016 um 17:48 schrieb Xen:
>> Reindl Harald schreef op 13-04-16 10:24:
>>> 4xHDD raid-10, hardware from 2011
>>> Startup finished in 660ms (kernel) + 5.380s (initrd) + 12.769s
>>> (userspace) = 18.810s
>>>
>>> os on sd-card
>>> Startup finished in 375ms (kernel) + 4.306s (initrd) + 8.323s
>>> (userspace) = 13.005s
>>>
>>> so 3 seconds is unacceptable and the idea ist a joke in general because
>>> you wait for something possibly happen while you don't know how long you
>>> have to wait and jsut hope for luck - that's not a good design and won't
>>> bew accepted anywhere
>>
>> You are the only one taking 3 seconds seriously as something to hang
>> onto just so you can say that I am full of shit
> 
> it don't matter *how long* you wait for something you don't know if it
> ever appears and how long it take to appear - period

That's why you *don't* and you just proceed with it in line with the
current booting of the system, you just postpone the renaming to a later
stage where you rename all in one go, instead of each time a device is
discovered.

The thing I talked about was not any form of "sleep".

Even Greg thought it was not completely out of the ordinary.

If you can produce for me systems that see networking devices added
after they have already been tried to "up" - meaning the software
configuration (firewall, routing) is being started on non-existing
devices, fine. Produce that list.

Show me those systems where not all devices are present at network up time.