When installing 11.0-BETA3 (on an amd64 VMware guest), the dialog "Choose the services you would like to be started at boot" does not seem to be functional anymore, in the sense that enabled services do NOT end up in the final rc.conf on the target installation. For example, if I check sshd, ntpd and dumpdev, the final rc.conf becomes: hostname="beta3test" ifconfig_em0="DHCP" ifconfig_em0_ipv6="inet6 accept_rtadv" zfs_enable="YES" Note the missing sshd_enable, ntpd_enable and dumpdev settings. This also applies to Auto UFS setups, where the only difference is that there is no zfs_enable line.
A commit references this bug: Author: dim Date: Mon Aug 1 19:49:43 UTC 2016 New revision: 303631 URL: https://svnweb.freebsd.org/changeset/base/303631 Log: Fix non-functional bsdinstall services dialog. The most recent version of bsdinstall does not seem to respect any of the checkboxes in the "Choose the services you would like to be started at boot" dialog. None of the chosen services end up in the rc.conf file that is installed onto the target system. This is caused by the bsdinstall/scripts/hardening script, which implements the new hardening options dialog. The script starts by overwriting the previously written rc.conf.services file: echo -n > $BSDINSTALL_TMPETC/rc.conf.services which is obviously incorrect. It should clear out rc.conf.hardening instead. Reviewed by: allanjude PR: 211506 MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D7387 Changes: head/usr.sbin/bsdinstall/scripts/hardening
Over to committer for possible MFC.
A commit references this bug: Author: dim Date: Thu Aug 4 17:26:33 UTC 2016 New revision: 303749 URL: https://svnweb.freebsd.org/changeset/base/303749 Log: MFC r303631: Fix non-functional bsdinstall services dialog. The most recent version of bsdinstall does not seem to respect any of the checkboxes in the "Choose the services you would like to be started at boot" dialog. None of the chosen services end up in the rc.conf file that is installed onto the target system. This is caused by the bsdinstall/scripts/hardening script, which implements the new hardening options dialog. The script starts by overwriting the previously written rc.conf.services file: echo -n > $BSDINSTALL_TMPETC/rc.conf.services which is obviously incorrect. It should clear out rc.conf.hardening instead. Approved by: re (kib) Reviewed by: allanjude PR: 211506 Differential Revision: https://reviews.freebsd.org/D7387 Changes: _U stable/11/ stable/11/usr.sbin/bsdinstall/scripts/hardening
Committed to head and merged to stable/11 in time for 11.0-RELEASE.