From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Unix v6 File System information
Date: Sun, 21 Feb 2016 16:21:42 -0500 [thread overview]
Message-ID: <CAC20D2PqLyjyGPbwTRM8GJCW86yRufm8vOwPvSKG=j8Pd43Wcg@mail.gmail.com> (raw)
In-Reply-To: <56CA26A3.20206@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Sun, Feb 21, 2016 at 4:05 PM, Will Senn <will.senn at gmail.com> wrote:
> Why, oh why, didn't someone save a tape image, rather than a tarball,
> given that tar on v6 was so hokey?!
hmm - no idea. I don't remember having had such problems to be honest.
Maybe we can find the a tp image. I'm sure they reason they used a tar
image was, that tp was more problematic.
That said, I still think the tar image should work. Maybe the solution is
try to compiler stp with a modern C compiler. It will take some work to
move it I suspect because the code would be 100% assuming PDP-11 in every
way, and is binary. Plus things like stat.h are a bit different than in
the old days. Let's take this off-line and let see what's possible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160221/d86d9107/attachment.html>
next prev parent reply other threads:[~2016-02-21 21:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 18:27 Noel Chiappa
2016-02-21 18:59 ` Clem Cole
2016-02-21 19:31 ` arnold
2016-02-21 20:45 ` Will Senn
2016-02-21 21:06 ` Clem Cole
2016-02-21 21:05 ` Will Senn
2016-02-21 21:21 ` Clem Cole [this message]
2016-02-22 2:20 ` Warren Toomey
[not found] ` <2D41A491-40CD-41DB-B3BA-0ACBD831E2C7@gmail.com>
2016-02-22 7:27 ` Warren Toomey
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 1:54 Norman Wilson
2016-02-22 3:02 ` Larry McVoy
2016-02-21 21:51 Noel Chiappa
2016-02-21 17:50 Noel Chiappa
2016-02-21 18:36 ` Random832
2016-02-22 13:10 ` ron
2016-02-21 11:44 Noel Chiappa
2016-02-21 13:34 ` Dave Horsfall
2016-02-21 15:21 ` Will Senn
2016-02-21 17:21 ` John Cowan
2016-02-22 1:58 ` Dave Horsfall
2016-02-22 2:32 ` Lyndon Nerenberg
2016-02-22 12:30 ` Tony Finch
2016-02-21 15:36 ` Will Senn
2016-02-21 20:24 ` Warren Toomey
2016-02-21 17:31 ` Random832
2016-02-21 17:36 ` ron
2016-02-21 9:45 Will Senn
2016-02-21 10:01 ` Dave Horsfall
2016-03-04 19:10 ` Jacob Ritorto
2016-03-10 8:51 ` Dave Horsfall
2016-03-10 9:31 ` SPC
2016-02-21 10:27 ` arnold
2016-02-21 12:29 ` Dave Horsfall
2016-02-21 13:54 ` arnold
2016-02-21 14:40 ` Clement T. Cole
2016-03-04 9:27 ` Dave Horsfall
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='CAC20D2PqLyjyGPbwTRM8GJCW86yRufm8vOwPvSKG=j8Pd43Wcg@mail.gmail.com' \
--to=clemc@ccc.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).