home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / sys / att / 1905 < prev    next >
Encoding:
Internet Message Format  |  1992-07-27  |  1.2 KB
  1. Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!mips!swrinde!cs.utexas.edu!rutgers!princeton!mccc!pjh
  2. From: pjh@mccc.edu (Pete Holsberg)
  3. Newsgroups: comp.sys.att
  4. Subject: Re: Virtual Terminal SV/386 R3.2.2
  5. Message-ID: <1992Jul27.141439.13309@mccc.edu>
  6. Date: 27 Jul 92 14:14:39 GMT
  7. References: <1992Jul26.022754.6090@mccc.edu> <tr.712204038@samadams>
  8. Organization: The College On The Other Side Of Route One
  9. Lines: 19
  10.  
  11. In article <tr.712204038@samadams> tr@samadams.princeton.edu (Tom Reingold) writes:
  12. =pjh@mccc.edu (P. J. Holsberg) writes:
  13. =
  14. =$ /etc/inittab starts /etc/vtgetty console console.
  15. =
  16. =$ Is it possible to run /etc/vtgetty for any other port? If so, how? I
  17. =$ looked at TFM but ...
  18. =
  19. =What sort of port were you hoping to run virtual terminals from?  I am
  20. =fairly certain that they use a device driver that directly read the
  21. =keyboard and write to the video buffer.  This would not work over a tty
  22. =port.  If you want that sort of thing, run "screen" which has some
  23. =features over vtlmgr anyway.
  24.  
  25. Modem port.
  26.  
  27. I thought that screen required facilities not present in AT&T SV/386
  28. R3.2.2 UNIX (sockets? pttys? ??). Is that not so? Does screen recognize
  29. "hot keys"?
  30.