On Sun, Dec 16, 2001 at 02:07:23AM -0500, The guy named after an Om Kalthoum song
wrote:
> Hi, I'm trying to figure out why I get this problem:
>
> [omri@percy-hobbs omri]$ pilot-xfer /dev/ttyS0 -b ~/Pilot
>
>Unable to bind to port /dev/ttyS0
>pi_bind: Invalid argument
>
> When I fire
Quote David A. Desrosiers :
>How about using the proper -p argument, as specified by
>pilot-xfer -h, as in:
>pilot-xfer -p /dev/ttyS0 -b ~/Pilot
[omri@percy-hobbs omri]$ pilot-xfer -p /dev/ttyS0 -b ~/Pilot
Unable to bind to port /dev/ttyS0
pi_bind: Invalid argument
Sa
On Sat, 2001-12-15 at 23:07, The guy named after an Om Kalthoum song
wrote:
> This is using RH 7.1, and did not happen with
> previous Redhats as far as I recall.
>
> The same problem happened with pilot-link 0.9.3,
> (pa_bind: Invalid argument.)
>
> Has anyone else run into this?
> Does anyon
Hi, I'm trying to figure out why I get this problem:
[omri@percy-hobbs omri]$ pilot-xfer /dev/ttyS0 -b ~/Pilot
Unable to bind to port /dev/ttyS0
pi_bind: Invalid argument
When I fire up GDB, and go step by step,
I find that for some reason my machine does not consider
/dev/ttyS0 to be a
