/dev/pilot does not exist
William M. Quarles
walrus at bellsouth.net
Sat Jul 10 20:51:58 UTC 2004
On a tangent, you can upgrade your operating system on your Palm
cheaply. This is one site that I found:
http://www.expansys.com/product.asp?code=113679
I like PalmOS 4.1 a LOT better than 3.5.
Try searching for this in Google:
Palm OS 4.1 -site:palm.com -site:palmone.com -site:palmos.com
-site:palmsource.com
/dev/pilot is not supposed to exist. It does not exist on anyone's
system out of the box. It depends on your individual device and
connection setup, so you are supposed to make it yourself. Making a
symbolic link named /dev/pilot to whatever serial device your Palm is or
connects to on your computer is enough. If your Palm connects to your
first serial port, you do this:
ln -s /dev/ttyS0 /dev/pilot
You might need to change the ownership of that serial port so that you
can have access to it.
Alternatively, you can often change the configuration of the program
that you are using to use the serial device directly rather than /dev/pilot.
fedora wrote:
> Situation-
> /dev/pilot does not exist
>
> What I am trying to do-
> sync palm Vx with Evolution1.4 on fc2
>
> Spec
> Palm Vx OS_3.5 after hard reset
> Serial cradle connected
> Evolution 1.4 never been synced before
>
> What I have tried...after Googling and fedora archive-
>
> 1_ originally I thought it was permissions
> [root at blue root]# chmod 0666 /dev/pilot
> chmod: cannot access `/dev/pilot': No such file or directory
>
> and
>
> [root at blue root]# pilot-xfer -p /dev/pilot -l
>
> The device /dev/pilot does not exist..
> Possible solution:
>
> mknod /dev/pilot c <major> <minor>
>
> Unable to bind to port: /dev/pilot
> Please use --help for more information
>
>
> 2_Well, I know ttyS0 and ttyS1 do exist...
>
> [root at blue root]# setserial -g /dev/ttyS[0-4]
> /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
> /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
> /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
> /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
> /dev/ttyS4, UART: unknown, Port: 0x0000, IRQ: 0
>
> ?Advice please..
> Should I make a soft link between ttyS0 and /dev/pilot...?
>
> or something with mknod? I did a man mknod, but do not understand what
> should be done.
>
> tia
> chris
>
More information about the fedora-list
mailing list