Re: Unconditional 30s boot delay.

Ian FREISLICH пишет:
> Ian FREISLICH wrote:
>> Which is fine and well if routing runs *after* the DHCP request,
>> but it doesn't it runs before devd is started so the default route
>> from DHCP is never acquired and we wait... for 30s....
>>
>> And this needs an "echo" after the "done" so that the next script's
>> output lands up at the start of the next line.
> 
> Forgot to add this console log in support:
> 
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
>         inet 127.0.0.1 netmask 0xff000000 
> vr0: link state changed to UP
> vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=2808<VLAN_MTU,WOL_UCAST,WOL_MAGIC>
>         ether 00:40:63:f4:22:7e
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
> Additional routing options: IP gateway=YES.
> Waiting 30s for an interface to come up: .............................Starting d
> evd.
> hw.acpi.cpu.cx_lowest: C1 -> C1
> DHCPREQUEST on vr0 to 255.255.255.255 port 67
> DHCPACK from 10.0.0.1
> bound to 10.0.0.223 -- renewal in 216000 seconds.
> Firewall rules loaded.
I write about this problem week ago, but - I today sourse contain this bug.
My desktop cannot get IP when boot, and I manually run dhclient after 
boot...