Package: kqemu-common Version: 1.3.0~pre11-1 Severity: serious Justification: Policy 10.6
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The package creates /dev/kqemu in its postinst. According to policy it must instead create the device via the MAKEDEV script. Also, on udev-using systems, the device should be created in /dev/.static/dev/kqemu, so that it actually ends up in /dev on my root filesystem rather than in udev's tmpfs mounted at /dev. I guess using MAKEDEV would sort this out. Finally, I'm a bit confused about how udev is intended to interoperate with kqemu. I moved the /dev/kqemu created by kqemu-common's postinst out of the way, and then loaded the kqemu module, to see if udev would correctly create the /dev/kqemu device. It did create a file with the right name, but with different major/minor numbers: crw-rw-rw- 1 root root 10, 62 2007-02-12 11:03 /dev/kqemu crw-rw-rw- 1 root root 250, 0 2007-02-12 10:46 /dev/kqemu.old Assuming that the module is passing the correct major/minor device numbers to the kernel when it creates its device, is the use of 250/0 incorrect? Or is it correct as well? - -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF0E1Gshl/216gEHgRAtCiAKDGH5jTl0M1Ubr6UXI7BCLOsL7cMwCcCD7+ 5S6nmSgHKybD05/zXmVVbfc= =vc6V -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
