http://qa.mandrakesoft.com/show_bug.cgi?id=5286





------- Additional Comments From [EMAIL PROTECTED]  2003-07-09 04:46 -------
[EMAIL PROTECTED] mythtv]# rm -rf /dev/lirc
[EMAIL PROTECTED] mythtv]# ls -l /dev/li*
srw-rw-rw-    1 root     root            0 Sep  5 02:58 /dev/lircd=
prw-r--r--    1 root     root            0 Sep  5 02:58 /dev/lircm|
[EMAIL PROTECTED] mythtv]# shutdown -r now

After reboot:

[EMAIL PROTECTED] mythtv]$ su
[EMAIL PROTECTED] mythtv]# ls -l /dev/li*
srw-rw-rw-    1 root     root            0 Sep  6 15:00 /dev/lircd=
prw-r--r--    1 root     root            0 Sep  6 15:00 /dev/lircm|

/dev/lirc:
total 0
drwxr-xr-x    1 root     root            0 Sep  6 15:00 0/
drwxr-xr-x    1 root     root            0 Sep  6 15:00 61/
drwxr-xr-x    1 root     root            0 Sep  6 15:00 c/
[EMAIL PROTECTED] mythtv]#

So, _something_ is creating these files rather than the character device at
major 61, minor 0.

Is makedev.d/mandrake the culprit?


-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEEDINFO
creation_date: 
description: 
Running lirc0.7.0pre2 (self compiled because it's not in contrib) to support
Hauppauge PVR-250 remote.  lirc_i2c is the device driver.

After rebooting, these are the entries in /dev:
[EMAIL PROTECTED] mythtv]# ls -l /dev/li*
srw-rw-rw-    1 root     root            0 Sep  5 02:58 /dev/lircd=
prw-r--r--    1 root     root            0 Sep  5 02:58 /dev/lircm|

/dev/lirc:
total 0
drwxr-xr-x    1 root     root            0 Sep  5 02:58 0/
drwxr-xr-x    1 root     root            0 Sep  5 02:58 61/
drwxr-xr-x    1 root     root            0 Sep  5 02:58 c/

Note that the /dev/lirc directory has three _files_ in it, rather than creating
the correct character device.  According to the lirc0.7.0pre2 docs, the correct
device would be created with mknod /dev/lirc c 61 0

Reply via email to