Mär 30 10:23:01 tine.local systemd[1]: Started Create list of required stat....Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.Hint: Some lines were ellipsized, use -l to show in full.

Since the update this morning my dhcp is not working properly.The Network-Manager starts and tries endlessly to connect to the wireless network.

I checked the systemctl and kmod-static-nodes.service failed, so I created the softlink which was recommended above and now kmod-static-nodes.service is "loaded active exited", but dhcp is still not working.

If I check dmesg and systemctl status NetworkManager.service (edit) I get the following informations:

I got wicd running, but as expected it didn't solved the problem with dhcpcd and unfortunately it also did not worked with dhclient.Finally I installed connman which works nice and fast. The only thing I miss is the nm-openconnect plug-in, connman has native openconnect support, but the USE flag is -openconnect.

@Fitzcarraldo: I tried the solution by soupdragon, but it didn't solve the problem. I checked systemctl and there was no dhcpcd.service running. If I understand the NetworkManager status and the dmesg above right, NetworkManager has no problems with starting dhcpcd, but at one during the dhcp process dhcpcd simply crashes. One can also see in the journal what happens between two crashes:

Yes there only one programm running/enabled which handles the network connections. When the problem appeared only NetworkManager was installed. The other two programs were installed later. Tonight I will have a look for the logs, of wicd with dhcpcd.

about the mkdir problem: a bug in an old coreutils ebuild was the cause of the mess between /usr/bin/mkdir and /bin/mkdir. I have been able to track it down and I am about to push a fixed sys-apps/systemd-208-r3 into sabayonlinux.org (weekly users will get the fix in 3 days).