pilot-link 0.9.5 Unable to bind to port

2001-12-16 Thread The guy named after an Om Kalthoum song

Quote David A. Desrosiers :


How about using the proper -p port 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

Same point of failure. I'm not asking here because 
I think it's a pilot-link bug. I'm asking because the archives
show others ran into the same problem, there's no mention
of someone finding a fix to the problem, and I thought it
best to throw in some more information, and because
someone might have fixed this.



___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix



Re: pilot-link 0.9.5 Unable to bind to port

2001-12-16 Thread Ben Darnell

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 up GDB, and go step by step, 
 I find that for some reason my machine does not consider 
 /dev/ttyS0 to be a TTY, as tested by isatty().

FWIW I've heard of someone whose serial port switched from /dev/ttyS0 to
/dev/ttyS2 (perhaps caused by a kernel upgrade or something).  This
produced the same not-a-tty behavior.  

-Ben
-- 
Ben Darnell  [EMAIL PROTECTED]
http://thoughtstream.org
Finger [EMAIL PROTECTED] for PGP/GPG key 1024D/1F06E509

___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix



pilot-link 0.9.5 Unable to bind to port

2001-12-15 Thread The guy named after an Om Kalthoum song

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 TTY, as tested by isatty().

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 anyone know why this is so?

Thanks in advance
-- 
Omri Schwarz [EMAIL PROTECTED]
Convince the lion that you are not prey and that you may be dangerous
yourself ---From What to do if you encounter a mountain lion, Orange County
Dept of Harbor, Beaches, and Parks.


___
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix