Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!ogicse!milton!etb
From: etb@milton.u.washington.edu (Eric Bushnell)
Newsgroups: comp.sys.apollo
Subject: problem w/BSD keys and environment
Keywords: madness
Message-ID: <1991Apr18.183923.15770@milton.u.washington.edu>
Date: 18 Apr 91 18:39:23 GMT
Sender: etb@milton.u.washington.edu (Eric Bushnell)
Organization: University of Washington, Seattle
Lines: 30

A few weeks ago, I updated a dozen DN35/4500s
in a student lab to sr10.3. I set them up with
the Aegis/BSD combination, and set all the
hosts' /sys/node_data/etc/environ files with
ENVIRONMENT = bsd
SYSTYPE = bsd4.3

Then all of them should use ^C for the process
interrupt signal and ^D for EOF. And so they
did -- for a while.

Last week I noticed one node had regressed to ^Q and ^Z
instead,  and since then they've all done it!

Both stty and tctl indicate that ^C and ^D are
supposed to be the keys for those signals. The
environ files haven't changed. I wasn't using
a $(HOME)/.environ file, but when I tried it,
it didn't help anyway.

The 10.3 node on my desk, which is on a different
network, hasn't suffered this malady.

What is this???


-- 
Eric Bushnell
Univ of Washington Civil Engineering
etb@u.washington.edu