Re: [TLUG]: FC4: Ways to use PalmPilot

I found I was able to use JPilot, and it appears to do what I want. 
But I seem to have run into a "feature" in FC4 which resets the 
permissions on /dev/ttyS0 to 660 from 666.

I have looked through the kernel docs, and I do not suspect the 
kernel is doing this. Any suggestions as to what is responsible for 
resetting these permissions, and how do I make these changes 
permanent?

Paul King
> Paul Mora ([e-mail]) wrote:
>
> Hi.
>
> I have used both Evolution, and KPilot (the KDE sync program). Both
> are pretty good, but both also have their issues.
>
> Right now, I'm using the KPilot program from KDE 3.4, and it seems to
> work well. It will sync pretty much everything, but it only syncs it
> into e KDE PIM (Kontact), and it's components (KAddressbook,
> KOrganizer, etc.)
>
> If you're looking for something exactly like the Palm desktop, look no
> further than JPilot.
>
> pm
>
> -- 
> Paul Mora
> email: [e-mail]

[TLUG]: FC4: Ways to use PalmPilot

[Christoph Wickert]

Am Mittwoch, den 31.08.2005, 10:26 -0400 schrieb [e-mail]:
> I found I was able to use JPilot, and it appears to do what I want. 
> But I seem to have run into a "feature" in FC4 which resets the 
> permissions on /dev/ttyS0 to 660 from 666.
>
> I have looked through the kernel docs, and I do not suspect the 
> kernel is doing this. Any suggestions as to what is responsible for 
> resetting these permissions, and how do I make these changes 
> permanent?

echo "<console> 0660 /dev/ttyS0 0666 root.uucp"
> /etc/security/console.perms.d/10-pilot.perms

(single line!)
> Paul King

Christoph

[TLUG]: FC4: Ways to use PalmPilot

[Robert Locke]

On Wed, 2005-08-31 at 10:26 -0400, [e-mail] wrote:
> I found I was able to use JPilot, and it appears to do what I want. 
> But I seem to have run into a "feature" in FC4 which resets the 
> permissions on /dev/ttyS0 to 660 from 666.
>
> I have looked through the kernel docs, and I do not suspect the 
> kernel is doing this. Any suggestions as to what is responsible for 
> resetting these permissions, and how do I make these changes 
> permanent?
>
> Paul King

Hi Paul,

You are battling with udev....  Turns out that every time you reboot,
the /dev/ directory is wiped out.  The files are regenerated by udev
when the system boots or you and I dynamically plug something in.

Now you can look to manipulate the udev rules to automatically create
your symlink of /dev/pilot, for example, there are several examples in
the archives.  But the system should probably already have a rule to
assign the "logged-in user" as the owner of the serial port or any
dynamically created USB ports....  You can see some of this
in /etc/udev/rules.d/....

--Rob

[TLUG]: FC4: Ways to use PalmPilot

[Craig White]

On Wed, 2005-08-31 at 12:02 -0400, Robert Locke wrote:
> On Wed, 2005-08-31 at 10:26 -0400, [e-mail] wrote:
> > I found I was able to use JPilot, and it appears to do what I want. 
> > But I seem to have run into a "feature" in FC4 which resets the 
> > permissions on /dev/ttyS0 to 660 from 666.
> >
> > I have looked through the kernel docs, and I do not suspect the 
> > kernel is doing this. Any suggestions as to what is responsible for 
> > resetting these permissions, and how do I make these changes 
> > permanent?
> >
> > Paul King
>
> Hi Paul,
>
> You are battling with udev....  Turns out that every time you reboot,
> the /dev/ directory is wiped out.  The files are regenerated by udev
> when the system boots or you and I dynamically plug something in.
>
> Now you can look to manipulate the udev rules to automatically create
> your symlink of /dev/pilot, for example, there are several examples in
> the archives.  But the system should probably already have a rule to
> assign the "logged-in user" as the owner of the serial port or any
> dynamically created USB ports....  You can see some of this
> in /etc/udev/rules.d/....

---
YMMV
you might want to check out this web site...
http://www.reactivated.net/writing_udev_rules.html

# cat /etc/udev/rules.d/10-udev.rules
KERNEL="ttyUSB1",SYMLINK="pilot"

# cat /etc/udev/permissions.d/10-udev.permissions
#set Palm Pilot rwx
pilot*:craig:usb:0666

Craig

[TLUG]: FC4: Ways to use PalmPilot

[Pete Toscano]

Craig White wrote:
> YMMV
> you might want to check out this web site...
> http://www.reactivated.net/writing_udev_rules.html
>
> # cat /etc/udev/rules.d/10-udev.rules
> KERNEL="ttyUSB1",SYMLINK="pilot"
>
> # cat /etc/udev/permissions.d/10-udev.permissions
> #set Palm Pilot rwx
> pilot*:craig:usb:0666

I think, in FC4, that the permissions files have been removed and the
functionalitys been moved into the rules files.  That said, there really
seems to be some weirdness with the rules files, priority, and how to
change things like permissions, group, and owner.

See my response to the (now closed) bug 165888 in Bugzilla:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=165888

pete

[TLUG]: FC4: Ways to use PalmPilot

I wonder what would happen if I created a directory for the device, 
and in that directory, I created the device statically with the 
permissions and ownerships I want and then udev can go do whatever it 
likes.

It seems to be a better than delving into /etc/udev, and dealing with 
a whole other set of intricacies. It's an idea I have, and I am just 
going to try it.

Thanks for everyone's help so far!

Paul King
> Robert Locke ([e-mail]) wrote:
>
> You are battling with udev....  Turns out that every time you reboot,
> the /dev/ directory is wiped out.  The files are regenerated by udev
> when the system boots or you and I dynamically plug something in.
>
> Now you can look to manipulate the udev rules to automatically create
> your symlink of /dev/pilot, for example, there are several examples in
> the archives.  But the system should probably already have a rule to
> assign the "logged-in user" as the owner of the serial port or any
> dynamically created USB ports....  You can see some of this in
> /etc/udev/rules.d/....
>
> --Rob

Permissions on /dev/hd* are reset on every boot

[Marcelo Magno T. Sales]

Hi,

I have noticed that every time I boot FC4, permissions on /dev/hd*
devices are reset to 640. However, I need them to be set as 660
permanently. Why are these permissions automatically reset on boot and
how could I make them stay as 660?

Thanks,

Marcelo

Permissions on /dev/hd* are reset on every boot

[Thomas Springer]

=== Date : Wed, 31 Aug 2005 17:42:57 -0300
=== From : Marcelo Magno T. Sales
> Hi,
>
> I have noticed that every time I boot FC4, permissions on /dev/hd*
> devices are reset to 640. However, I need them to be set as 660
> permanently. Why are these permissions automatically reset on boot and
> how could I make them stay as 660?

$ head /etc/udev/rules.d/50-udev.rules
# There are a number of modifiers that are allowed to be used in some
# of the fields.  See the udev man page for a full description of them.
#
# default is OWNER="root" GROUP="root", MODE="0600"
#

# all block devices
SUBSYSTEM=="block",             GROUP="disk", MODE="0640"
> Thanks,
>
> Marcelo

Thomas