Bug 123447

Summary: upgrading bind-chroot has device file issues
Product: [Fedora] Fedora Reporter: Chris Ricker <chris.ricker>
Component: bindAssignee: Jason Vas Dias <jvdias>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: bind-9.2.4rc6-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-04 14:24:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Ricker 2004-05-18 16:46:36 UTC
Upgrading from FC1 to FC2, I see:

Upgrading bind-chroot-9.2.3-13.i386.
warning: /var/named/chroot/dev/null created as
/var/named/chroot/dev/null.rpmnewwarning: /var/named/chroot/dev/random
created as /var/named/chroot/dev/random.rpmnew

Looking at the files, I now have:

]# ls -l /var/named/chroot/dev
total 0
crw-rw-rw-  1 root root  1, 3 Apr 16 20:13 null
-rw-r-----  1 root named    0 Mar 24  2003 null.rpmnew
crw-r-----  1 root named 1, 9 Apr 16 20:13 random
-rw-r-----  1 root named    0 Mar 14  2003 random.rpmnew
#

Comment 1 Jason Vas Dias 2004-08-04 14:24:43 UTC
fixed - bind-9.2.4rc6-4 now does mknod in the %post script.