On Sun, 15 Jul 2018, John D. Baker wrote:
On Mon, 16 Jul 2018, Roy Marples wrote:
Sadly, all my machines are x86 based. I have an ERLITE mips router where I
also run dhcpcd, and it doesn't stamp on routes there either, so I'm pretty
sure this isn't an arch issue ... but I could be wrong.
The only route that was an issue was the local route to the NFS server.
Somehow a netbooted x86 system can complete the configuration, but
non-x86 dies as soon as 'dhcpcd' (or the earlier 'dhclient') touches
the interface. Interface is downed, root file system is gone, can't
bring interface back up, game over.
I've got a fresh build of -current just installed for the netbooted
Lemote YeeLoong. Need to give it a whirl with "dhcp" in the
"ifconfig.rtk0" file and see if the situation has changed.
Well, what do you know! The YeeLoong successfully used 'dhcpcd' upon
netbooting. And with "env force_hostname=YES", it gets an FQDN instead
of its short name (only).
And a SPARCstation 5 netbooting -8 has just done the same. Looks like
a winner.