Duncan posted on Sat, 23 May 2015 08:17:59 +0000 as excerpted: > Off for a 1 AM sync and some testing, now... if I don't get too sleepy > to think straight first. Still 219 with those patches applied if 220 > isn't in-tree yet when I sync. I'll post back when I have some results.
Well, back with a mixed report... still on 219_p112 as 220 still hadn't made it to the tree. Upstream's patch for the tmpfiles/subvolumes/dirs thing worked perfect. =:^) The gentoo-bug proposed patch to get IPv4-only working again... not so much. It addressed one complaint in the log, but that wasn't the major problem, apparently, and networkd still doesn't bring up the network properly. But, while I was testing, I tested something that another poster had noted on the upstream IPv4 bug -- networkd appears to be configuring the interface, just not bringing it up. So a simple ifconfig <iface> up (what I used, or equivalent IP command, which is what he used) brings the interface up, configured as it should be. =:^) Between the two, I think I'll stick with 219_p112 instead of reverting back to 218-r3, for now. The tmpfiles.d thing is fixed by the upstream patch I dropped into /etc/portage/patches/sys-apps/systemd before the rebuild, and I can do a manual ifconfig up after reboot for now, or setup a quick service to automate it if I get tired of doing the manual ifconfig thing. So mixed report, but there's progress, and a workaround for the remaining issue, so 219_p112 with additional patches and a manual workaround it is, for now. =:^/ -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
