Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!rutgers!mailrus!cs.utexas.edu!samsung!aplcen!haven!udel!mmdf
From: postmaster@att-in.att.com
Newsgroups: comp.os.minix
Subject: (none)
Message-ID: <8381@nigel.udel.EDU>
Date: 16 Jan 90 17:09:46 GMT
Sender: mmdf@udel.EDU
Lines: 42

Mail to `att.att.com!attmail!mhs!envoy!ics.test/pn=_test_group' alias `att!attmail!mhs!envoy!ics.test/pn=_test_group' from 'VM1.NoDak.EDU!INFO-MINIX%UDEL.EDU' failed.
The error message was:
destination unknown or forwarding disallowed
The message began:
Received: from NDSUVM1.BITNET by VM1.NoDak.EDU (IBM VM SMTP R1.2.1MX) with BSMTP id 4885; Tue, 16 Jan 90 01:55:00 CST
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.03B) with BSMTP id
 4872; Tue, 16 Jan 90 01:54:58 CST
Date:         Tue, 16 Jan 90 05:03:29 GMT
Reply-To:     INFO-MINIX%UDEL.EDU@VM1.NoDak.EDU
Sender:       Minix operating system <MINIX-L@VM1.NoDak.EDU>
Comments:     Warning -- original Sender: tag was info-minix-request@UDEL.EDU
From:         "B.C." <bc%UX1.CSO.UIUC.EDU@VM1.NoDak.EDU>
Subject:      /dev/tty2 panic with "term"
Comments: To: info-minix@udel.edu
To:           Multiple recipients of list MINIX-L <MINIX-L@NDSUVM1>

I have been completely unsuccessful in using the programs "term", "zterm", and
"kermit" with /dev/tty2.  (Read: any program with /dev/tty2.)

Whenever I run any of these under a standard AT 1.3 kernel, a bunch of garbage
shows up on the screen and the system hangs (real hang, not ^F9 hang).  Under
Evans' protected-mode kernel I get a general protection fault (9) panic,
followed by an immediate automatic reboot (I don't even have time to read the
error message -- the code seems to indicate that I should have to press a key
to reboot).

I have changed the NR_RS_LINES constant to 2 in the file kernel/tty.h, thinking
that that would help, but it did not.  I checked the constants relating to the
interrupt and port assignments, and they all seem to be OK.  The programs work
OK with /dev/tty1, though, except for the fact that this is a mouse.  :-)

I guess a workaround would be to swap the mouse and the modem, but since my
port sizes are happiest (no adapters) the way they are, I'd rather find a real
solution (not to mention I'd like to know what's going on).

If anyone has a clue for me, I'd love to hear from you.  If I get a deluge of
new and unposted patches, I'll post the first one that works.

Thanks,

Ben Cox
b-cox2@uiuc.edu