OBSD 3.2 - Bind 9.2.2rc1 /dev/urandom error chrooted

[Mark_Andrews at isc.org]

> I have built many bind 9.2.2rc1 installs and they all run very well
> chrooted...until I worked on OpenBSD.
> 
> I created the links like normal:
> 
> /var/named/dev
> crw-rw-rw-  1 named  named    2,   2 Feb 13 21:23 null
> crw-rw-rw-  1 named  named   45,   0 Feb 13 21:23 random
> crw-rw-rw-  1 named  named   45,   2 Feb 13 21:23 urandom
> 
> 
> (verified against what is in /dev)
> crw-rw-rw-  1 root  wheel    2,   2 Feb 14 10:14 /dev/null
> crw-r--r--  1 root  wheel   45,   0 Feb 13 20:34 /dev/random
> crw-r--r--  1 root  wheel   45,   2 Feb 14 09:58 /dev/urandom
> 
> When I start named - this shows up:
> 
> Feb 14 09:59:46 michelob named[26462]: starting BIND 9.2.2rc1 -t
> /var/named -u named
> Feb 14 09:59:46 michelob named[26462]: using 1 CPU
> Feb 14 09:59:46 michelob named[26462]: loading configuration from
> '/etc/named.conf'
> Feb 14 09:59:46 michelob named[26462]: listening on IPv4 interface lo0,
> 127.0.0.1#53
> Feb 14 09:59:46 michelob named[26462]: listening on IPv4 interface em0,
> 192.168.45.10#53
> Feb 14 09:59:46 michelob named[26462]: command channel listening on
> 127.0.0.1#953
> Feb 14 09:59:46 michelob named[26462]: errno2result.c:109: unexpected error:
> Feb 14 09:59:46 michelob named[26462]: unable to convert errno to
> isc_result: 6: Device not configured
> Feb 14 09:59:46 michelob named[26462]: could not open entropy source
> /dev/urandom: unexpected error

	Choose a filesystem that doesn't have devices disabled for
	the chroot area.

	Mark
> 
> 
> Since I feel I know what I am doing (it works on all other OS's I have
> tested and setup) - what am I missing here?
> 
> Is this an OBSD issue and if so, is there a work around?
> 
> Thanks...
> 
> {jeff}_[bronson]*at*ktxgDOTcom
> 
> 
> 
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org