From RPKatMIT-XX  Wed Jun 30 00:00:00 1982
From: RPKatMIT-XX (Robert P. Krajewski)
Date: 30 Jun 1982, 00:00
Subject: XGPSEND
Message-ID: <mailman.322.1479821109.4695.its@nocrew.org>

[The Twenex program] does not work from XX or OZ.  It can't create a
spooling file.  Have some protocols been changed or something ?  Yes,
people don't use the XGP much, but ...

bob
-------

From ALANatMIT-MC  Sat Jun 26 00:00:00 1982
From: ALANatMIT-MC (Alan Bawden)
Date: 26 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.323.1479821109.4695.its@nocrew.org>

Supdup figures that when you type <break>P you probably don't even want it as
your current job anymore, so it cleverly sets some OTHER job as being current.
That's what it's doing when it valrets <alt>1J to your DDT, it's trying to
select your PREVIOUSLY selected job.  This is why you somtimes get the error
message JOB GONE? when leaving a supdup (the previously selected job has
dissapeared since you started your supdup).

I guess it's somebody's idea of a feature.  I've never found the slightest bit
convienent.


From HDTatMIT-AI  Fri Jun 25 00:00:00 1982
From: HDTatMIT-AI (Howie Daniel Trachtman)
Date: 25 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.324.1479821109.4695.its@nocrew.org>

  This is minor, but I just thought you might like to know.
