benson@ksr.UUCP (Benson Margulies) (05/26/88)
We are running X11R2 on Suns. Recently, a couple of us just decided to take the plunge into the korn shell. I remember some postings about why we can't start x up with SHELL of ksh. It tends to print a message about switching to the new tty driver and it tends to hang. Did this indeed get discussed? Does anyone recall the answer? --benson -- Benson I. Margulies Kendall Square Research Corp. harvard!ksr!benson ksr!benson@harvard.harvard.edu
RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler) (05/26/88)
See fix #22, recently made available.
benson@ksr.UUCP (Benson I. Margulies Kendall Square Research Corp.) (05/27/88)
thanks. I got past the problem by reordering some code in ksh to look more like csh. I am curious to see the fix, which I will grab soon. --benson
avr@mtgzz.UUCP (XMRP50000[jcm]-a.v.reed) (06/01/88)
In article <350@ksr.UUCP>, benson@ksr.UUCP (Benson Margulies) writes:
< We are running X11R2 on Suns. Recently, a couple of us just decided
< to take the plunge into the korn shell.
< I remember some postings about why we can't start x up with
< SHELL of ksh. It tends to print a message about switching to the
< new tty driver and it tends to hang. Did this indeed get discussed?
< Does anyone recall the answer?
The problem is in xinit, which does some incredibly stupid
csh-specific stuff. I initialize X with a ksh script, and it runs
just fine with ksh on my SUN 3/60.
Adam Reed (mtgzz!avr)