README.SCOTTY 1.7 KB

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