Xref: utzoo comp.unix.wizards:18987 comp.unix.questions:17246 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!unisoft!greywolf From: greywolf@unisoft.UUCP (The Grey Wolf) Newsgroups: comp.unix.wizards,comp.unix.questions Subject: Re: csh won't work on Suns... Keywords: Well, read on...it's not that simple Message-ID: <2548@unisoft.UUCP> Date: 27 Oct 89 22:14:40 GMT References: <2543@unisoft.UUCP> Reply-To: greywolf@unisoft.UUCP (The Grey Wolf) Distribution: usa Lines: 55 In article <2543@unisoft.UUCP> I wrote: Lots of stuff pertaining to csh not compiling. I received a letter from one person explaining what was going on, but it was under the assumption that I was using 4.2 sources. Let me clarify some things... - The sources tried were modified AND untouched 4.3 VAXen sources, hacked just a wee bit to work on the pyramid (they had to be). No, this is not a contradiction in terms, I compiled it twice -- once with my additions, once without (just to verify that my additions were not the main prob- lem). I also had to use a generic printf.c as doprnt.c was VAX assem- bler (and therefore machine dependent). - With some porting, normal csh (less filename completion) has been made to work under V3.2 on a 68k chip before. Just not 4.3 sources for obvious reasons - The 4.2 sources I tried to work with a LONG time ago (just when we'd made the move from 4.2 to 4.3) failed miserably, so the patches from the 4.*1* version (yes, we had a 4.1 version of this modified shell, called D-shell, incidentally...(never mind the "distributed shell"...don't bother me with details!)), while they (mostly (with some syntax work)) worked to 4.2, were completely useless to the 4.3 release. So I started from scratch on replacing some of the elements which used to be present... Again, the problem (SunOS ONLY!) It compiles with no errors. When run as a login shell, the first interrupt kills the shell. No savehist, no logout, it just plain dies. When run as a "normal" shell (i.e. what you get when you just type "csh" at your prompt), interrupts are handled fine until you run a command which is NOT a builtin command, after which point if you hit an interrupt the shell dies. [ In favour of redundancy to achieve clarity ] When run as a "fast" shell (i.e. "csh -f") (well, the source comments say "fast shell"), interrupts are handled fine until a file such as .cshrc and .login is sourced, after which point interrupts will kill the shell. IMPORTANT QUESTION: Do SunOS signals require that the handler be re- initialised after each invocation of the signal (is Sun that brain-dead? I would prefer to think not; that's a SVism which (hopefully) has gone away in V4 (haven't tried it yet)...), or did they (smartly) adapt to BSD signals which *remember* what they're supposed to do? D V A Thankx A E N C -- "Insane I may be. I am not stupid." Antryg Windrose