Suggestion: default /etc/resolv.conf
Carsten Haitzler (The Rasterman)
raster at openmoko.org
Thu Jul 24 17:35:25 CEST 2008
On Thu, 24 Jul 2008 17:06:33 +0200 "arne anka" <openmoko at ginguppin.de> babbled:
> > Stuff like dhclient/udhcpcd and/or NetworkManager manages the
> > resolv.conf for you. AFIAK the problem is that the current firmwares do
> > not properly support this via GUI.
> what he's talking about is, probably, that most people try the first steps
> by _usb_ connection!
> and usually (even if you run a dhcp server on your computer) usb
> networking is no scenario for dynamic address allocation.
> thus, new users see themselves rather fast confronted with the need to
> edit the resolv.conf thru an ssh connection with vi -- because desktops
> ususally do not do name resolution but rely on a router or so.
> therefore the current default 192.168.0.200 is not much help either.
> insofar it's probably a better idea to put some open dn servers into the
> default resolv.conf -- it gets overwritten by networkmanager/whatever soon
if they have to ssh in and edit resolv.conf - i see it as no big addition to
having to issue iptables, ifconfig etc. commands to enable your host desktop to
route packets for your freerunner anyway - so one way or another you'd
fiddling with scripts and command-line goop. the same script to set up
ifconfig/iptables could ALSO scp a resolv.conf over that works (eg a copy of
your host system's resolv.conf). :)
Carsten Haitzler (The Rasterman) <raster at openmoko.org>
More information about the community