Openmoko Bug #2056: /etc/resolv.conf is empty on first boot

Openmoko Public Trac bugs at
Mon Oct 6 16:30:49 CEST 2008

#2056: /etc/resolv.conf is empty on first boot
    Reporter:  rwhitby  |        Owner:  julian_chu
        Type:  defect   |       Status:  new       
    Priority:  normal   |    Milestone:            
   Component:  Distro   |      Version:            
    Severity:  normal   |   Resolution:            
    Keywords:           |    Blockedby:            
Reproducible:  always   |     Blocking:            
Changes (by zecke):

  * owner:  raster => julian_chu
  * component:  Network Manager => Distro


 The other side of the story is
 this]. usb0 adds a default route and when you add a DNS entry to any kind
 of name resolving will take a while until it times out. This was a big hit
 for assassin as it added a huge (several seconds) delay to have a opkg
 update fail. My assumption was as nameserver is wrong most
 of the time anyway and added complication (koen did a similar fix in OE)
 and that with wlan one would have dhcp most of the time anyway.

 Any ideas how to make both sides happy? Have a default DNS server but
 still fail fast in case usb0 is not routed to the world?

Ticket URL: <> <>
openmoko trac

More information about the buglog mailing list