I had a supdup to oz which I typed <break>p to get back to ai`s ddt.

I then later had to :mc for something...
  Then I did a <break>p to get back to AI, and sent someone a message, and
did not start up any jobs.  However, when I did a :contin I got my oz job.
  Am I seeing things, or is this a bug?
BTW, my mc job was still around afterwards.

--Howard--

From GJC at MIT-MC  Tue Jun 22 00:00:00 1982
From: GJC at MIT-MC (GJC at MIT-MC)
Date: 22 Jun 1982 00:00
Subject: the strangest thing
Message-ID: <mailman.325.1479821109.4695.its@nocrew.org>

I was running :CHTN HTJR, a vax running VMS. On the Vax I ran a program
which does a lot of I/O displaying information like a PEEK program
(it was a peek type program) and taking character input at interrupt level.
I ran this peek program looking at itself, and low and behold the CHTN
was too busy or something to listen very well, even to the CHTN break
character. That is, I found I could not break out of CHTN nor get
any response from the VAX which just kept outputing characters.
I then hung up the phone and redialed MC.
Being brave, I then did :UJOB GJC HACTRO and :SNARF CHTN.
The CHTN and the DDT then seemed to have control of the TTY at
the *same* time, DDT getting characters only once in a while
with the CHTN doing lots of output to my TTY. I then HUNG UP the phone
again, and sent this bug note.

Later... It seems I can reproduce this condition at will.


From MOON at MIT-MC  Sat Jun 19 00:00:00 1982
From: MOON at MIT-MC (MOON at MIT-MC)
Date: 19 Jun 1982 00:00
Subject: MC:.MAIL.;NAMES > is too large
Message-ID: <mailman.326.1479821109.4695.its@nocrew.org>

space frequently.  If you read the file, a great deal of it looks like pure trash.
I removed a few obviously obsolete entries; others should do the same.  It may
be necessary to remove some of the large mailing lsts into separate files
(using @FILE).  It would also be desirable to remove the personal entries for
people who no longer exist; I don't know if there is a reliable way to tell whether
someone no longer exists.  I also personally feel that the full-name entries at
the end of the file are worthless and should be flushed, although others may disagree.

From ZVONAatMIT-AI  Thu Jun 17 00:00:00 1982
From: ZVONAatMIT-AI (David Chapman)
Date: 17 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.327.1479821109.4695.its@nocrew.org>

It seems that the msgs times was reset sometime last night.
Everyone says that they had to read all the old messages again.

From DulceyatMIT-AI  Thu Jun 17 00:00:00 1982
From: DulceyatMIT-AI (Mark J. Dulcey)
Date: 17 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.328.1479821109.4695.its@nocrew.org>

I corrected a bug in the file AI: LMIO1; RFONTW >, and installed the
changes on the Lisp Machine.  However, I know that these functions are
also used by other folks (not on the Lisp Machine), so I thought I'd let
you know so you can recompile and load the new FASL files.

From DCP at MIT-MC  Mon Jun 14 00:00:00 1982
From: DCP at MIT-MC (DCP at MIT-MC)
Date: 14 Jun 1982 00:00
Subject: No subject
Message-ID: <mailman.330.1479821109.4695.its@nocrew.org>

Not without a good deal of hacking.  They are different operating
systems, and OZ is not on the ARPAnet, which is what the infamous
MLDEV uses.  The standard ITS 6 character DIR, FN1 and FN2 will
not map well to a twenex file system, and not many programs
implement RMS's string open system call to get around this
problem.


From DCP at MIT-MC  Mon Jun 14 00:00:00 1982
From: DCP at MIT-MC (DCP at MIT-MC)
Date: 14 Jun 1982 00:00
Subject: No subject
Message-ID: <mailman.331.1479821109.4695.its@nocrew.org>

Not without a good deal of hacking.  They are different operating
systems, and OZ is not on the ARPAnet, which is what the infamous
MLDEV uses.  The standard ITS 6 character DIR, FN1 and FN2 will
not map well to a twenex file system, and not many programs
implement RMS's string open system call to get around this
problem.


From CStacyatMIT-AI  Mon Jun 14 00:00:00 1982
From: CStacyatMIT-AI (Christopher C. Stacy)
Date: Monday, 14 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.332.1479821109.4695.its@nocrew.org>

    RICH at MIT-MC 06/14/82 10:35:45
    To: (BUG ITS) at MIT-MC
    Will it be possible soon to have OZ: as a device from ITS
    like MC:, etc.
	

As I explained when we were deciding what operating system to
run, TOPS-20 doesn't have any facility for doing this sort of
thing.  It is a major task to write it into the guts of the
Tops-20 monitor.  I (or someone) will probably be working on it
in the near future, but it is likely to take a while.

Chris



From MOON at MIT-MC  Mon Jun 14 00:00:00 1982
From: MOON at MIT-MC (MOON at MIT-MC)
Date: 14 Jun 1982 00:00
Subject: OZ: device
Message-ID: <mailman.333.1479821109.4695.its@nocrew.org>

It's possible but unlikely.  The problem is that the inter-ITS
devices simply relay system calls from the remote machine to the foreign
machine.  20X has, of course, different system calls, and not all
the ITS system calls map simply into 20X system calls.  There is also
the issue of incompatible file name lengths and syntax.

On the other hand, since it was done for the FC: it can probably be
done for OZ also assuming someone is available to do the work.
If the FC: device used the standard file access protocol that 20X
already supports, it would have been trivial to extend it into an OZ:
device.  Since it uses a private protocol instead, either that protocol
will have to be implemented on TOPS-20 or an entirely new job-device
program will have to be written.

From RICH at MIT-MC  Mon Jun 14 00:00:00 1982
From: RICH at MIT-MC (RICH at MIT-MC)
Date: 14 Jun 1982 00:00
Subject: No subject
Message-ID: <mailman.334.1479821109.4695.its@nocrew.org>

Will it be possible soon to have OZ: as a device from ITS
like MC:, etc.
	

From MCB at MIT-MC  Fri Jun 11 00:00:00 1982
From: MCB at MIT-MC (MCB at MIT-MC)
Date: 11 Jun 1982 00:00
Subject: No subject
Message-ID: <mailman.335.1479821109.4695.its@nocrew.org>

I was just looking for some tip info and noticed that .info.;tip manual
on MC appears to have been clobbered sometime early this morning.


From GUMBYatMIT-AI  Tue Jun  8 00:00:00 1982
From: GUMBYatMIT-AI (David Vinayak Wallace)
Date: 8 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.336.1479821109.4695.its@nocrew.org>

When I am in emacs on a AAA and I get a send while the screen is redisplaying,
part of the buffer is displayed under the mode line.

From MARTYatMIT-AI  Tue Jun  8 00:00:00 1982
From: MARTYatMIT-AI (Martin David Connor)
Date: 8 June 1982, 00:00
Subject: No subject
Message-ID: <mailman.337.1479821109.4695.its@nocrew.org>


I found not one, but wo bogus copies of OCTPUS on the
SYS directories.  One was 35 blocks long, and would not
BINPRT. The other was small, and unrecognizable.

Please keep your eyes open for this bogosity, because people
are using these to log in and do damage.  Thanks.

Marty


From RWKatSCRC-TENEX  Wed Jun  2 00:00:00 1982
From: RWKatSCRC-TENEX (Robert W. Kerns)
Date: Wednesday, 2 June 1982, 00:00
Subject: 2-character escape sequences getting broken up
In-Reply-To: The message of 27 May 82 03:00-EDT from David A. Moon <Moon at SCRC-TENEX>
Message-ID: <mailman.338.1479821109.4695.its@nocrew.org>


    Date: Thursday, 27 May 1982, 03:00-EDT
    From: David A. Moon <Moon at SCRC-TENEX>
    DDT could avoid this by doing its interrupt-level typeout
    (e.g. of sends) on a separate I/O channel.
DDT doesn't do interrupt-level typeout.  DDT gets interrupted and goes
off and does other typeout, via the HAKKAH kludge.  I think the problem
is with ECHOED (at ITS interrupt level) typeout anyway, not with DDT's
typeout.

From PDL  Thu Jun  3 00:00:00 1982
From: PDL (P. David Lebling)
Date: 3 Jun 1982, 00:00
Subject: M-X DIRED$MEYER;AR9:
Message-ID: <[MIT-DMS].233727>

I was finally able to reproduce the problem, but it went away after
a while.  I have to assume that the problem is with EMACS, because
even when it was losing in EMACS saying :PRINT DIRAR9:NAME1 UP worked
in DDT.  Alternatively it may be a funny timing problem with the
archive or dir device.  In any case, I am CCing this to BUG-ITS and
BUG-EMACS in the hope that someone can help.

For those who are hearing about this problem for the first time,
in EMACS, M-X DIRED$MEYER;AR9: (and other archives, on DM) often
gets FILE LOCKED? errors.  It seems to always go away eventually, but
eventually return.  Could this be a JOBREU lossage with one of those
devices not reiniting properly?

	Dave