From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux; X11; , en_US.UTF-8, en_US, en)

Description of problem:
The bind-chroot rpm creates:

	/var/named/chroot/dev/null
	/var/named/chroot/dev/random

Neither of these dev files are needed.  A:

	lsof -p $(pidof named)

will show that neither /dev/null nor /dev/random are open.
Removal of these files /var/named/chroot/dev/* files does
not seem to impare named.

Creation of /var/named/chroot/dev/ special files gives the
impression that the /var file system cannot be mounted with
the nodev option.  The /var file system can be mounted with
nodev (and should for security reasons).  By removing these
unnecessary dev files from the bind-chroot package, the /var
filesystem can remain special device free.

Version-Release number of selected component (if applicable):
bind-chroot-9.2.2-21

How reproducible:
Always

Steps to Reproduce:
1.install bind and bind-chroot
2.rm -rf /var/named/chroot/dev
3.service named start
    

Actual Results:  The bind daemon will run without any problem without the
/var/named/chroot/dev files.

Expected Results:  If /var/named/chroot/dev was required, a problem with
bind would have noticed.

Additional info: