🚀 go-pugleaf

The problem
-----------

We are having problems using GNU 18.55 when run remotely on a SparcStation 1+
that is running Sun OS 4.1.

Background
----------

- the Emacs was built on a SparcStation 1 running Sun OS. 4.0.3
- we recently purchased a SparcStation 1+.  It runs Sun OS 4.1
- we have noticed no problems with the Emacs until we tried it on the 
  SparcStation 1+ OS 4.1
- we have no problems with Emacs if it is run locally on the SparcStartion 1+
- we have no problems with Emacs if we rlogin into the SparcStation 1+.

The scenario
------------

let machine A = sun 3 or 4 or SparcStation 1 running OS 4.0.3
let machine B = SparcStation 1+ running OS 4.1

login to machine a

start the X window system

start emacs on machine b but displaying to machine a's console
using something like 

   xhost b
   rsh b -n "(set path=($path); setenv DISPLAY a:0.0; emacs)"

  where a and b are the names of the machines described above.

emacs starts on machine b and a window is popped up on machine a's console.

do m-x shell in the new emacs

you get the following message

   Process shell stopped (tty input)

and the shell does not work.

Further if you then start a lisp (we use Allegro CL), the lisp starts fine but
if you type ^C^C to it, Emacs beeps and prints quit in the mini-buffer.  The lisp
does not appear to get the ^C^C.


Comments
--------

We have noticed some comments in the OS 4.1 release notes concerning setsid and
controlling terminal assignments that may be related to the problem.  We have
tried some experiments with setsid in shell mode -- the results have been
inconclusive.

We routinely go through the above scenario with any combination of Sun3, Sun4
or SparcStation 1 that is running OS 4.0.3.

 

-bill-

bill@reasoning.com
William A. Brew
Reasoning Systems Inc.