© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
> However, Focal (which uses klibc 2.0.7) uses dhclient for networking initialization instead of ipconfig...
If no users in Focal could be affected by the bug then I'm fine with accepting the fix to Bionic only. But could you please expand on the above statement? Under what conditions does Focal use dhclient instead of ipconfig? Presumably through initramfs-tools and ip=/ip6=? Are there any other situations where users could reasonably be using klibc/ipconfig on Focal? Is it possible for them to be doing this but not using initramfs-tools?
It would help me understand if you could present a complete user story to explain the user impact. Right now the bug description doesn't explain the full scenario under which they would be impacted by this bug.
> [Where problems could occur]
I don't think you've really answered this question. What different scenarios, from a user perspective (ie. user stories), can reasonably be predicted that will hit this ipconfig DHCP-related timeout case?