STEINBERGER@SRI-KL.ARPA (Richard Steinberger) (10/24/86)
Thanks to all who sent responses to my query on using the debugger on
a different terminal than the one that the 'screen mode' program is running
on. For those who asked, and others who are interested, here is the
summary of what to do. Assume you want the Debug I/O to occur on
terminal txa6: (and of course you are using a different one).
$ ALLOCATE txa6:
$ assign txa6: dbg$input
$ assign txa6: dbg$output
.
.
run your program
.
.
$ deallocate txa6:
I did this from the sys$manager account. Some privelege is needed to do
the allocate command.
-Ric Steinberger
Steinberger@sri-kl
-------STEINBERGER@SRI-KL.ARPA (Richard Steinberger) (10/27/86)
Stephan, Thanks for the suggestion. -Ric Steinberger -------
dp@JASPER.Palladian.COM (Jeffrey Del Papa) (10/28/86)
Date: Mon, 27 Oct 86 09:31:21 -0100
From: "Stephan Wasserroth" <unido!vax.hmi.dfn!wasserroth@seismo.CSS.GOV>
Just a comment to the ALLOCATE-command:
If You add the following line in Your SYSTARTUP.COM for all terminal
lines, then everybody may allocate currently unused terminals:
$ SET PROTECTION=W:RWLP/DEVICE TXnn:
ARPA: <unido!vax.hmi.dfn!wasserroth@seismo.css.gov>
EARN/BITNET: <wasserroth%vax.hmi.dfn@gmdzi.uucp>
DFN: <wasserroth@vax.hmi.dfn>
Stephan Wasserroth - VAX System Manager
Hahn-Meitner-Institut, Berlin, Fed. Rep. of Germany
of course this defeats most of the trojan horse protection
laboriously added to the device system .. now anyone can write their
onw loginout lookalike. (yes I have run (and advocate running) a system this
wide open, but only in the case where their is no out of the building
acces to the system, and the user base is small and responsible enough
for peer pressure to work as a control/security mechanisim. (the system
didn't use passwords, all users were fully priv'd, and the only data
loss in 3 years was due to operator error with standalone backup))
<dp>