From RWKatSCRC-TENEX Sat May 29 00:00:00 1982 From: RWKatSCRC-TENEX (Robert W. Kerns) Date: Saturday, 29 May 1982, 00:00 Subject: WHARTON In-Reply-To: The message of 29 May 82 17:29-EDT from GSB at MIT-ML Message-ID: From: GSB at MIT-ML Date: 05/29/82 17:29:23 GSB at MIT-ML 05/29/82 17:29:23 Is wharton no longer on the arpanet, or is the host table trashed? It's in the arpanet-bboards list, but it took me a bit to track this down because comsat issued no diagnostic for a "TO:(BBOARD WHARTON)", just sent it to bboard locally (which is a dumb thing to do). Wharton is off the arpanet due to administrative fuckup of some sort or another. They'll be back someday (at different address) when it all gets straightened out. From DCP at MIT-MC Sat May 29 00:00:00 1982 From: DCP at MIT-MC (DCP at MIT-MC) Date: 29 May 1982 00:00 Subject: No subject Message-ID: :host WHARTON Lookup failed. So, it is not in the host table on MC. CAH tells me that WHARTON punted the ARPAnet, or the other way around. Politics, or something like that. From GSB at MIT-ML Sat May 29 00:00:00 1982 From: GSB at MIT-ML (GSB at MIT-ML) Date: 29 May 1982 00:00 Subject: No subject Message-ID: Is wharton no longer on the arpanet, or is the host table trashed? It's in the arpanet-bboards list, but it took me a bit to track this down because comsat issued no diagnostic for a "TO:(BBOARD WHARTON)", just sent it to bboard locally (which is a dumb thing to do). From FONERatMIT-AI Sat May 29 00:00:00 1982 From: FONERatMIT-AI (Leonard N. Foner) Date: 29 May 1982, 00:00 Subject: No subject Message-ID: Something appears wrong with the way certain host names are being displayed by FINGER. While most of the lines printed out are fine, FINGER is consistently showing these lines wrong: FONER T Leonard N. Foner F T43 #27: At home GYRO A Scott W. Layson HACTRN 7.T44 Net site (Chaos) As you can see, the hostnames (in my case, MIT-TIP... I don't know about Scott) are not being displayed. I dunno what's wrong. Ciao. From MoonatSCRC-TENEX Thu May 27 00:00:00 1982 From: MoonatSCRC-TENEX (David A. Moon) Date: Thursday, 27 May 1982, 00:00 Subject: 2-character escape sequences getting broken up Message-ID: DDT could avoid this by doing its interrupt-level typeout (e.g. of sends) on a separate I/O channel. From RWKatSCRC-TENEX Thu May 27 00:00:00 1982 From: RWKatSCRC-TENEX (Robert W. Kerns) Date: Thursday, 27 May 1982, 00:00 Subject: Illegal chr after control P In-Reply-To: The message of 27 May 82 01:18-EDT from Michael Travers Message-ID: Date: 27 May 1982 01:18-EDT From: Michael Travers I was SUPDUPing to AI from XX. While reading my mail with $^A I typed a space to a --More-- break. It spat out: TTY: MT; - ILLEGAL CHR AFTER CNTRL P ON TTY DISPLAY I can't reproduce this as nothing at all out of the ordinary was being done. I did notice that there was new mail in my mail file that I had not seen a notification for; perhaps it was trying to print it when it got the error. This is the usual screw with two-character escape sequences getting asynchronous typeout intervening between them. From MTatMIT-AI Thu May 27 00:00:00 1982 From: MTatMIT-AI (Michael Travers) Date: 27 May 1982, 00:00 Subject: No subject Message-ID: I was SUPDUPing to AI from XX. While reading my mail with $^A I typed a space to a --More-- break. It spat out: TTY: MT; - ILLEGAL CHR AFTER CNTRL P ON TTY DISPLAY I can't reproduce this as nothing at all out of the ordinary was being done. I did notice that there was new mail in my mail file that I had not seen a notification for; perhaps it was trying to print it when it got the error. From CSTACY at MIT-MC Sat May 22 00:00:00 1982 From: CSTACY at MIT-MC (CSTACY at MIT-MC) Date: 22 May 1982 00:00 Subject: hung TVs Message-ID: On AI, sometimes when you get a TV by hitting call, you get wedged in TTYI. It looks like the person get blocked at TYI1+20. I dont know anything about that part of the system yet. From JNCatMIT-XX Wed May 19 00:00:00 1982 From: JNCatMIT-XX (J. Noel Chiappa) Date: 19 May 1982, 00:00 Subject: No subject Message-ID: I doubt that ITS will ever implement InterNet, and I see no signs of them implementing SMTP. In the meantime, you can get mail from ITS to InterNet sites by sending mail to "person%final_host"@forwarder_host; I am told that the ISI sites provide such a forwarding arrangement; others, closer to MIT, should be appearing shortly. ------- From DCPatMIT-MC Tue May 18 00:00:00 1982 From: DCPatMIT-MC (David C. Plummer) Date: 18 May 1982, 00:00 Subject: No subject Message-ID: I don't know if anybody else has checked recently, but all four SYS directories are at least 95% full. Should we try to clear some out, or go to SYS4; (gack). From DCP at MIT-MC Mon May 17 00:00:00 1982 From: DCP at MIT-MC (DCP at MIT-MC) Date: 17 May 1982 00:00 Subject: No subject Message-ID: I replied to GJC (it was a user's (perhaps not his own) .MASK variable). From GJC at MIT-MC Mon May 17 00:00:00 1982 From: GJC at MIT-MC (GJC at MIT-MC) Date: 17 May 1982 00:00 Subject: No subject Message-ID: Saw a funny thing on the system consol today: 223616/ 204202,,321560 204202,721560 STEVER 02:10:17 anybody know what that location might be? From MOONatMIT-MC Sat May 15 00:00:00 1982 From: MOONatMIT-MC (David A. Moon) Date: 15 May 1982, 00:00 Subject: MC mem D Message-ID: The problem with memory D is massive trauma to its electrical outlet under the floor, and its plug. The plastic is melted and somewhat burned. I left the floor pulled up and the plug unplugged so you can see it. I don't know whether this is due to a fault of mem D itself, however I saw no evidence of burned wiring inside its power control. Neither the circuit breaker on mem D nor the one on the wall is blown. This will need the attention of some sort of electrician. By the way, could you ask whoever is in charge not to block off maintenance access to the MC machine? I shoved the offending desk out into the main passageway where it will cause a massacre if there is a fire--hopefully this will ensure that it gets moved to someplace reasonable soon (not shoved back in front of the machine where it blocks off the memory doors). From GUMBYatMIT-AI Wed May 12 00:00:00 1982 From: GUMBYatMIT-AI (David Vinayak Wallace) Date: 12 May 1982, 00:00 Subject: No subject Message-ID: :f ken PARERR; 14603>>TDNN 4,(5) 4/ 1 50000/ TLZN 14,45602 From MARTYatMIT-AI Tue May 11 00:00:00 1982 From: MARTYatMIT-AI (Martin David Connor) Date: 11 May 1982, 00:00 Subject: GFR25 Message-ID: Whoever did GFR 25 seems to have reaped the wrong files. Since some twit opened all the files on the system on 2 April, reference date was no good for reaping on. The XGP login init was reaped, along with a couple other files. Whoever did it, please fix it. Thanks. Marty From SWGatMIT-XX Fri May 7 00:00:00 1982 From: SWGatMIT-XX (S. W. Galley) Date: 7 May 1982, 00:00 Subject: strange ITS crash Message-ID: I just now reloaded DM ITS after it was hung in user mode, but with the parity-stop and run lights on. I dumped it to DM:CRASH;COMSYS >, because the light for job #5 (COMSYS COMSYS) was lit. PC/ 725717, parity buffer/ 0, pager mem addr/ 1,,337717 (in ARM-10), parity error light off! ------- From PGSatMIT-AI Thu May 6 00:00:00 1982 From: PGSatMIT-AI (Patrick G. Sobalvarro) Date: 6 May 1982, 00:00 Subject: No subject Message-ID: I answered NEVES's question. From NEVES at MIT-MC Wed May 5 00:00:00 1982 From: NEVES at MIT-MC (NEVES at MIT-MC) Date: 05 May 1982 00:00 Subject: No subject Message-ID: SIGH... HOW DOES ONE GET A FILE FROM A CHAOSNET SITE SUCH AS SPEECH TO MIT-MC WHILE ON THE MIT-MC END? THE CFTP PROGRAM ON ITS DOESN'T SEEM TO BE THE APPROPRIATE THING TO USE BECAUSE IT DOESN'T ALLOW ONE TO LOGIN TO THE OTHER MACHINE. -DAVE From CSTACYatMIT-AI Tue May 4 00:00:00 1982 From: CSTACYatMIT-AI (Christopher C. Stacy) Date: 4 May 1982, 00:00 Subject: weird! Message-ID: In COMSAT 380, ITS 1273, on MIT-AI: COMSAT was not properly delivering mail to GUMBY. The stats log says the mail was delivered, and he got CLI messages saying it had been. But the mail seems to have gone into a black hole. I temporarily changed his netaddress to MC; receiving mail on another host seems to work fine. I wonder how many other people have been losing mail, and how this could be happenning? From MOON at MIT-MC Sun May 2 00:00:00 1982 From: MOON at MIT-MC (MOON at MIT-MC) Date: 02 May 1982 00:00 Subject: JOB: device Message-ID: It might be that the bootstrap loader for the job has to fit in the AC's and doesn't have enough locations left to signal an error -- maybe it does a .LOGOUT thinking that will make ITS signal an error for it, but someone broke ITS to reload the job instead? Just a theory.