Hi, I've got a wireless interface (wlan0) that gets brought up using /etc/init.d/net.wlan0 with WPA and DHCP, and hence it gets backgrounded whilst everything else starts up. Since the recent udev update (089), it now gets started even earlier in the boot process. I am using dhcpcd-2.0.4-r1 (I can't entirely remember why I picked this one, I think it may've been mentioned in the handbook?) and baselayout 1.12.0_pre17-r1, with resolvconf-gentoo-0.1. So when I start /etc/init.d/net.wlan0 either from boot, or by stopping and restarting it manually, I get no entry in resolv.conf, resolvconf -l shows nothing and resolvconf -i shows an empty line. Catting a valid resolv.conf into resolvconf -a wlan0 works fine (and it starts to show up in resolvconf -l and -i), but vanishes when the interface is restarted. I also read the only other bug on resolvconf that I could find, and that recommended removing /var/lib/dhcpc/dhcpc-wlan0.info, and having done that there's still no effect (more interesting it doesn't seem to have been recreated), even though I definitely picked up the address. I don't really know what else to try, or how to diagnose the problem, but if there's anyway in which I can help, or any tests I can run for you, just let me know. Thanks!
What does running dhcpcd with the -d flag produce? Could you attach any dhcpcd syslog entries please?
Oh do I ever feel like a complete fool. I am so, so sorry for wasting your time... 5:( It turns out that I'd set it to a static address a few weeks ago and completely forgotten. Since it doesn't show whether DHCP's in use when it backgrounds for WPA, I had simply assumed I was still on dhcp. I appologize so much... SORRY!!!! 5:(
