On 22 Jan 2006, at 16:10, D. Hugh Redelmeier wrote: > | From: John Jordan <[EMAIL PROTECTED]> > > I'm going to assume that your problem is DNS-related. > Your DHCP client most likely rewrites /etc/resolv.conf to reflect what > the DHCP server told it were the DNS servers. The resolv.conf you > quote reflects what Comcast's DHCP server would have told your client.
Thanks for your observations and suggestions. You were more or less right. I also posted the same problem to an e-list of a local Linux user group, and someoe responded with more or less the same thing. Today I was at the university. I logged in first with 64-bit Firefox. Then I checked /etc/resolv.conf and the contents were different, listing the university and its DNS servers. I copied the three lines to /chroot/breezy/32bits/etc/resolv.conf and saved the file. Then I opend 32-bit Firefox running in chroot. When I tried to go somewhere on the net, bingo! Worked perfectly! Right now I am workingn on creating a hard link between /etc/resolv.conf and the one in chroot. Someone told me to create a hard link by doing this, but the syntax doesn't quite work: ln /etc/resolv.conf /chroot/breezy/32bits/etc/resolv.conf It says the file already exists. I read the man page on ln and it gave a lot of information about options, but nowhere did it say exactly what ln DOES. But don't get me started on Linux documentation. :( Anyway, I'm [MaxwellSmartvoice:ON] *that* close [MaxwellSmartvoice:Off]. _______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
