rvdp@cs.vu.nl (Ronald van der Pol) (11/15/90)
I created shell layers with 'mkdev shl', started 'shl' and typed 'create foobar'. This crashed the system. Is this another one in the endless SCO bug list? Are panic messages saved in some kind of file???????? (sorry, I seemed logical to me :-) (Compaq systempro/20 MB RAM/SCO UNIX 3.2.1) -- Ronald van der Pol <rvdp@cs.vu.nl>
tim@delluk.uucp (Tim Wright) (11/15/90)
In <8244@star.cs.vu.nl> rvdp@cs.vu.nl (Ronald van der Pol) writes: >I created shell layers with 'mkdev shl', started 'shl' and >typed 'create foobar'. This crashed the system. Is this another >one in the endless SCO bug list? Are panic messages saved in >some kind of file???????? (sorry, I seemed logical to me :-) >(Compaq systempro/20 MB RAM/SCO UNIX 3.2.1) To be fair to SCO, this kind of problem is inherent with Shell Layers. That's not to say they're a bad idea but I never saw a correct (read bug-free) implementation. The layers code from AT&T always had bugs - some major, some minor. It could be argued that other vendors should fix these, but it's always been way down the list of priorities ! I suppose the upshot of this is don't use them :-( tim -- Tim Wright, Dell Computer Corp. (UK) | Email address Dell Computer Corp. (UK), Bracknell | Domain: tim@dell.co.uk Tel: +44-344-860456 | Uucp: ...!ukc!delluk!tim "What's the problem? You've got an IQ of six thousand, haven't you?"
gorpong@ping.uucp (Gordon C. Galligher) (11/18/90)
In article <8244@star.cs.vu.nl> rvdp@cs.vu.nl (Ronald van der Pol) writes: >I created shell layers with 'mkdev shl', started 'shl' and >typed 'create foobar'. This crashed the system. Is this another >one in the endless SCO bug list? Are panic messages saved in >some kind of file???????? (sorry, I seemed logical to me :-) >(Compaq systempro/20 MB RAM/SCO UNIX 3.2.1) I have had the same problem on a 4 MB 80386. I have narrowed it down to 'stty intr'. Search in your .cshrc (or .profile) file for stty intr ... If I remove them from the file, then I get a shell; and if I type: $ stty intr POOF System reboots. If I type 'tty' it tells me 'not a tty.' According to the manual page, shell layers are supposed to act exactly like a TTY. Apparently they do not. I have seen a followup to this mentioning something about "It is not SCO's fault." I beg to disagree. I have used Interactive's 386/ix before, and their shell layers work just fine. SCO's is broken. -- Gordon. -- Gordon C. Galligher 9127 Potter Rd. #2E Des Plaines, IL 60016-4881 ...!uunet!telxon!teleng!ping!gorpong
tim@delluk.uucp (Tim Wright) (11/20/90)
In <1990Nov17.213527.14378@ping.uucp> gorpong@ping.uucp (Gordon C. Galligher) writes: >In article <8244@star.cs.vu.nl> rvdp@cs.vu.nl (Ronald van der Pol) writes: >>I created shell layers with 'mkdev shl', started 'shl' and >>typed 'create foobar'. This crashed the system. Is this another >>one in the endless SCO bug list? Are panic messages saved in >>some kind of file???????? (sorry, I seemed logical to me :-) >>(Compaq systempro/20 MB RAM/SCO UNIX 3.2.1) >I have had the same problem on a 4 MB 80386. I have narrowed it down to >'stty intr'. Search in your .cshrc (or .profile) file for stty intr ... >If I remove them from the file, then I get a shell; and if I type: > $ stty intr > POOF >System reboots. If I type 'tty' it tells me 'not a tty.' According to >the manual page, shell layers are supposed to act exactly like a TTY. >Apparently they do not. >I have seen a followup to this mentioning something about "It is not SCO's >fault." I beg to disagree. I have used Interactive's 386/ix before, and >their shell layers work just fine. SCO's is broken. Yep, it was me. I thought the reference was to the original layers bugs. It appears that SCO "enhanced" these :-) Tim -- Tim Wright, Dell Computer Corp. (UK) | Email address Bracknell, Berkshire, RG12 1RW | Domain: tim@dell.co.uk Tel: +44-344-860456 | Uucp: ...!ukc!delluk!tim "What's the problem? You've got an IQ of six thousand, haven't you?"