This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 2009-09-25, Jonathan Larmour <jifl@jifvik.org> wrote:But yes that does confirm that an unplugged cable at startup means no IP address unless the user calls init_all_network_interfaces again.
In this respect, the DHCP code wants improvement.
I can't think of any use-cases for our products where the DHCP client should ever give up. Telling customers they have to guarantee the power-up sequence of various portions of their plant to make our DHCP client happy isn't really an option. ;)
Am I missing something? Are there situations where giving up on acquiring an address is the right thing to do?
Jifl -- --["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
-- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |