irda connection

[Paul M. Bucalo]

On Sat, 2005-06-04 at 17:00 +0200, S. Donig wrote:
> Am Freitag, den 03.06.2005, 12:18 +0200 schrieb Albin Blaschka:
> > Hello,
> > 
> > one question concerning the missing devices: what's about udev and 
> > permissions when I create the devices?
> > 
> > Thanks in advance,
> > Albin
> > 
> I see no problem here. By default Ubuntu's udev-implementation seems to 
> blank the /dev directory on startup. (So your changes are erased when you 
> boot the next time in your box.)
> I've never come up with a solution for automatically creating the devices.
> Theoretically it *should* work out of the box. 

Albin & Simon,

With the implementation of udev and use of hotplug under kernel-2.6.x, a
lot of devices are now created on each boot-up and on-the-fly via rules.
It may be that you need to setup a rule that allows udev to properly
setup /dev and associated link for your irda port. 

I played around a bit with rule making when I resolved an issue with
getting my Palm device to sync with gpilotd in FC 3. After I found a
syntax that worked, it worked all the time. 

Take a look at '/etc/udev/rules.d/udev.rules' for some examples as well
as set parameters that apply to your system. You might only need to
tweak a rule. Permissions appear to be rectified automatically once the
device is "described" here and therefore picked up on boot-up or through
hotplug live.

By the way, if you decide to add or change a rule, you need to put such
changes or additions into a separate file. Any changes you make to
udev.rules are subject to being wiped out in a future update. The file
is replaced from time to time, but what you create otherwise is not. A
little Googling on 'udev.rules' will give you some ideas how to do this.
I tried to find some links I used earlier this year on Fedora Core 3,
but couldn't come up with any joy. Sorry. :0(

HTH

Paul