The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pechter@gmail.com (William Pechter)
Subject: [TUHS] 4.3 Wisc file transfer
Date: Sun, 9 Apr 2017 23:32:50 -0400	[thread overview]
Message-ID: <406d9148-497c-4bfe-89a9-19103af4add4.maildroid@localhost> (raw)
In-Reply-To: <20170410000508.GA28291@minnie.tuhs.org>

Should work fine with the 4.3 template tape... But I would save the original kernel
just in case

I moved binaries from the older 4.3 to Reno and uWisc without problems. 

Ftp works.  I wish I could get lynx and wet to build. 

Bill





-----Original Message-----
From: Warren Toomey <wkt@tuhs.org>
To: Mary Ann Horton <mah at mhorton.net>
Cc: TUHS main list <tuhs at minnie.tuhs.org>
Sent: Sun, 09 Apr 2017 20:05
Subject: Re: [TUHS] 4.3 Wisc file transfer

On Sun, Apr 09, 2017 at 10:14:06AM -0700, Mary Ann Horton wrote:
> 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.

I don't know how close 4.3UWisc is (in terms of config files etc.) to
valilla 4.3BSD, but you might be able to untar the 4bsd-uucp customisation
tarball over the top of 4.3UWisc. That would get you the ftp binary with
PASV on by default, and the de0 interface set up with a working NAT IP
address. Then you could set up a local ftp server on another box.

I'm nearly out the door for a week's break else I'd try it out.
Cheers, Warren


  reply	other threads:[~2017-04-10  3:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-09 17:14 Mary Ann Horton
2017-04-10  0:05 ` Warren Toomey
2017-04-10  3:32   ` William Pechter [this message]
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
2017-04-09 23:10 Noel Chiappa
2017-04-09 23:20 ` Arthur Krewat

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=406d9148-497c-4bfe-89a9-19103af4add4.maildroid@localhost \
    --to=pechter@gmail.com \
    /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).