After emerging upgrading to and booting up the next day, /etc/init.d/net.eth0 failed stating that iproute2 needs to be emerged, even thou my configuration was set to use DHCP. Reproducible: Always Steps to Reproduce: /etc/init.d/net.eth0 start Actual Results: * Starting eth0 * For iproute2 support, emerge sys-apps/iproute2 Expected Results: * Caching service dependencies ... [ ok ] * Starting eth0 * Bringing up eth0 * dhcp * Running dhcpcd ... [ ok ] * eth0 received address 10.0.0.31/24 Even removing the configuration file (which is supposed to default everything to DHCP) didn't help. I managed to get online by substituting umods=( "${umods[@]}" "iproute2" "dhcpcd" "iwconfig" "netplugd" ) for umods=( "${umods[@]}" "dhcpcd" "iwconfig" "netplugd" ) in /etc/init.d/net.eth0 (or net.lo if you prefer).
Please attach the contents of conf.d/net and conf.d/wireless (if it exists) using the "Create a new Attatchment" link above
Created attachment 70435 [details] /etc/conf.d/net Here you go, although an empty configuration file resulted in the same bug on my machine...
OK, could you set RC_VERBOSE="yes" in conf.d/rc (add it as a new variable) and post the output of eth0 starting again please? Thanks
* Starting eth0 * Loading networking modules for eth0 * For iproute2 support, emerge sys-apps/iproute2
Created attachment 70438 [details, diff] Fixes net.lo This patch to net.lo fixes the issue
It really does! :P Thank You! :)
Fixed in baselayout-1.12.0_pre9-r1
*** Bug 108991 has been marked as a duplicate of this bug. ***
*** Bug 109131 has been marked as a duplicate of this bug. ***
