The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] 2bsd tarball
Date: Tue, 28 Jul 2020 19:46:56 -0500	[thread overview]
Message-ID: <a43bafab-1d20-d912-a83e-d7e3cc9d051e@gmail.com> (raw)
In-Reply-To: <CANCZdfpHbELdJdeuX7EvWRM0Xxe+Y+JNdknTxQFDM5vPi1jUWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

On 7/28/20 7:09 PM, Warner Losh wrote:
> Both of the 2bsd tapes you found are from the days when Berkeley just 
> sent patches to the 7th Edition out. The 2.8BSD tape was the first one 
> to have a kernel that was bootable from the tape. The 2BSD tapes 
> originally had 2 files on them. The first one was a binary copy of tar 
> that ran on V7. The second was a tarball of all the rest. As you 
> discovered, they shipped with a label like:
>         Second Berkeley Software Tape
>         May 10, 1979    TAR 800BPI
>
>         %dd if=/dev/mt0 bs=1b skip=1 of=tar
>         %chmod 755 tar
>         % tar x
>
>         10000 blocks
> but the 2bsd.tar.gz file has just the second file.
>
> The spensor_2bsd.tar.gz has a tar binary in it:
>
>     tar tvf spencer_2bsd.tar.gz | head
>     -rw-r--r--  0 0      0       24688 Feb 17  1980 tar
>     -rw-r--r--  0 0      10       3687 Feb 17  1980 tar.1
>     -rw-r--r--  0 0      10        456 Feb 17  1980 tar.ms <http://tar.ms>
>     -rw-r--r--  0 0      10      15216 Feb 17  1980 install.ms
>     <http://install.ms>
>
> if you are looking for that pre-built. If you are looking to create a 
> tape with tar on it to extract other tar tapes, you'd need to use a 
> variation on the maketape.pl <http://maketape.pl> with a block size of 
> 1 so the above dd will work on the target system...

This definitely makes sense. Thanks. This


-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF


[-- Attachment #2: Type: text/html, Size: 3012 bytes --]

  parent reply	other threads:[~2020-07-29  0:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 23:03 Will Senn
2020-07-29  0:09 ` Warner Losh
2020-07-29  0:19   ` Clem Cole
2020-07-29  0:45   ` Will Senn
2020-07-29  0:46   ` Will Senn [this message]
2020-07-29  0:21 ` Clem Cole
2020-07-29  9:50   ` [TUHS] [simh] " Johnny Billquist
2020-07-29 13:52     ` John Cowan
2020-07-29 14:30       ` Johnny Billquist
2020-08-11 23:41       ` Dave Horsfall
     [not found]     ` <5A12E0BB-4FFF-4C3E-B486-D4E852FAA97F@comcast.net>
2020-07-29 14:29       ` Johnny Billquist
2020-08-11 23:55         ` Dave Horsfall
2020-07-29 13:42   ` [TUHS] 2bsd tarball -> pdtar, with a side of uuslave John Gilmore
2020-07-29 15:40     ` Clem Cole
2020-07-29 19:34       ` Richard Salz
2020-07-29 19:42         ` Warner Losh

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=a43bafab-1d20-d912-a83e-d7e3cc9d051e@gmail.com \
    --to=will.senn@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).