Well, I'm back from my escapades fighting robots in California. A sincere
appology goes out for missing the LEAF meeting in San Francisco Wedensday
night. As Mike reported, I didn't get in until really early Thursday
morning.
Currently, it looks like the highest priority is verifying Ewald's
Charles Steinkuehler wrote:
Well, I'm back from my escapades fighting robots in California. A sincere
appology goes out for missing the LEAF meeting in San Francisco Wedensday
night. As Mike reported, I didn't get in until really early Thursday
morning.
Currently, it looks like the highest
Welcome back! I hope you will find some time to give us a report of how
your bot did and anything else noteworthy about the trip
Paonia
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Well, I'm back from my escapades fighting robots in California. A sincere
appology goes out for
Symptom:
When I boot the new package I get after:
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
receive_packet failed on eth0: Network is down
Then if I issue after login in
/etc/init.d/dhclient restart
it works ok
I replaced the dhclient package with the one on Charle's
Charles:
Heya, welcome back. :)
IMO, since this ES3 release will be a whole-floppy release,
it makes sense to me to release it with dhclient and dnscache
pre-setup to groove together nicely. Just my two coppers.
-Scott
On Thu, 31 May 2001, Charles Steinkuehler wrote:
2) Add a prepend statement to dhclient.conf:
prepend domain-name-servers 127.0.0.1;
This *should* use the local dnscache to resolve names, falling back to
the
DNS server(s) provided by the ISP if local resolution fails, and keeps
everything standard but the dhclient configuration file,
