Bug#410294: kqemu-common: Stop creating /dev/kqemu
Package: kqemu-common Version: 1.3.0~pre9-12 Severity: serious Justification: Policy 10.6 kqemu creates a device file in its postinst script using mknod. This violates Debian Policy 10.6. Additionally, it breaks usage of kqemu because it creates the node with the wrong device numbers (kqemu is configured to dynamically assign device numbers). If at all, it should use MAKEDEV to create the device node which spares udev system of such breakage. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.1-server Locale: LANG=en_US.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410294: kqemu-common: Stop creating /dev/kqemu
severity 410294 normal tags 410294 pending thanks kqemu creates a device file in its postinst script using mknod. This violates Debian Policy 10.6. no. it is only a policy violation *iff* MAKEDEV knows about the device. it is already requested for inclusion, see #407345. Additionally, it breaks usage of kqemu because it creates the node with the wrong device numbers (kqemu is configured to dynamically assign device numbers). the number is not wrong and does work here, what makes it failing for you? If at all, it should use MAKEDEV to create the device node which spares udev system of such breakage. again, MAKEDEV does not (yet) know about it. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410294: kqemu-common: Stop creating /dev/kqemu
On Friday 09 February 2007, Daniel Baumann wrote: severity 410294 normal tags 410294 pending thanks kqemu creates a device file in its postinst script using mknod. This violates Debian Policy 10.6. no. it is only a policy violation *iff* MAKEDEV knows about the device. it is already requested for inclusion, see #407345. ok. (although I doubt it will be accepted, major 250 is in the range intended for local/experimental uses) Additionally, it breaks usage of kqemu because it creates the node with the wrong device numbers (kqemu is configured to dynamically assign device numbers). the number is not wrong and does work here, what makes it failing for you? kqemu uses a dynamically assigned device number (default in 1.3.0pre11), on my system it used (10, 62) the last time. Udev did the right thing(tm) in this case and tried to create the correct device node, but failed because it already existed (due to the postinst). $ cat /etc/modprobe.d/kqemu options kqemu major=0 $ ls -la /dev/kqemu crw-rw-rw- 1 root root 10, 62 2007-02-09 14:34 /dev/kqemu If at all, it should use MAKEDEV to create the device node which spares udev system of such breakage. again, MAKEDEV does not (yet) know about it. Then the postinst has to check for udev, and not create the node if it is in use. (although this won't prevent using the wrong major/minor numbers) Alex. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
