As default network configuration, we've reasonally chosen a dhcp configuration, which is great on a dhcp network, but ugly when it has to wait for timeout.
We could modify rc.network by adding a & to the dhclient row ...
Simply running dhclient in the background is probably not a great idea, since that will allow the boot to continue and any network programs/daemons will try to start before the network gets initialized. (Even if your FreesBIE distro isn't running any network daemons, someone else will start from your work and try to add them... ) If you're not using rcNG (sounds like you're not), then a better approach may be to run your rc.network script in the background. It can then run dhclient and then run any other network daemons only after that definitively succeeds or fails. Meanwhile, the rest of the boot can proceed normally.
Can an optional flag be added (configurable in rc.conf)?
Not to CURRENT, no. CURRENT has adopted rcNG, for which no such easy workaround is possible. (Short of putting all the network startup back into a single script file.... ;-( Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
