Removing -n option from udhcpc

[Daykin, Evan]

>Please be more specific. They exited how? what are the messages from them?
Sending discover...
Sending discover...
Sending discover...
No lease obtained, forking to background. (ps shows nothing, it is dead)

> Of course. If you gave -n to udhcpc, it will exit if lease is not obtained.
>If you don't want this, don't give it the -n option.

Understood, but in this case rebuilding and updating Busybox is a non-trivial matter. We are wondering what the rationale is for this being baked-in, default behavior (networking/Config.src:55) instead of being specified in the interfaces file.