On Sat, May 06, 2006 at 11:19:03AM -0700, Ralph Alvy wrote:
> On Sat May 6 2006 10:33 am, Ralph Alvy wrote:
> > On Sat May 6 2006 7:46 am, ubunt2 at gmail.com wrote:
> > > Regarding
> > > http://www.jpilot.org/pipermail/jpilot/2006-January/005739.html
> > >
> > > It says something about "/etc/udev/rules.d/visor.rules "
> > > i went to "/etc/udev/rules.d/" but couldn't find a file named visor.rules
> >
> > Under Mepis 6 Beta 2 (which is essentially Kubuntu Dapper), I put that
> > single line the end of /etc/udev/mepis.rules. It works fine, as long as
> > JPilot is already loaded before you hit the cradle button.
You should create the file named 10-visor.rules if it doesn't already
exist. Generally, you should *not* edit an existing file in the
/etc/udev or /etc/udev/rules.d directory. There are two reasons for
this: 1) when you update your system, if there's a udev update it is
likely to replace your changes, and 2) the order in which the rules are
read is important.
I'm not familiar with Mepis, so it's possible that the mepis.rules file
is a "local" file intended for the user to make local changes to, and
therefore not touched by the update process. If that is the case, then
that will address point 1 above, but not point 2.
> Later ... I just tried doing something similar under CentOS 4.3 (essentially
> Redhat Enterprise Linux 4). I placed the single line at the end
> of /etc/udev/rules.d/50-udev.rules, and it fails to even create a symlink for
> pilot. I also tried placing it at the beginning of that file, and it fails
> again. I also tried changing the group assignment on that line from usb to
> uucp (which CentOS likes to assign to ttyUSBx), but that fails to help
> anything.
Adding the rule to the end of 50-udev.rules won't work, because there is
probably already an existing rule for the device file that the palm
uses, and the kernel will use the first rule that it finds. That's why
it is important to put the rule in a file named "10-visor.rules": the
"10" part will get sorted before the "50" in 50-udev.rules, so the udev
system will read that file first.
For more information on udev and udev rules, here are two very good
primers:
http://www.reactivated.net/writing_udev_rules.html
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html
Jason
--
Jason Day jasonday at
http://jasonday.home.att.net worldnet dot att dot net
"Of course I'm paranoid, everyone is trying to kill me."
-- Weyoun-6, Star Trek: Deep Space 9
More information about the jpilot mailing list