Contributed by rueda on from the dhcplease-resolv-me dept.
The commits are,
CVSROOT: /cvs Module name: src Changes by: firstname.lastname@example.org 2021/07/16 09:21:41 Modified files: etc : netstart rc.conf Log message: switch to dhcpleased/resolvd in base OK deraadt
in the ramdisk,
CVSROOT: /cvs Module name: src Changes by: email@example.com 2021/07/16 09:24:09 Modified files: distrib/alpha/miniroot: list distrib/amd64/ramdisk_cd: list distrib/arm64/ramdisk: list distrib/armv7/ramdisk: list distrib/hppa/ramdisk: list distrib/i386/ramdisk: list distrib/i386/ramdisk_cd: list distrib/landisk/ramdisk: list distrib/loongson/ramdisk: list distrib/luna88k/ramdisk: list distrib/macppc/ramdisk: list distrib/octeon/ramdisk: list distrib/powerpc64/ramdisk: list distrib/riscv64/ramdisk: list distrib/sparc64/miniroot: list Log message: Replace dhclient with dhcpleased/resolvd on the ramdisk. OK deraadt who also helped making some space.
and in the installer:
CVSROOT: /cvs Module name: src Changes by: firstname.lastname@example.org 2021/07/16 09:25:31 Modified files: distrib/miniroot: install.sub Log message: Switch from dhclient to dhcpleased in the installer. More cleanup is needed from a real ksh hacker, but looks already pretty good to kn. OK deraadt
on misc@, Theo de Raadt (
explained some of the rationale:
[…] We are moving from a model where dhclient on 1 interface believes it is MASTER of /etc/resolv.conf and a bunch of system aspects, and the userbase is familiar with a pile of hacky control knobs in dhclient.conf. Towards a model where multiple interfaces + unwind can advertise their DNS resolution abilities to resolvd, which then sorts the offers and maintains a configuration. dhclient will remain available for people who want that old model, but I suspect they will encounter increasing difficulty sticking to it. Because the default configuration is changing. […]
(Comments are closed)