Xref: utzoo comp.windows.x:28930 comp.sys.pyramid:952
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cis.ohio-state.edu!karl_kleinpaste
From: karl_kleinpaste@cis.ohio-state.edu
Newsgroups: comp.windows.x,comp.sys.pyramid
Subject: Re: Xterm su problems on Pyramid
Message-ID: <KARL.90Oct31100857@giza.cis.ohio-state.edu>
Date: 31 Oct 90 15:08:57 GMT
References: <556@telxon.UUCP>
Sender: news@tut.cis.ohio-state.edu
Followup-To: comp.windows.x
Distribution: na
Organization: Ohio State Computer Science
Lines: 57

matth@telxon.uucp writes:
   Has anyone tried compiling and running the X11 R4 xterm on a Pyramid 9820?
   I compiled it straight from the MIT tape and everything seems to be fine
   when running it with one exception.
   Whenever I try to run "su" or "passwd" it seems to shoot out extraneous
   CR's.  For example,
   % passwd matth
   Old password: < at this point xterm sends(?) CR before user gets a chance to
		   type
   Sorry.
   It seems that when these programs turn off echo, things get confused
   and a CR is sent.

The actual problem is a Pyr-specific glitch where /dev/tty is not
being attached to your xterm properly.  This has been discussed here
at least a half dozen times in the last couple of years.  Make the
change indicated below to your xterm sources, recompile, and you'll
have a functional /dev/tty in xterm again.

--karl
    ________________

From: gprieur@pyramid.pyramid.com (Gordon Prieur)
Newsgroups: comp.sys.pyramid
Subject: Re: Problem porting X11R4 clients to OSx5.0
Date: 9 Aug 90 14:59:53 GMT

In article <BOB.90Aug7091403@volitans.MorningStar.Com> bob@MorningStar.Com (BobS
utterfield) writes:
>>>   Just for the record, I've compiled and run the X11R4 xterm with no
>>>   problems (and no major code changes).
>>>
>>Can you say "cat < /dev/tty" and have it wait 'till you type
>>something?  What non-"major code changes" were required?

Yes, I can say "cat < /dev/tty" and have it wait till I type. The only change
to xterm in this version was in main.c, where the line

        close(open(ttydev, O_WRONLY, 0));

was changed to
        close(open(ttydev, O_RDWR, 0));

The reason for this eludes me, and I'm not in a position to recompile the
source without the fix, but it seems unlikely that its going to change the
behavior you see. I remember the original article posting the problem stated
they were running OSx 4.4. I've tested this xterm with both 5.0 and 5.1. I
suggest your problem is from an old version of OSx. If you are running a
version 5 and still see the problems, you should report it as a bug (by
sending mail to bugs@pyramid.com).

                 Gordon Prieur
      -m-------  Pyramid Technology Corporation
    ---mmm-----  1295 Charleston Rd, P.O. Box 7295
  -----mmmmm---  Mt. View, CA 94039-7295  (415) 335-8533
-------mmmmmmm-  {decwrl,hplabs,sun,uunet}!pyramid!pyrps5!gprieur
    ________________