Actually yes (sorry), I was hoping this would be enough to help him out by
itself (I actually copied the stuff from a LUG meeting my brother did at his
LUG http://www.gtlug.org/meetings.html)  Here is a better set of
instructions.

# Tips on what not to forget:
# 
#     * Find your port by doing a HotSync and then checking 'dmesg'
#       output.
#     * Create the '/dev/pilot' device:
#       serial: ln -s /dev/ttyS# /dev/pilot
#       usb: ln -s /dev/usb/ttyUSB# /dev/pilot
#     * As root, change the permissions on /dev/usb/ttyUSB# device:
#       chown 'user' /dev/usb/ttyUSB#
#       chgrp 'group' /dev/usb/ttyUSB#
#       chmod ug+rw /dev/usb/ttyUSB#
#     * With 'pilot-xfer' and 'J-Pilot' start the HotSync from your PDA
#       before engaging the application's sync features. (/dev/pilot needs
#       to be active).  gpilotd does not need this step to sync with
evolution.

Once again, sorry.  I should have taken a minute to proofread and correct
this before sending it.


-----Original Message-----
From: Jesse Keating [mailto:hosting@;j2solutions.net]
Sent: Wednesday, October 02, 2002 1:35 PM
To: [EMAIL PROTECTED]
Subject: Re: USB Cradle setup (Was: 8.0 Problems - Any ideas?)


On Wed, 2 Oct 2002 13:22:17 -0400
"Carter, Shaun G" <[EMAIL PROTECTED]> wrote:

# 
# Tips on what not to forget:
# 
#     * Create the '/dev/pilot' device:
#       serial: ln -s /dev/ttyS# /dev/pilot
#       usb: ln -s /dev/usb/ttyUSB# /dev/pilot
#     * Find your port by doing a HotSync and then checking 'dmesg'
#     output.* As root, change the permissions on /dev/pilot device:
#       chown 'user' /dev/pilot
#       chgrp 'group' /dev/pilot
#       chmod ug+rw /dev/pilot
# * With 'pilot-xfer' and 'J-Pilot' start the HotSync from your PDA
# before engaging the application's sync features. (/dev/pilot needs
# to be active).

not to nitpik here, but wouldn't you want to find your port BEFORE you
create your symlink?  Also, since you are just using a symlink, you'll
have to change the permissions on the serial/usb device, not the
symlink.  You can't very well create a symlink to /etc/shadow as a
normal user, change the permissions on the symlink, then have access
to edit /etc/shadow now would you?

-- 
Jesse Keating
j2Solutions.net
Mondo DevTeam (www.mondorescue.org)

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=jkeating



-- 
Psyche-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/psyche-list




Reply via email to