Title: | -={ H A C K E R S }=- |
Notice: | Write locked - see NOTED::HACKERS |
Moderator: | DIEHRD::MORRIS |
Created: | Thu Feb 20 1986 |
Last Modified: | Mon Aug 03 1992 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 680 |
Total number of notes: | 5456 |
I wonder if anybody could supply a few hints/tips on how to do the following : Two processes, two terminals: Process A's terminal displays whatever process B's terminal shows, AS IT HAPPENS. The method should preferably be in a way such that process B is unaware of anything happening AND the routine should only work on the consent of the owner of process B. I think this is clear; if user B types 'dir', then presses return, his display will show 'dir' then a dump of his directory contents. At the same time, on user A's screen, the same display will be seen. Any good ideas ? Jamie.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
299.1 | Been done outside DEC | 16513::SYSTEM | Thu Aug 28 1986 21:36 | 12 | |
Hmmm... I've daisychained VT241's using rgb coax... 8^) How would you suggest that Process B grant permission to Process A? I assume that the permission could also be revoked? There are various third party utilities to do this. Scott Hesterman | |||||
299.2 | 1984 | VAXWRK::NORDLINGER | Tue Sep 02 1986 11:59 | 16 | |
One third party program that succeeded in displaying the Type ahead buffer was Control, however it occasionally crashed the system. Later versions may not have that "feature" :^). I am under the impression things changed such that UCB+TT_TYPAHD no longer points to the buffer containing the users immediate input, rather the recall command buffer. You have ahead of you a merry chase to try to find the correct offsets, the easy thing is just to see how TTdriver does it ;^). Incidentally I received a call from a university in NJ that had put hooks into mail "to study how people communicate" and wanted to do the same for phone. This is the type of thing hackers would do well to discourage! John (Willing_to_discuss_further_off_line) |