> I'm interested in responding to a suggestion from a list member here
> sent to me privately. That suggestion is to test the CoLinux support
> for Braille terminals and displays--which is something I could possibly
> accomplish with the new serial daemon in 0.7.1.
> ArchLinux doesn't seem to have /dev/ttys0 or any ttys devices, but
> rather ttyS--which it claims to be for serial terminals. Should I
> manually mknod the former, or is there an easier way to get them?
What is the different between your ArchLinux and the image file
ArchLinux-0.7.2-ext3-512mb.7z from sourceforge.net?
I have ArchLinux downloaded from sourceforge.net, and there exist
/dev/ttyS0, it's a link to /dev/tts/0 and should work.
[root@... ~]# ls -l /dev/ttyS*
lrwxrwxrwx 1 root root 5 Jul 26 05:39 /dev/ttyS0 -> tts/0
[root@... ~]# ls -l /dev/tts/0
crw-rw---- 1 root tty 4, 64 Jul 22 2006 /dev/tts/0
The device exist after boot. Have not tested it. Have no serial port
and no USB adapter here in this time.
For CoLinux add these or similars parameters to your configuration:
ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"
The full command reference is in this file (starts with "ttysX"):
Mostly of arguments are still forwarded to the Windows command "MODE".
Inside CoLinux you should than use /dev/ttyS0.
Remember: The Windows config needs ttys0 and inside Linux it's ttyS0,
the difference is the lower and upper letter.
Have you a Braille Terminal and is working under Windows? My sample
"COM1" should replace with your Windows device name. For
USB-Serial-Adapters you can also use the Windows internaly name that
beginning with backslashes, for sample "\\.\COM1"