Nick Morrott wrote:
On 03/02/07, Gary Desrochers <GaryBrenda@comcast.net> wrote:
  
I am having a problem that I thought I already fixed.

The problem started when I upgraded to FC 6 from FC5.  Mostly everything
is working okay except for lirc.  I can no longer use the remote on my
150.  It all seems to be because I have no /dev/lirc directory.
    

/dev/lirc is a LIRC device, not a directory.

  
Yes, I realize I put the wrong term for it after I reread the message after sending.  I am glad you knew what I meant.

  
And also from the /var/log/messages:
Feb  3 15:59:40 SeaStorm lircd-0.8.1-CVS[2193]: lircd(userspace) ready
Feb  3 15:59:40 SeaStorm lircd-0.8.1-CVS[2193]: accepted new client on
/dev/lircd
Feb  3 15:59:40 SeaStorm lircd-0.8.1-CVS[2193]: could not get file
information for /dev/lirc
Feb  3 15:59:40 SeaStorm lircd-0.8.1-CVS[2193]: default_init(): No such
file or directory
Feb  3 15:59:40 SeaStorm lircd-0.8.1-CVS[2193]: caught signal

Any ideas with this?  the /dev directory has no /dev/lirc.
    

You can have lircd start using a different device - usually
/dev/lirc0. You can add the lircd options to /etc/sysconfig/lircd.

  

  
I used to have a file lirc.rules in the /etc/udev/rules.d directory with:
KERNEL="lirc[0-9]*",    NAME="lirc%n"
KERNEL="lirc0",         SYMLINK="lirc"
in it.  But they give errors now.
    

What udev errors are you seeing? The /dev/lirc symlink should be
created when the /dev/lirc0 device is created, via your udev rule.

Nick
  

I figured it out.  The new udev requires a double "=" so the /etc/udev/rules.d/lirc.rules file should now be:
KERNEL=="lirc[0-9]*",    NAME="lirc%n"
KERNEL=="lirc0",         SYMLINK="lirc"
I appreciate the response though.  Thanks.

Gary