Doing a new machine installation, installed bind, enabled chroot, ran emerge --config net-dns/bind, but starting fails: # /etc/init.d/named start * Starting chrooted named ... [ !! ] * Your chroot dir /chroot/dns is inconsistent, please run 'emerge --config net-dns/bind' first * ERROR: named failed to start Seems like commit https://github.com/gentoo/gentoo/commit/03b0458f99af0352b933bec57b7aff351f2c4480 removed /dev/random in pkg_config(), but the init script requires /dev/random to be present https://github.com/gentoo/gentoo/blob/master/net-dns/bind/files/named.init-r13#L80 After removing /dev/random from check_chroot() it seems to start and work fine. Not sure however if it's really needed in the chroot.
net-dns/bind-9.16.15::gentoo was built with the following: USE="caps dlz zlib -berkdb -dnsrps -dnstap -doc -fixed-rrset -geoip -geoip2 -gssapi -json -ldap -lmdb -mysql -odbc -postgres -python (-selinux) -static-libs -xml" ABI_X86="(64)" PYTHON_TARGETS="python3_8 python3_9"
Seeing same thing, same or similar to #673746 In that and my case urandom was missing, so during install I now copy that over. https://github.com/ASoft-se/Gentoo-HAI/pull/55 Current config "emerge --config net-dns/bind" does most of the setup And then init script verifies that everything exists. Instead of the init script failing, maybe it could try and actually fix the issue. Or say some details about what is wrong instead of only "is inconsistent"
fixed as https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e8faaad077caf9048e2c5a132ddade0b0b316aa I've killed it by mistake for chroots.
