diff options
| author |   kn <kn@openbsd.org> | 2021-03-12 11:32:03 +0000 |
|---|---|---|
| committer | kn <kn@openbsd.org> | 2021-03-12 11:32:03 +0000 |
| commit | 13c27aa6861b5ddf2842a257786779b4fea490af (patch) | |
| tree | a5946cebcc5f6500edf03948bb36efdaacd39108 /sys/uvm/uvm_pmemrange.c | |
| parent | spelling (diff) | |
| download | wireguard-openbsd-13c27aa6861b5ddf2842a257786779b4fea490af.tar.xz wireguard-openbsd-13c27aa6861b5ddf2842a257786779b4fea490af.zip | |
Emulate "[inet] autoconf" hostname.if(5) lines with "dhcp"
With dhcpleased(8) in base, netstart(8) and ifconfig(8) understand both
"autoconf" and "inet autoconf" lines in hostname.if(5) files to signal the
new daemon.
The installer however currently has only dhclient(8), hence manual upgrades
with "[inet] autoconf" instead of "dhcp" in hostname.if files would fail to
establish IPv4 connectivity.
Make install.sub's netstart clone treat autoconf lines like old fashioned
dhcp lines such users^Wearly testers of the new approach don't get stuck in
nyetwork land.
Note that this is only relevant for manual upgrades; installation always
creates working hostname.if files and automated upgrades with sysupgrade(8)
do not care about network/hostname.if files.
Idea from deraadt
OK deraadt krw ajacoutot
Diffstat (limited to 'sys/uvm/uvm_pmemrange.c')
0 files changed, 0 insertions, 0 deletions