As far as I know .. it's useless because every time you get a DHCP
lease from a different server, it overrides your resolv.conf with it's
own favourite DNS servers.
On Thu, Jul 24, 2008 at 5:15 PM, Brian C [EMAIL PROTECTED] wrote:
Suggestion:
The rootfs should contain a resolv.conf that lists
Hi,
I am not sure that this is a good suggestion.
Brian C schrieb:
Suggestion:
The rootfs should contain a resolv.conf that lists some
publicly-available dns servers so that people with new FreeRunners would
have a chance of getting net access without editing that file first.
Stuff like
Suggestion:
The rootfs should contain a resolv.conf that lists some
publicly-available dns servers so that people with new FreeRunners would
have a chance of getting net access without editing that file first.
Despite clear instructions on the wiki, this issue continues to cause
people problems
On Thu, Jul 24, 2008 at 9:15 AM, Brian C [EMAIL PROTECTED] wrote:
Suggestion:
The rootfs should contain a resolv.conf that lists some
publicly-available dns servers so that people with new FreeRunners would
have a chance of getting net access without editing that file first.
Hi Brian.
On Thu, 24 Jul 2008 17:06:33 +0200 arne anka [EMAIL PROTECTED] 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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| There's the DHCP issue that other emails talk about. Another problem
| is that you have to trust your DNSs and somehow it would mean that
| OpenMoko trusts (blindly) a few DNS servers. I feel that trusting
On Thu, Jul 24, 2008 at 10:52 AM, Andy Green [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| There's the DHCP issue that other emails talk about. Another problem
| is that you have to trust your DNSs and somehow it would
Joe Pfeiffer wrote:
Much better to get resolv.conf, along with IP address, from DHCP.
Typically, I'd agree -- except the Freerunner doesn't get its IP from
DHCP for the USB port, which is where pretty much all of the DNS
questions come from to the list (until GRPS starts working reliably...)
ian douglas writes:
Joe Pfeiffer wrote:
Much better to get resolv.conf, along with IP address, from DHCP.
Typically, I'd agree -- except the Freerunner doesn't get its IP from
DHCP for the USB port, which is where pretty much all of the DNS
questions come from to the list (until GRPS starts
Yes, but I'd like it to use DHCP for its usb IP address, as well.
what stops you? the dhcp client will overwrite resolv.conf, then.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
arne anka writes:
Yes, but I'd like it to use DHCP for its usb IP address, as well.
what stops you? the dhcp client will overwrite resolv.conf, then.
This is actually a reprise of a discussion a week or so ago -- as a
matter of fact, that is what I do. But, since it's not set up that way
in
12 matches
Mail list logo
