The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] 4.3 Wisc file transfer
Date: Sun, 9 Apr 2017 19:20:35 -0400	[thread overview]
Message-ID: <9a2474cf-0a88-2de8-c6a9-5e77eb7c95e9@kilonet.net> (raw)
In-Reply-To: <20170409231058.8F42F18C0C2@mercury.lcs.mit.edu>

I haven't done it, but wouldn't Kermit be relatively painless over a 
serial line?

http://www.kermitproject.org/ck90.html

I used it on TOPS-10 and SIMH, using a TELNET connection into an 
emulated DZ11 (the version that I got working with SIMH, not the newer one).

Put KERMIT on the BSD side into server mode, and just send all the files 
you want to.



On 4/9/2017 7:10 PM, Noel Chiappa wrote:
>      > From: Mary Ann Horton
>
>      > What's the best way to transfer files in and out of the simh 4.3BSD Wisc
>      > version?  I can do it with tape files, but it seems like FTP or ssh or
>      > NFS ought to be possible, and none is behaving at first blush.
>
> Someone should add the equivalent of Ersatz-11's 'DOS' device to SIMH; it's a
> pseudo-device that can read files on the host filesystem. (Other stuff too,
> but that's the relevant one here.) A short device driver in the emulated OS,
> and a program to talk to it, and voila, getting a file into the emulated
> system is a short one line command, none of this hassle with putting the bits
> on a virtual tape, etc, etc.
>
> I found editing files with 'ed' on my simulated V6 system painful (although i
> still have the mental microcode to do it), so I did my editing under Windows
> (Epsilon), and then read the file down to the Unix to compile it. Initially I
> was doing it by putting the file on a raw virtual pack, and doing something
> similar to that tape kludge. Then I got smart, and whipped up a driver for the
> DOS device in Ersatz-11, and a program that used it, to allow me to easily
> read a file from the Windows filesystem down to the Unix. Going around the
> compile-debug-edit loop is totally painless now.
>
> 	Noel
>



  reply	other threads:[~2017-04-09 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-09 23:10 Noel Chiappa
2017-04-09 23:20 ` Arthur Krewat [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-04-09 17:14 Mary Ann Horton
2017-04-10  0:05 ` Warren Toomey
2017-04-10  3:32   ` William Pechter
2017-04-10  3:56     ` jsteve
2017-04-10  4:26       ` Henry Bent
2017-04-10 15:23     ` Mary Ann Horton
2017-04-10 15:42       ` Jason Stevens
2017-04-10 15:43         ` Cory Smelosky
2017-04-10 23:52           ` Jason Stevens
2017-04-10 16:13       ` William Pechter
2017-04-11 12:37         ` Jason Stevens
2017-04-10  1:46 ` Jason Stevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a2474cf-0a88-2de8-c6a9-5e77eb7c95e9@kilonet.net \
    --to=krewat@kilonet.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).