On Dec 1, 2005, at 3:40 PM, Dima Diall wrote:
> On 30/11/05, Craig Hughes <craig@...> wrote:
>> It's very easy to set up from the Mac side -- just add bluetooth
>> device using the wizard thingie, say it's a "any device" device,
>> enter the pin when prompted, and it creates a serial port called /
>> tty.Gumstix which you can then access.
> Somewhat off-topic, but which devices files to be *ideally* used these
> serial connections - '/dev/tty.*' or '/dev/cu.*'? I know thatthe
> former historically was/is for dial-out and the latter for dial-in,
> but does anyone know for sure what's the difference?
This is referring to linux, but a lot of it applies to *BSD too (and
osx). Basically, /dev/cu* are deprecated and you shouldn't use
them. They're there for superbackward compatibility on some
machines, but many have just removed them, and 99.9% of apps out
there have been re-written by now to do the right POSIX stuff:
> 10 - /dev/ttySxx devices are fully POSIX-compliant TTY devices.
If you are
> only going to be using one set of tty devices, you should be
> /dev/cuaXX devices are different from /dev/ttySXX in two ways
> of all, they will allow you to open the device even if CLOCAL
is not set
> and the O_NONBLOCK flag was not given to the open device.
> programs that don't use the POSIX-mondated interface for opening
> /dev/ttySxx devices to be able to use /dev/cuaXX to make
> calls on their modem (cu stands for "callout", and is taken
> The second way in which /dev/cuaXX differs from /dev/ttySXX
is that if
> they are used, they will trigger a simplistic kernel-based
> scheme: If /dev/ttySXX is opened by one or more processes,
> attempt to open /dev/cuaXX will return EAGAIN. If /dev/cuaXX
> by one or more processes, then an attempt to open /dev/ttySXX
> the open blocking until /dev/cuaXX is closed, and the carrier
> goes high.
>> I use either ckermit from fink or ZTerm, depending on my mood.
> I don't see either in fink, but kermit is available through
> darwinports. Is any of these better suited for use with gumstix than
> minicom (the tutorial says we need kermit installed to help minicom do
[craig@...:~]$ locate ckermit.info
works fine for me, despite the "unstable" tag.
> On 30/11/05, Dave Smith <dave@...> wrote:
>> Alternatively, you could use OBEX to push the files to the GS.
> Just another off-topic note: this package's download URL seems
> invalid, I had to manually get it to compile the buildroot from trunk
> (on a GNU/Linux box)