From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Description of problem: The stock install of the bind packages with Fedora Core_1 create a /var/named/chroot directory. The chroot directory has the expected entries of dev etc and var. Looking in the var directory you have named run and temp. Again, ok. So up to this point we have gone as far as: /var/named/chroot/var drilling down another level shows that /var/named/chroot/var/named contains another chroot directory. This directory has a complete duplicate implemenation of everything in /var/named/chroot. Here is a sample output from /var/named/chroot: ls -R .: dev etc var ./dev: null random ./etc: named.conf rndc.key localtime named.custom ./var: named run tmp ./var/named: chroot localhost.zone named.ca named.local slaves ./var/named/chroot: dev etc var ./var/named/chroot/dev: null random ./var/named/chroot/etc: localtime named.conf named.custom rndc.key ./var/named/chroot/var: named run tmp ./var/named/chroot/var/named: ./var/named/chroot/var/run: named ./var/named/chroot/var/run/named: ./var/named/chroot/var/tmp: ./var/named/slaves: ./var/run: named ./var/run/named: ./var/tmp: [root@localhost chroot]# Version-Release number of selected component (if applicable): bind-chroot-9.2.2.P3-9.i386 How reproducible: Always Steps to Reproduce: 1. Install fedora Core_1 with DNS server components 2. After install, navigate directories 3. Actual Results: see sample output in description Expected Results: Why is the chroot environment duplicated? Additional info:
Here's a patch that gets rid of the duplicate chroot dir, on both installs and upgrades. It also moves the tempfile used in the bind-chroot %preun out of /tmp.
Created attachment 97382 [details] bind spec patch (for 9.2.3-5 spec)
Fixed in bind-9.2.3-13 Dan
fixed in bind-9.2.4-6+