Openmoko Bug #2056: /etc/resolv.conf is empty on first boot
Openmoko Public Trac
bugs at docs.openmoko.org
Mon Oct 6 12:29:17 CEST 2008
#2056: /etc/resolv.conf is empty on first boot
-----------------------------+----------------------------------------------
Reporter: rwhitby | Owner: raster
Type: defect | Status: new
Priority: normal | Milestone:
Component: Network Manager | Version:
Severity: normal | Keywords:
Blockedby: | Reproducible: always
Blocking: |
-----------------------------+----------------------------------------------
Scenario:
Flash a new ASU or FSO distribution, and connect to it via USB networking
(since it's a GTA01, so there is no wireless, and GPRS and Bluetooth don't
connect to anything out of the box).
Type "opkg update". If /etc/resolv.conf had sensible contents it would
work. However, /etc/resolv.conf is empty, so it doesn't.
This has been mentioned countless times on many OM mailing lists, but it
seems that no-one has ever officially reported it as a bug.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2056>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list