README.SCOTTY 1.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465
  1. This is obsolete ... read README.SCO-TTY-NAMES
  2. This is an updated version of old_notes/README.SCOTTY
  3. which I am *sure* you already read a long time ago, heh heh :)
  4. Last Updated Fri Jun 23 01:57:44 EDT 1995
  5. On SCO, TTY devices must be named in the style of:
  6. /dev/ttyNA
  7. ^^
  8. ||
  9. |`------ uppercase letter for modem control
  10. | lowercase for non-modem control
  11. `--------digit (1-4 usually, but any digit)
  12. tty opened lock file created
  13. -------- ------------------
  14. tty23 LCK..tty23 violates NA
  15. tty0A00 LCK..tty0A00 violates NA
  16. tty0a00 LCK..tty0a00 violates NA
  17. tty1a LCK..tty1a
  18. tty1A LCK..tty1A
  19. tty2q LCK..tty2q
  20. tty2Q LCK..tty2q
  21. tty9a LCK..tty9a
  22. tty9A LCK..tty9A
  23. tty231a LCK..tty231a
  24. tty231A LCK..tty231a
  25. tty%%1a LCK..tty%%1a
  26. tty%%1A LCK..tty%%1a
  27. This is the procedure used for any SCO ECU version.
  28. If you are using FAS or other third-party driver, you may use ecu
  29. with ports not normally named in the /dev/tty#N style in one of two
  30. ways under UNIX and one way under XENIX:
  31. 1. Under XENIX or UNIX, create a link to the port
  32. with a compatible name:
  33. ln /dev/ttyF00 /dev/tty1a
  34. ln /dev/ttyFM00 /dev/tty1A
  35. 2. Under UNIX, add additional lines to the
  36. /etc/conf/node.d file and rebuild the kernel
  37. environment (this is the recommended approach
  38. for UNIX, as documented in FAS 2.08 and 2.09):
  39. fas ttyF00 c 48
  40. fas tty1a c 48
  41. fas ttyF01 c 49
  42. fas tty1b c 49
  43. fas ttyFM00 c 208
  44. fas tty1A c 208
  45. fas ttyFM01 c 209
  46. fas tty1B c 209