David Baron wrote:
This is being created, apparently by a /etc/qmeu-ifup.... (there are several) with major 250, minor 0.kqemu.ko gets placed in misc. Implication is major==10? There is no entry in /proc/devices (and this cannot be simply edited).kqemu has a minor value of 63 in /proc/misc. So what really should be going on here?
Hi, David, I have Qemu installed on my Debian system. What I have looks like this: $ l /dev/kq* crw-rw-rw- 1 root root 10, 63 2007-01-29 15:55 /dev/kqemu $ ls /etc/*qemu* ls: /etc/*qemu*: No such file or directory $ find /lib/modules -name '*qemu*' /lib/modules/2.6.17-2-686/misc/kqemu.ko /lib/modules/2.6.18-3-686/misc/kqemu.ko $ lsmod | grep qemu kqemu 107620 0 $ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. loop sbp2 kqemu major=0 ===This last item is what makes /dev/kqemu with major number 10 (I believe that's because major 10 is available for use and is picked dynamically during the boot process, so it could be something different if some other driver loads first).
The /etc/qemu-ifup file is part of the Qemu network setup when using the tun/tap devices (which I don't use, as yet) and so have nothing to do with the device node for kqemu itself.
Hope this is helpful. Bob
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature