info-vax (05/18/82)
>From CPR@MIT-XX Tue May 18 14:34:44 1982
What's a reliable way to write tapes under Unix (with both binary
and text files) to be read by VMS? Does using dd in the obvious way
do the right thing?
-------info-vax (05/18/82)
>From greep@RAND-UNIX Tue May 18 15:00:48 1982
I'm not sure what you mean by "the obvious thing". Unix text files are
stored with line-feeds but no carriage-returns. I have a very simple
program which adds carriage returns which I will be glad to send you if
you want. Its output can be directed right to /dev/mt0, or you can
pipe it through dd if you want to select the tape block size.
Going the other way, carriage returns can be deleted with the tr program.info-vax (05/19/82)
>From RWK@SCRC-TENEX@MIT-AI Tue May 18 19:53:09 1982
Date: Tuesday, 18 May 1982 14:56-PDT
From: greep at RAND-UNIX
I'm not sure what you mean by "the obvious thing". Unix text files are
stored with line-feeds but no carriage-returns. I have a very simple
program which adds carriage returns which I will be glad to send you if
you want. Its output can be directed right to /dev/mt0, or you can
pipe it through dd if you want to select the tape block size.
Going the other way, carriage returns can be deleted with the tr
program.
I'm confused. What's wrong with just writing an ANSI standard format
tape? Software exists for reading and writing ANSI standard format
tapes from UNIX. Then your tapes can be read on VMS, TOPS20 (software
for ANSI tapes exists at MIT (ANSIWRITE & ANSIREAD on XX, complete with
HELP file), Multics, IBM, etc.). I will carefully abstain from flaming
about how Unix has historically been oblivious to how the rest of the
world communicates.
If the software to handle ANSI tapes isn't on your Unix, I'll ask around
to find it. A copy was sent to Fateman at Berkeley to facilitate
shipping MACSYMA sources from MIT to Berkeley. If it didn't make it
into 4.1 BSD there's no good reason for it.