Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: Need help on Linux
What I know about the subject is that ttySx are the input devices and
cuax are the output devices, hence for years people have adopted the
trick of using cuax when doing input output, like in hylafax. I've
seen ttySx used mostly when you are going to leave a listening
program connected to the port only, like in uugetty.
I've also seen an email in this list where they mention that the
split input output tirck stinks and that the MIT guys are going to
discontinue it in the next release of LInux.
I've been using cuax for some time with no problem, but....
I hope this helps,
Julio
> Reply-to: Matthias.Apitz@SOFTCON.de (Matthias Apitz)
> Carsten Hoeger wrote:
>
> On Sat, 15 Nov 1997, Julio C Spinelli wrote:
>
> [...]
>
> > Then either start the faxgetty cuax (x=0,1,2,3 etc.) by hand or add
> > it to your init file.
>
> By the way: Don't use one of the /dev/cuax devices. Use /dev/ttySx
> instead...
>
> Could you please explain in detail the difference between
> the two devices (as far I can see they have at least different
> major number and perhaps different kernel drivers):
>
> $ ls -l /dev/ttyS1 /dev/cua1
> crw-rw-rw- 1 root uucp 5, 65 Jul 18 1994 /dev/cua1
> crw-rw-rw- 1 root tty 4, 65 Jul 18 1994 /dev/ttyS1
>
> Why /dev/cuax exists _and_ should not be used?
>
> matthias
>
> --
> firm: matthias.apitz@sisis.de [voc:+49-89-61308-351, fax: +49-89-61308-188]
> priv: guru@thias.muc.de
> PGP: Key fingerprint = 0C 01 F2 23 EC 17 A2 D5 46 2D 29 4C 0E 8B 7E 8F
>
> from USENET:
> People who run servers understand that flashy interactive interfaces have
> nothing to do with the underlying functionality and often get in the way.
>
>