My Slack resolv.conf never gets overwritten. 1. It be a static IP and my particular SOHO DSL gateway/firewall/router (it's a 2wire 1701HG) may also have to do with this.
Slack 11 Rocks! I just discovered some more on my particular Slack http www browsing slow issue. So, next, just sharing of what's happened so far.
P.S. my outdated Slack current 2.6 www browser is intermittently (albeit too often) way too slow.
it's a Slack current that was current until near 7, 8 weeks prior to release of Slack 11 and then I lacked the time to update those the copius changes of those mentioned 8 weeks.
That box is a static 192.168.1.xx IP. I had *manually* added the IP and info of that box to my SOHO dsl modem/firewall/router (a 2wire 1701HG) (AT&T Yahoo DSL).
More info on that box: 220.127.116.11 kernel I had compiled using/adding/changing a base config of one of the official Slack extra or testing kernels.
Its resolv.conf always stays the same, never overwritten it points directly to the 2wire (internet gateway).
My point here is that I just installed Slack 11 on a different box that had not ever been on the 2wire internet gateway; and with this new box's (a static IP box) resolv.conf pointing directly to the 2wire, web browsing with Firefox is blazingly fast nearly all of the time!
I let the 2wire automatically discover this new box. (the 2wire likes to use its arp) (I don't like 2wire using arp but that's another story.)
The differences between these 2 boxes: different 2.6 kernel versions, new box uses Slack 2.6 kernel from /extra -- old box is a compiled 2.6 kernel, differences in firewall (ip tables); old box was manually entered into 2wire -- new box I let it be auto discovered by the 2wire.
I'm simply going to backup my data off of the old box and then format and install Slack 11 on it. I'll also delete it from the 2wire. And then, when Slack 11 is on it up and running, I'll let the 2wire auto discover this box too.
Later on I may experiment with pointing resolv.conf to ISP's name servers. And I also want to try a Linux bridging firewall box in between my 2wire and my small LAN (I don't care that much for that 2wire -- if I knew of better alternative(s) to this 2wire 1701HG I'd do it and dump this 2wire 1701HG) (BTW I'm ready to hear of better alternative(s)
I'm not going to try and figure out just exactly why the old box's www browsing is slow and problematic due to www browsing on Slack 11 on another, new box is working so fast and superbly.