Path: utzoo!attcan!uunet!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: xdm/xterm on ncd X terminals
Message-ID: <8909221225.AA22083@expire.lcs.mit.edu>
Date: 22 Sep 89 12:25:29 GMT
References: <19290@princeton.Princeton.EDU>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 16


    1. xdm isn't up to the job; e.g., cycling power confuses xdm, and
    manual initiation of X clients interferes with the xdm session.

Perhaps you could be a lot more specific about these problems (at least
in a bug report to xbugs)?  Things aren't likely to get fixed unless we
understand how they're broken.

    2. the xterm's swamp the 8650. with ~70 xterm processes, our load
    average shoots to ~25. most users need only a fraction of xterm's
    features; a simpler terminal emulator would be useful.

What exactly is swamping the system?  Not enough CPU cycles, or paging
to death, or what?  Having lots of features in a xterm, whose text
space is shared among all processes, doesn't sound like it should a priori
be a problem.  In what way would a "simpler" client be useful?