Comment 35 for bug 1621507

I just had the thought.. is there any reason that we are using dhclient for ipv4 rather than leaving the old path in place entirely for ip= ?

If we just change back to letting klibc's ipconfig take care of the ipv4 dhcp, then that resolves my 'b' and 'c' (for the ipv4 case).

We can then also go back to the original test for "done" of just checking for presense of /run/net-"$DEVICE".conf to idnicate ipv4 is done. All in all, the change to taking 'ip6=' on the command line makes it fairly easy to ensure we do not regress the ipv4 use case.