The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jsteve@superglobalmegacorp.com (Jason Stevens)
Subject: [TUHS] 4.3 Wisc file transfer
Date: Mon, 10 Apr 2017 09:46:54 +0800	[thread overview]
Message-ID: <4FA45575-95C4-4E93-ACB9-F031BD868D0C@superglobalmegacorp.com> (raw)
In-Reply-To: <850255f3-8ce3-a051-51c7-cb11fcdb0aab@mhorton.net>

You have to remember this is old stuff, so you will have to fight protocol drift.

Simh has issues using pcap and talking to the host is, it's more so a pcap limitation.  I think the newer version has tun/tap support which may be easier to deal with, although more involved.

My favorite way was using a web server to serve files out.  As for getting stuff in, a simple CGI or like thing for uploading.

Back in 4.3 land, ftp is going to be active mode, there was no nat, no passive mode, so you'll need to configure accordingly.

How do you have your lan setup?  What host OS? Are you trying to access fSit from the same machine?  

In the past I've had to use uuencode/uudecode on a connection to transfer the bare minimum of a pre-compiled GCC to sparc solaris, so I know this pain.

Also don't forget if you have tty access you can build sz/rz and use Z-modem.

NFS should be present in UWisc, it has many Sun stuff built in.  But keep in mind it's very old, and could easily suffer from odd things like block size issues, akin to stuff like ancient Sun-100U / Sun-2 had.

On April 10, 2017 1:14:06 AM GMT+08:00, Mary Ann Horton <mah at mhorton.net> wrote:
>Apologies if this is already on the list somewhere.
>
>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.
>
>Also, what's the recommended way to shut down the system?  I shutdown 
>now to single user, then sync a few times, then ^E, but when I boot 
>again I get fsck errors serious enough to require a manual fsck (which 
>generally works fine.)
>
>Thanks,
>
>     Mary Ann

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170410/d6766677/attachment.html>


  parent reply	other threads:[~2017-04-10  1:46 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
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 [this message]
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=4FA45575-95C4-4E93-ACB9-F031BD868D0C@superglobalmegacorp.com \
    --to=jsteve@superglobalmegacorp.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).