![]() |
-----BEGIN PGP SIGNED MESSAGE----- On Mon, 17 Nov 1997, Carsten Hoeger wrote: > On Mon, 17 Nov 1997 Matthias.Apitz@SOFTCON.de wrote: > > > 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? > > > I don't know exactly why, but you can for example read in the PPP-HOWTO: It's a legacy of when some OS'es, such as SunOS, used one device for incoming calls and another for outgoing calls. This unfortunately made using the same lock files rather awkward, and could confuse the hell out of systems like HylaFAX that have a single process (faxgetty) monitoring the line and spinning off getty's, fax process, etc. as necessary. According to Ted T'so at MIT, who maintains the Linux archives, it's being written out of future releases: it's much too difficult and confusing to maintain. Nico Garcia Engineer, CIRL Mass. Eye and Ear Infirmary raoul@cirl.meei.harvard.edu -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNHB87z/+ItycgIJRAQG9PQP8C53EDfoQ6jODON3P2Hl3b/+6j0BpQRL4 7M9d4phZi727TDcjryqR4+hnI0anikqUrcv/nUryA0lhE79lX0GLkifjMy8D7txv FFd2W9NvKDuSDT1wFdQ1gOI6GHUlliZw4cPY4tUdHaNh+jjnBMtiHOu+OTb0oY16 9ySZRAuZ2Pw= =PqHb -----END PGP SIGNATURE-----