This project is intented for all release related issues (isos, installer, etc), under the umbrella of the ArchLinux Release Engineers
FS#49983 - dhcpcd stalls booting when NIC is not connected since 2016.07
Attached to Project:
Release Engineering
Opened by Tom Yan (tom.ty89) - Thursday, 07 July 2016, 09:08 GMT
Opened by Tom Yan (tom.ty89) - Thursday, 07 July 2016, 09:08 GMT
|
DetailsThe title pretty much told it all. Also attached a screenshot.
It's probably due to an (un)intentional change in dhcpcd. The thing is, why are we STILL sticking to dhcpcd, instead of the more decent dhclient, or, systemd-networkd? |
This task depends upon
https://lists.archlinux.org/pipermail/arch-releng/2014-February/003365.html
elif [[ "${copy_resolvconf}" != "n" && -f /etc/resolv.conf ]]; then #if copytoram=n
cp /etc/resolv.conf /new_root/etc/resolv.conf
What was the point of this parameter anyway? Maybe it should be obsoleted and we will just always do the (rm and) symlink in this /newroot (i.e. /newroot/etc/resolv.conf -> /newroot/run/systemd/resolve/resolv.conf), and make sure resolved is (re?)started after "switiching root"?
P.S. Sorry I don't really know about PXE boot