I emerged baselayout-1.12.0_pre7 last night, and my system has a hard time booting. It is trying to assign 127.0.0.1 for the localhost address and fails, sitting for a long time in a loop. After 2 mins I can hit ctrl-C and get the boot to continue, but there is no lo address assigned. I can start up my wireless adapter and have an eth1 ip address assigned, but if I try to start samba, samba fails with no local loopback ip address. A series of messages come up at the time of trying to activate the lo device (a bunch of SIOCXXXX messages which I can't reproduce now exactly because they aren't in front of me on my working machine right now), but the ending message is initially can't find file, and the rest of them are can't assign address. Another notable is that at the end of the baselayout emerge, etc-update is apparently unaware of any config files that might need to be changed, and tells me nothing needs to be done, which, in my experience, is unusual after a baselayout emerge. To get my machine back & running, I have had to revert back to baselayout-1.11.13-r1 which thankfully was still on my harddrive. Reproducible: Always Steps to Reproduce: 1.emerge sync (Keyword=~x86) 2.emerge baselayout 3.reboot Actual Results: my system has a hard time booting. It is trying to assign 127.0.0.1 for the localhost address and fails, sitting for a long time in a loop. After 2 mins I can hit ctrl-C and get the boot to continue, but there is no lo address assigned. If I do an ifconfig, no network devices (especially lo) show. I cannot ping 127.0.0.1 either. Expected Results: lo should have 127.0.0.1 assigned and appear in the ifconfig listing. Additionally I should be able to ping 127.0.0.1.
Happened to me too, I
Happened to me too, I´m downgrading to pre6 for the time being. Error messages: * Starting lo * Bringing up lo * 127.0.0.1/8 SIOCSIFADDR: File exists SIOCSIFFLAGS: Cannot assign requested address SIOCSIFNETMASK: Cannot assign requested address SIOCSIFBRDADDR: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address
This bug is a duplicate of bug #104415 I'm not a developer and can't mark it. bug #104415 is fixed FYI.
*** This bug has been marked as a duplicate of 104415 ***
