sean@ms.uky.edu (Sean Casey) (10/25/88)
This is really for Matt Dillon, but I don't have his email address.
When using environment variables from "shell" or when I just start up
"dterm", I get a requestor for drive ENV:. I understand this is
probably a request to an installed ENV device, but I've never heard of
it except for a brief reference in the shell docs.
Is this supposed to be happening? I have dres.library in libs:, and its
the latest off ucbvax. The requestor really throws a wrench in the
works for totally automated logins with dterm. I'd like to know how to
get rid of it. If I can't, I'll have to stick with "vt100" for a term
program, but I'd much rather use a state machine like the one in dterm.
Thanks,
Sean
--
*** Sean Casey sean@ms.uky.edu, sean@ukma.bitnet
*** The Hacker from Spaaaaaaaaace. {backbone|rutgers|uunet}!ukma!sean
*** U of K, Lexington Kentucky, USA ..where Christian movies are censored.
*** ``The World... she's a flat! She's a round! Flat! Round! Flat! Round!''dillon@CORY.BERKELEY.EDU (Matt Dillon) (10/26/88)
Sean Casey sean@ms.uky.edu Writes:
:"dterm", I get a requestor for drive ENV:. I understand this is
:probably a request to an installed ENV device, but I've never heard of
:...
:the latest off ucbvax. The requestor really throws a wrench in the
:works for totally automated logins with dterm. I'd like to know how to
:get rid of it. If I can't, I'll have to stick with "vt100" for a term
:program, but I'd much rather use a state machine like the one in dterm.
ENV: = 1.3 enviroment variables. If you don't use them yet, just
assign ENV: somewhere (like RAM:). My latest shell automatically searches
ENV: if it can't find the variable locally, plus adds new commands to
support the enviroment.
-Matt