BABYL OPTIONS: Owner: SCHREQ Append: 0 Mail: DSK: SCHEME; SCHREQ MAIL Version:5 Expiration-Check-Time:04/03/88 11:09:59  1,, Date: Sun, 3 Apr 88 11:05:51 EDT From: Jonathan A Rees Subject: [Ralph.Hyre: T discussion and newsgroups] To: SCHREQ@AI.AI.MIT.EDU Message-ID: <352309.880403.JAR@AI.AI.MIT.EDU> *** EOOH *** Date: Thu, 31 Mar 1988 19:36-EDT From: Ralph.Hyre at IUS3.IUS.CS.CMU.EDU To: JAR at ai.ai.mit.edu Re: T discussion and newsgroups The 'backbone cabal' has replaced berkeley as far as administrivia. Changing comp.lang.scheme to a 'moderated' group would force posts to be mailed to info-scheme, in order to help keep things together on both sides. Mention this to backbone@cbosgd.att.com As for T, if there are more than 100 people on the T-Discussion mailing list, then it should be easy to authorize creation of a comp.lang.scheme.t list. Thanks for the info! -- - Ralph W. Hyre, Jr. Internet: ralphw@ius2.cs.cmu.edu Phone:(412)268-{2847,3275} CMU-{BUGS,DARK} Amateur Packet Radio: N3FGW@W2XO, or c/o W3VC, CMU Radio Club, Pittsburgh, PA  1, unseen,, Date: Sun, 3 Apr 88 11:04:56 EDT From: Jonathan A Rees Subject: scheme-request To: jinx@ZURICH.AI.MIT.EDU cc: SCHREQ@AI.AI.MIT.EDU In-reply-to: Msg of Sat 2 Apr 88 08:16:08 est from jinx at CHAMARTIN.AI.MIT.EDU (Guillermo J. Rozas) Message-ID: <352308.880403.JAR@AI.AI.MIT.EDU> *** EOOH *** Date: Sun, 3 Apr 88 11:04:56 EDT From: Jonathan A Rees To: jinx at ZURICH.AI.MIT.EDU cc: SCHREQ at AI.AI.MIT.EDU Re: scheme-request OK, here are some instructions: The list is in the file MC: JAR; SCHEME LIST. The format should be pretty obvious. For now I'm still removing people by commenting out their line. And except for large redistribution lists, I remove people after only a couple of bounced messages, and put in an annotation saying what happened, with the date. Also, I acknowledge all addition and deletion requests. For additions, the acknowledgement acts as a test of the address. I include the file AI: JAR; POLICY > in acknowledgements. I route Internet addresses not in AI's host table via XX. (:HOST will say whether or not it's there.) I don't add BITNET addresses, I just send the file AI: JAR; BITNET >. Often I have to look at Received: lines (0H in BABYL) to figure out how to route mail. I have just created an ITS account called SCHREQ. Scheme-Request@MC simply forwards to SCHREQ@AI. I handle requests by logging in as SCHREQ and running BABYL. This way if someone replies to acknowledgements, the reply goes to SCHREQ and not to me personally. SCHREQ's home directory is AI: SCHEME;, so the requests pile up in AI: SCHEME; SCHREQ MAIL. You may deal with requests either by logging in on AI as SCHREQ, or by changing MC: .MAIL.; NAMES > to forward Scheme-Request mail to some destination of your choice. Oh yeah, requests for T-Discussion also go to the same place. You can either leave those for me to deal with when I get back, or handle them by editing MC: JAR; T-DISC LIST. Thanks much.  1,, Date: Fri, 1 Apr 88 11:47:57 EST From: Jonathan A Rees Subject: [princeton!A ‡: Returned mail: User unknown] To: SCHREQ@AI.AI.MIT.EDU Message-ID: <351584.880401.JAR@AI.AI.MIT.EDU> *** EOOH *** Date: Thu, 31 Mar 88 11:32:49 EST From: princeton!A‡@rutgers.edu at rutgers.edu To: JAR at ai.ai.mit.edu Re: Returned mail: User unknown ----- Transcript of session follows ----- 550 csaba... User unknown ----- Unsent message follows ----- Received: by Princeton.EDU (5.58+/1.58) id AA13599; Mon, 28 Mar 88 11:22:56 EST Received: by rutgers.edu (5.54/1.15) with UUCP id AA00922; Mon, 28 Mar 88 11:11:10 EST Received: from MC.LCS.MIT.EDU by seismo.CSS.GOV (5.54/1.14) id AA15169; Mon, 28 Mar 88 11:01:14 EST Received: from MC.LCS.MIT.EDU by OZ.AI.MIT.EDU with Chaos/SMTP; Mon 28 Mar 88 10:58:33-EST Received: from AI.AI.MIT.EDU (CHAOS 3130) by MC.LCS.MIT.EDU 28 Mar 88 10:23:41 EST Date: Mon, 28 Mar 88 10:24:22 EST From: Jonathan A Rees Subject: T discussion and newsgroups To: uunet.uu.net!mcvax!ukc!reading!onion!minster!SoftEng!martin Cc: mc.lcs.mit.edu!scheme In-Reply-To: Msg of 19 Mar 88 22:38:32 GMT from mcvax!ukc!reading!onion!minster!SoftEng!martin at uunet.uu.net Message-Id: <348649.880328.JAR@AI.AI.MIT.EDU> Discussion pertaining T can be carried out on the T-Discussion mailing list. Send mail to t-discussion-request@MC.LCS.MIT.EDU to be added. Similarly for C Scheme; info-cscheme-request%OZ@MC.LCS.MIT.EDU. ... unless you do not have access to the Internet, as I understand many Usenet people do not. In that case, please carry on the conversation here (or on comp.lang.scheme), as there is no "comp.lang.t" newsgroup to my knowledge. Or lobby Berkeley to create one. The same goes for C Scheme (I have repeatedly requested that they create a C Scheme newsgroup, but they say they are too busy). And speaking of comp.lang.scheme: please correct me if I'm wrong, but it's my understanding that messages sent to the Scheme mailing list on the Internet are forwarded to comp.lang.scheme on Usenet, but not vice versa. It's possible that there is interesting discussion happening on comp.lang.scheme that us Internet users are missing out on, but I wouldn't know. I hear rumors that there exist mailing lists for which there is mutual forwading between Internet and Usenet (without infinite loops), but I don't know how to set one up. If anyone would like to volunteer to do so, please speak up by sending a message to me at scheme-request@mc.lcs.mit.edu. - humble moderator.  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 30 Mar 88 05:17:01 EST Received: from RELAY.CS.NET (TCP 1201000005) by MC.LCS.MIT.EDU 30 Mar 88 05:15:24 EST Received: from relay2.cs.net by RELAY.CS.NET id ab12524; 30 Mar 88 4:53 EST Received: from tektronix.tek.com by RELAY.CS.NET id ab06443; 30 Mar 88 4:41 EST Received: by tektronix.TEK.COM (5.51/6.24) id AA01719; Tue, 29 Mar 88 18:15:54 PST Received: by tekig5.PEN.TEK.COM (5.52/6.24) id AA17130; Tue, 29 Mar 88 18:11:16 PST Message-Id: <8803300211.AA17130@tekig5.PEN.TEK.COM> To: t-discussion-request@mc.lcs.mit.edu Date: 29 Mar 88 18:11:13 PST (Tue) From: tims%tekig5.pen.tek.com@RELAY.CS.NET *** EOOH *** Date: 29 Mar 88 18:11:13 PST (Tue) From: tims%tekig5.pen.tek.com at RELAY.CS.NET To: t-discussion-request at mc.lcs.mit.edu Please add me to the T discussion mailing list. Thanks, Tim  0, unseen,, *** EOOH *** Date: Tue, 29 Mar 88 23:50:13 EST From: Jonathan A Rees Subject: [rsalz: Scheme mailing list and Usenet] To: SCHREQ@AI.AI.MIT.EDU Message-ID: <350257.880329.JAR@AI.AI.MIT.EDU> Date: Tue, 29 Mar 88 16:54:42 EST From: rsalz at pineapple.bbn.com To: jar at ai.ai.mit.edu Re: Scheme mailing list and Usenet Hiya. I don't read comp.lang.scheme, but I maintain Usenet around here at BBN. It's quite possible to set up a bidirectional gateway between a Usenet newsgroup and an Internet mailing list. For example, comp.protocols.tcp-ip articles are sent to the tcp-ip list and vice-versa. The impression I got is that the scheme list is moderated? If so, then it should be possible to arrange that you get a copy of all Usenet articles, so you can forward them. I think. If, however, the list isn't moderated, and you're just a maintainer of the mailing list, then it's even easier. (Sorry, no insult meant on "just"; I know what list maintenance (oops, pun) is like!) Here's what I suggest you do. Drop a line to Erik Fair, fair@ucbarpa.berkeley.edu and explain to him how the scheme list is run, and what you'd like to happen with comp.lang.scheme. Erik's a real nice guy, but somewhat disorganized and AMAZINGLY busy. He doesn't even work at UCB anymore. Expect that it'll take awhile for your request to get processed. As for scheme vs. T, one of the primary requirements for a Usenet newsgroup is based on volume. Since comp.lang.scheme seems to get two or three articles/day, average, there isn't desire or want to create a new newsgroup. Yeah, this might cause a hassle for T/scheme/Cscheme discussions. Hope this info helps. Some parts may be incomplete or inappropriate; as I said, I don't read scheme stuff, I just happened across your message. /rich $alz, rsalz@bbn.com  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 19:45:26 EST Received: from ATHENA (TCP 2222000047) by MC.LCS.MIT.EDU 29 Mar 88 19:44:18 EST Received: by ATHENA.MIT.EDU (5.45/4.7) id AA08269; Tue, 29 Mar 88 19:42:12 EST Received: by SNORKELWACKER.MIT.EDU (5.45/4.7) id AA13918; Tue, 29 Mar 88 18:59:42 EST Date: Tue, 29 Mar 88 18:59:42 EST From: Jean Marie Diaz Message-Id: <8803292359.AA13918@SNORKELWACKER.MIT.EDU> To: scheme-request@mc.lcs.mit.edu Subject: scheme@mc <--> comp.lang.scheme Reply-To: ambar@athena.mit.edu Usnail: 55 Grove St., Somerville, MA 02144 Nynex: (617) 623-6591 you can send mail to fair@ucbarpa.berkeley.edu to ask about the gatewaying scheme he uses, since he set it up. AMBAR  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 14:30:53 EST Received: from Apple.Com (TCP 30001235014) by MC.LCS.MIT.EDU 29 Mar 88 14:29:35 EST Received: by Apple.Com id AA11810; Tue, 29 Mar 88 11:20:49 PDT Date: Tue, 29 Mar 88 11:20:49 PDT From: Gene Garbutt Message-Id: <8803291920.AA11810@Apple.Com> To: t-discussion-request@MC.LCS.MIT.EDU Subject: add to mailing list Please add me to the mailing list. Gene Garbutt gwg%apple.apple.com@relay.cs.net  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 13:50:38 EST Received: from acf3.NYU.EDU (TCP 20036500015) by MC.LCS.MIT.EDU 29 Mar 88 13:49:30 EST Received: by acf3.NYU.EDU (5.54/25-eef) id AA00776; Tue, 29 Mar 88 13:46:24 EST Date: Tue, 29 Mar 88 13:46:24 EST From: Eric S. Tiedemann Message-Id: <8803291846.AA00776@acf3.NYU.EDU> To: scheme-request@mc.lcs.mit.edu Please add me to RRRS-AUTHORS as tiedeman@acf3.nyu.edu. Thanks, Eric S. Tiedemann  0, unseen,, *** EOOH *** Date: Tue, 29 Mar 88 13:04:59 EST From: Jonathan A Rees Subject: [ram-ashwin: T discussion and newsgroups] To: SCHREQ@AI.AI.MIT.EDU Message-ID: <349941.880329.JAR@AI.AI.MIT.EDU> Date: Mon, 28 Mar 88 15:03:48 EST From: Ashwin Ram Reply-To: Ram-Ashwin at YALE.ARPA (Ashwin Ram) To: JAR at AI.AI.MIT.EDU (Jonathan A Rees) Re: T discussion and newsgroups Full-Name: Ashwin Ram Organization: Computer Science, Yale University, New Haven, CT 06520-2158 In article <348649.880328.JAR@AI.AI.MIT.EDU> you write: > In that case, please carry on the conversation > here (or on comp.lang.scheme), as there is no "comp.lang.t" newsgroup to > my knowledge. Or lobby Berkeley to create one. The same goes for C > Scheme (I have repeatedly requested that they create a C Scheme > newsgroup, but they say they are too busy). I think the procedure to create a new newsgroup, as described in news.announce.newusers, is pretty straightforward. You post a message to all the relevant groups (including news.groups) describing the proposed newsgroup, and ask people to e-mail "yea" and "nay" votes to you. If you get at least 100 more yeas than nays, they make a newsgroup for you. Here are the complete "guidelines". I sure would be nice to have a comp.lang.t newsgroup (or perhaps comp.lang.scheme.t, comp.lang.scheme.c, etc.) I'll leave you to work out the details. [From news.announce.newusers:] Guidelines ---------- The following guidelines assume you have determined that you want a newsgroup to be created. You may want this newsgroup to address a topic of particular interest, or it might be to help subdivide an existing newsgroup. Once you have decided you want a new newsgroup, you should do the following: 1) Determine if a new newsgroup is actually needed. Look carefully through the lists of active newsgroups and mailing lists to be sure there is currently no existing forum for your topic. If there is such a group or mailing list, try using it before attempting to create a new group -- it might be just what you want. 2) Determine an appropriate name for your proposed newsgroup -- a name should be informative, reasonably short, and in an appropriate top-level hierarchy. Also determine if you want the newsgroup to be moderated or not. 3) Post an article to the newsgroup "news.groups" describing your proposed new group. Be sure to describe why you think the group is needed and/or interesting, and what you think it should be named. Ask for comments to be posted and for votes to be *MAILED* to you. Be sure to cross-post your article to any newsgroups where there might be interest, but set the "Followup-to" header so that responses only go to the "news.groups" group. 4) Consider carefully all comments and objections, whether posted or mailed. Answer objections and questions in a timely fashion. Change the name or nature of the group, if needed, based on the comments of others. Remember that the success of the group is based on the support and participation of the other people on the network, so listen to their advice and concerns. 5) Collect MAILED votes on the issue of the new newsgroup. The threshold currently set as necessary for creating a new group is 100 more "yes" votes than "no" votes in a 30 day period. a) If you get at least 100 more "yes" votes than "no" votes, post an article to the news.groups newsgroup including the totals and the list of account names of people voting. b) If you fail to get at least 100 more "yes" votes than "no" votes, consider starting a mailing list for your topic instead of a new group, or else think about starting the group as an "alt" group. If a group cannot get the support of at least 100 people in one month's time, it does not belong on the Usenet until such time as it gains sufficient support. c) If you are trying to get an exisiting mailing list upgraded to a newsgroup, consider the current subscriber list as a set of "yes" votes of equal number, but only if they have already agreed that they want the list turned into a newsgroup. 6) Send mail to "backbone@rutgers.edu" and ask that the group be created. You can issue the control message yourself, but many sites will ignore the group unless the control message originates from one of the known backbone admins (usually one of: spaf@arthur.cs.purdue.edu, mark@cbosgd.att.com, rick@uunet.uu.net, woods@hao.ucar.edu or fair@ucbarpa.berkeley.edu). If the group is moderated, be sure to include information about the moderator and submission addresses in your mail message so that the appropriate postings and databases can be updated. The group will likely be created at this time, but if the members of the backbone list perceive that there are serious unanswered questions about the group's creation, it may be postponed until those questions are resolved.  0, unseen,, *** EOOH *** Date: Tue, 29 Mar 88 13:03:44 EST From: Jonathan A Rees Subject: [MAILER-DAEMON: Returned mail: Service unavailable] To: SCHREQ@AI.AI.MIT.EDU Message-ID: <349940.880329.JAR@AI.AI.MIT.EDU> Date: Mon, 28 Mar 88 22:42:52 EST From: MAILER-DAEMON at flash.bellcore.com (Mail Delivery Subsystem) To: < at mc.lcs.mit.edu:JAR@mc.lcs.mit.edu> Re: Returned mail: Service unavailable ----- Transcript of session follows ----- >>> HELO flash.bellcore.com <<< 553 flash.bellcore.com I refuse to talk to myself 554 ... Service unavailable: Bad file number ----- Unsent message follows ----- Received: from RICE.EDU by flash.bellcore.com (5.58/1.1) id AA13386; Mon, 28 Mar 88 22:42:52 EST Received: from RELAY.CS.NET by rice.edu (AA25902); Mon, 28 Mar 88 21:41:47 CST Received: from mc.lcs.mit.edu by RELAY.CS.NET id aa04597; 28 Mar 88 21:52 EST Received: from AI.AI.MIT.EDU (CHAOS 3130) by MC.LCS.MIT.EDU 28 Mar 88 11:32:07 EST Date: Mon, 28 Mar 88 11:32:49 EST From: Jonathan A Rees Subject: [kranz: T operations, etc] To: t-discussion@mc.lcs.mit.edu Message-Id: <348696.880328.JAR@AI.AI.MIT.EDU> Note to people without Internet FTP access: as far as I know, no tapes will be made of T 3.1; you'll have to either beg or wait for T 3.2, which is due in May, probably. Date: Mon, 28 Mar 88 11:05:50 EST From: kranz at wheaties.ai.mit.edu (David Kranz) To: mcvax!ukc!reading!onion!minster!SoftEng!martin at uunet.uu.net cc: mcvax!ukc!its63b!aiva!jeff at uunet.uu.net, t3-bugs at YALE.ARPA Re: T operations, etc The operation stuff is indeed "unreleased". There is a T3.1 which is not yet officialy released but which you can get from anonymous ftp to wheaties.ai.mit.edu in the pub/t3.1 directory. Rebuilding and suspending systems is documented in this version and there is a script for doing so. In addition, it is possible to dynamically load C code and the interface is fully documented. -David Kranz  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 13:20:26 EST Received: from MITVMA.MIT.EDU (TCP 2227000003) by MC.LCS.MIT.EDU 28 Mar 88 12:19:38 EST Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Mon, 28 Mar 88 12:17:29 EST Received: from UKACRL.BITNET by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id 8978; Mon, 28 Mar 88 12:17:11 EST Received: from RL.IB by UKACRL.BITNET (Mailer X1.25) with BSMTP id 4597; Mon, 28 Mar 88 18:13:22 BST Via: UK.AC.RL.EARN; Mon, 28 Mar 88 18:13:20 BST Received: Via: UK.AC.DUR.EASBY; 28 MAR 88 18:13:01 BST From: Martin Ward Date: Mon, 28 Mar 88 18:14:43 +0100 Message-Id: <8803281714.AA18890@easby> To: t-discussion-request@MC.LCS.MIT.EDU *** EOOH *** Date: Mon, 28 Mar 88 18:14:43 +0100 From: Martin Ward To: t-discussion-request at MC.LCS.MIT.EDU Please put me on the t-discussion mailing list. Thanks. Martin. My ARPANET address is: martin%EASBY.DUR.AC.UK%CUNYVM.CUNY.EDU JANET: martin@uk.ac.dur.easby BITNET: martin%dur.easby@ac.uk UUCP: ukc!uk.ac.dur.easby!martin  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 14:01:32 EST Received: from MCC.COM (TCP 1200600076) by MC.LCS.MIT.EDU 28 Mar 88 13:36:09 EST Received: from obi-wan.aca.mcc.com by MCC.COM with TCP; Mon 28 Mar 88 11:04:15-CST Date: Mon, 28 Mar 88 11:04:11 CST From: mark@mcc.com (Mark Scheevel) Posted-Date: Mon, 28 Mar 88 11:04:11 CST Message-Id: <8803281704.AA00354@obi-wan.aca.mcc.com> Received: by obi-wan.aca.mcc.com (3.2/ACAv3.6) id AA00354; Mon, 28 Mar 88 11:04:11 CST To: t-discussion-request@mc.lcs.mit.edu *** EOOH *** Date: Mon, 28 Mar 88 11:04:11 CST From: mark at mcc.com (Mark Scheevel) To: t-discussion-request at mc.lcs.mit.edu Please add me to the t-discussion mailing list. Thanks, Mark Scheevel scheevel@mcc.com  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 14:18:33 EST Received: from ads.com (TCP 20071217020) by MC.LCS.MIT.EDU 28 Mar 88 14:11:48 EST Received: from meridian.ads.com by ads.com (5.58/1.9) id AA04997; Mon, 28 Mar 88 11:11:00 PST Message-Id: <8803281911.AA04997@ads.com> Received: by meridian (5.52/4.7) Date: Mon, 28 Mar 88 11:09:07 PST From: matsumot%meridian@ads.com (Michael Matsumoto) To: t-discussion-request@mc.lcs.mit.edu Subject: Subscription *** EOOH *** Date: Mon, 28 Mar 88 11:09:07 PST From: matsumot%meridian at ads.com (Michael Matsumoto) To: t-discussion-request at mc.lcs.mit.edu Re: Subscription Please subscribe me. Mike Matsumoto  1, unseen,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 15:59:29 EST Received: from entropy.ms.washington.edu (TCP 20027610431) by MC.LCS.MIT.EDU 28 Mar 88 14:40:03 EST Received: by entropy.ms.washington.edu (5.52.1/6.12) id AA21216; Mon, 28 Mar 88 11:36:25 PST Date: Mon, 28 Mar 88 11:36:25 PST From: jam@entropy.ms.washington.edu (John Alan McDonald) Return-Path: Message-Id: <8803281936.AA21216@entropy.ms.washington.edu> To: scheme-request@mc.lcs.mit.edu Subject: please remove me from the mailing list Cc: jam@entropy.ms.washington.edu *** EOOH *** Date: Mon, 28 Mar 88 11:36:25 PST From: jam at entropy.ms.washington.edu (John Alan McDonald) To: scheme-request at mc.lcs.mit.edu cc: jam at entropy.ms.washington.edu Re: please remove me from the mailing list Please remove me from the list, Thanks. John Alan McDonald, Statistics, GN-22, U of W, Seattle, Wa. 98195 (206) 545 7438, 543 2517 jam@entropy.ms.washington.edu {decvax,ihnp4,ucbvax!lbl-csam}!uw-beaver!entropy!jam  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 16:11:24 EST Received: from XX.LCS.MIT.EDU (CHAOS 2420) by MC.LCS.MIT.EDU 28 Mar 88 14:58:53 EST Received: from MICKEY-MOUSE.LCS.MIT.EDU by XX.LCS.MIT.EDU via Chaosnet; 28 Mar 88 14:55-EST Date: Mon, 28 Mar 88 14:56 EST From: Mark A. Sheldon Subject: Please add me To: t-discussion-request@MC.LCS.MIT.EDU Message-ID: <880328145650.6.DEATH@MICKEY-MOUSE.LCS.MIT.EDU> *** EOOH *** Date: Mon, 28 Mar 88 14:56 EST From: Mark A. Sheldon To: t-discussion-request at MC.LCS.MIT.EDU Re: Please add me Thanks. -Mark (Death@XX.LCS.MIT.EDU)  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 16:24:33 EST Received: from SUMEX-AIM.Stanford.EDU (TCP 1200000070) by MC.LCS.MIT.EDU 28 Mar 88 15:58:28 EST Date: Mon, 28 Mar 88 12:16:11 PST From: Max Hailperin Subject: Re: scheme mailing list To: scheme-request@mc.lcs.mit.edu In-Reply-To: <348693.880328.JAR@AI.AI.MIT.EDU> Message-ID: <12386001112.41.HAILPERIN@SUMEX-AIM.Stanford.EDU> *** EOOH *** Date: Mon, 28 Mar 88 12:16:11 PST From: Max Hailperin To: scheme-request at mc.lcs.mit.edu Re: scheme mailing list > I hear that SUSHI is going away. Please send your new address to > scheme-request@mc.lcs.mit.edu. Thanks for being so on top of things. I actually sent my new address already, but in case your message implicitly means it didn't get through, here goes again: Old address: hailperin@sushi.stanford.edu New address: hailperin@sumex-aim.stanford.edu Thanks.  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 16:25:59 EST Received: from MITVMA.MIT.EDU (TCP 2227000003) by MC.LCS.MIT.EDU 28 Mar 88 16:09:05 EST Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Mon, 28 Mar 88 15:09:35 EST Received: from DB0TUI6.BITNET (NET) by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id 0404; Mon, 28 Mar 88 15:09:32 EST Received: by tub.UUCP; Mon, 28 Mar 88 21:59:19 +0200; AA22568 Date: Mon, 28 Mar 88 21:59:19 +0200 From: Oliver Laumann Message-Id: <8803281959.AA22568@tub.UUCP> To: t-discussion-request@MC.LCS.MIT.EDU Subject: Add me. *** EOOH *** Date: Mon, 28 Mar 88 21:59:19 +0200 From: Oliver Laumann To: t-discussion-request at MC.LCS.MIT.EDU Re: Add me. Please add the address t-l%tub.BITNET@MITVMA.MIT.EDU to the T discussions mailing list. Thank you in advance. -- Regards, Oliver Laumann, Technical University of Berlin, Germany. ...!pyramid!tub!net or net@TUB.BITNET  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 18:09:21 EST Received: from csvax.caltech.edu (TCP 1200200066) by MC.LCS.MIT.EDU 28 Mar 88 18:06:18 EST Received: by csvax.caltech.edu (5.54/1.2) id AA00211; Mon, 28 Mar 88 15:03:59 PST Date: Mon, 28 Mar 88 15:03:59 PST From: newton@csvax.caltech.edu (Mike Newton) Message-Id: <8803282303.AA00211@csvax.caltech.edu> To: t-discussion-request@mc.lcs.mit.edu Subject: please add me *** EOOH *** Date: Mon, 28 Mar 88 15:03:59 PST From: newton at csvax.caltech.edu (Mike Newton) To: t-discussion-request at mc.lcs.mit.edu Re: please add me Hi... Please add me (newton@csvax.caltech.edu) to the list. Thanks, - mike  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 28 Mar 88 23:15:12 EST Received: from Sierra.Stanford.EDU (TCP 4402400015) by MC.LCS.MIT.EDU 28 Mar 88 23:13:14 EST Date: Mon, 28 Mar 1988 20:10 PST Message-ID: From: DAVIES@Sierra.Stanford.EDU To: scheme-request@MC.LCS.MIT.EDU Subject: Please remove me cc: Davies@Sierra.Stanford.EDU Please remove me from the Scheme mailing list. This is no reflection on the quality of the discussions, which are often very interesting. My interests have migrated elsewhere, however. -- Byron  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 01:25:05 EST Received: from polya.stanford.edu (TCP 4402000240) by MC.LCS.MIT.EDU 29 Mar 88 00:52:07 EST Received: by polya.stanford.edu (5.54/inc-1.2) id AA23724; Mon, 28 Mar 88 21:49:46 PST Date: Mon, 28 Mar 88 21:49:46 PST From: andy@polya.stanford.edu (Andy Freeman) Message-Id: <8803290549.AA23724@polya.stanford.edu> To: t-discussion-request@mc.lcs.mit.edu Subject: please change andy@sushi to andy@polya.stanford.edu *** EOOH *** Date: Mon, 28 Mar 88 21:49:46 PST From: andy at polya.stanford.edu (Andy Freeman) To: t-discussion-request at mc.lcs.mit.edu Re: please change andy@sushi to andy@polya.stanford.edu thanks, -andy  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 01:44:19 EST Received: from ee.ecn.purdue.edu (TCP 20013500417) by MC.LCS.MIT.EDU 29 Mar 88 01:42:45 EST Received: by ee.ecn.purdue.edu (5.54/1.12jrs) id AA12152; Tue, 29 Mar 88 01:40:35 EST Message-Id: <8803290640.AA12152@ee.ecn.purdue.edu> Received: by iuvax.cs.indiana.edu; (iuvax/MX/4.5/02-10-87) id AA18965; Tue, 29 Mar 88 01:12:03 EST Date: Tue, 29 Mar 88 01:12:03 EST From: Eric Ost To: t-discussion-request@mc.lcs.mit.edu Subject: Please add me to the T-Discussion mailing list... *** EOOH *** Date: Tue, 29 Mar 88 01:12:03 EST From: Eric Ost To: t-discussion-request at mc.lcs.mit.edu Re: Please add me to the T-Discussion mailing list... Thanks, eric  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 07:40:20 EST Received: from MITVMA.MIT.EDU (TCP 2227000003) by MC.LCS.MIT.EDU 29 Mar 88 07:39:06 EST Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Tue, 29 Mar 88 07:37:03 EST Received: from HENUT5.BITNET (SPLIT) by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id 5157; Tue, 29 Mar 88 07:37:01 EST Date: Tue, 29 Mar 88 11:31 N From: Subject: changed E-mail address To: T-Discussion-Request@MC.LCS.MIT.EDU X-Original-To: tproj, SPLIT Please note my changed E-mail address, Dolf M. Maaswinkel University of Twente Dept. of Instructional Technology P.O.Box 217, 7500 AE Enschede NETHERLANDS tel. (53) 893598 Electronic mail address : (Bitnet) split@henut5 ______________________________________________________  0, unseen,, *** EOOH *** Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 07:41:25 EST Received: from XX.LCS.MIT.EDU (CHAOS 2420) by MC.LCS.MIT.EDU 29 Mar 88 07:39:29 EST Received: from RELAY.CS.NET by XX.LCS.MIT.EDU with TCP/SMTP; Tue 29 Mar 88 07:36:04-EST Date: Tue, 29 Mar 88 7:21:50 EST From: RELAY Mail System (MMDF) Sender: mmdf@RELAY.CS.NET Subject: Failed mail (msg.aa24355) To: @XX.LCS.MIT.EDU,@mc.lcs.mit.edu:scheme-request@mc.lcs.mit.edu After 7 days (158 hours), your message could not be fully delivered. It failed to be received by the following address(es): raulefs@cel.fmc.com (host: cel.fmc.com) (queue: smtp) Problems usually are due to service interruptions at the receiving machine. Less often, they are caused by the communication system. Your message follows: Received: from xx.lcs.mit.edu by RELAY.CS.NET id aa24355; 22 Mar 88 16:12 EST Received: from MC.LCS.MIT.EDU by XX.LCS.MIT.EDU with Chaos/SMTP; Tue 22 Mar 88 16:03:20-EST Received: from ucbvax.Berkeley.EDU (TCP 1200400116) by MC.LCS.MIT.EDU 22 Mar 88 15:33:24 EST Received: by ucbvax.Berkeley.EDU (5.58/1.26) id AA21491; Tue, 22 Mar 88 04:37:21 PST Received: from USENET by ucbvax.Berkeley.EDU with netnews for scheme@mc.lcs.mit.edu (scheme@mc.lcs.mit.edu) (contact usenet@ucbvax.Berkeley.EDU if you have questions) Date: 21 Mar 88 23:31:20 GMT From: hpcea!hpccc!ga@hplabs.hp.com (G.A. Gordon) Organization: HP Corporate Computing Center Subject: Re: xscheme Message-Id: <160001@hpccc.HP.COM> References: <1538@ncsuvx.ncsu.edu> Sender: scheme-request@mc.lcs.mit.edu To: scheme@mc.lcs.mit.edu / hpccc:comp.lang.scheme / gjs@ZOHAR.AI.MIT.EDU (Gerald Jay Sussman) / 8:20 pm Mar 2, 1988 / You said: I'm just an undergraduate, my opinion doesn't matter. Why do you feel that way? You have an unhealthy self-image problem. Your opinion does matter, at least it does to me. ----------  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 07:44:35 EST Received: from MITVMA.MIT.EDU (TCP 2227000003) by MC.LCS.MIT.EDU 29 Mar 88 07:43:11 EST Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU ; Tue, 29 Mar 88 07:41:07 EST Received: from HENUT5.BITNET (SPLIT) by MITVMA.MIT.EDU (Mailer X1.25) with BSMTP id 5190; Tue, 29 Mar 88 07:41:05 EST Date: Tue, 29 Mar 88 11:21 N From: Subject: TC compiler for T2.8 To: T-Discussion-Request@MC.LCS.MIT.EDU X-Original-To: tproj, SPLIT *** EOOH *** Date: Tue, 29 Mar 88 11:21 N From: To: T-Discussion-Request at MC.LCS.MIT.EDU Re: TC compiler for T2.8 I am using the T2.8 interpreter, and desperately seeking for a TC compiler; I am currently running programs on a VAX 11/750 with ULTRIX V2.0. Can someone help me ? Dolf M. Maaswinkel University of Twente Dept. of Instructional Technology P.O.Box 217, 7500 AE Enschede NETHERLANDS tel. (53) 893598 Electronic mail address : (Bitnet) split@henut5 ______________________________________________________  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 10:25:14 EST Received: from acf2.NYU.EDU (TCP 20036500014) by MC.LCS.MIT.EDU 29 Mar 88 10:22:43 EST Received: by acf2.NYU.EDU (5.54/25-eef) id AA04525; Tue, 29 Mar 88 10:19:49 EST Date: Tue, 29 Mar 88 10:19:49 EST From: Benjamin Goldberg Message-Id: <8803291519.AA04525@acf2.NYU.EDU> To: t-discussion-request@MC.LCS.MIT.EDU Subject: mailing list *** EOOH *** Date: Tue, 29 Mar 88 10:19:49 EST From: Benjamin Goldberg To: t-discussion-request at MC.LCS.MIT.EDU Re: mailing list Please add me to the t-discussion mailing list. -Ben  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 10:52:54 EST Received: from megaron.arizona.edu (TCP 20061003001) by MC.LCS.MIT.EDU 29 Mar 88 10:51:07 EST Date: Tue, 29 Mar 88 08:49:19 MST From: "Mike Coffin" Message-Id: <8803291549.AA06564@megaron.arizona.edu> Received: by megaron.arizona.edu; Tue, 29 Mar 88 08:49:19 MST To: t-discussion-request@MC.LCS.MIT.EDU Subject: request to be added to the mailing list *** EOOH *** Date: Tue, 29 Mar 88 08:49:19 MST From: Mike Coffin To: t-discussion-request at MC.LCS.MIT.EDU Re: request to be added to the mailing list Could you add me to the T-Discussion mailing list? Mike Coffin mike@arizona.edu Univ. of Ariz. Dept. of Comp. Sci. {allegra,cmcl2,ihnp4}!arizona!mike Tucson, AZ 85721 (602)621-4252  1,, Received: from MC.LCS.MIT.EDU (CHAOS 3131) by AI.AI.MIT.EDU 29 Mar 88 10:53:57 EST Received: from ifi.uio.no (TCP 20011601002) by MC.LCS.MIT.EDU 29 Mar 88 10:52:47 EST Date: Tue, 29 Mar 88 17:50:26 +0200 From: even@ifi.uio.no Message-Id: <8803291550.AA00494@gaut> To: t-discussion-request@MC.LCS.MIT.EDU Subject: t-discussion *** EOOH *** Date: Tue, 29 Mar 88 17:50:26 +0200 From: even at ifi.uio.no To: t-discussion-request at MC.LCS.MIT.EDU Re: t-discussion Please add me to the mailing list.