From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30195 invoked from network); 28 Jul 2020 13:52:06 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 28 Jul 2020 13:52:06 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 0E0AC9C8E4; Tue, 28 Jul 2020 23:52:04 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 501079C8E8; Tue, 28 Jul 2020 23:50:55 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="CyA0/0Mu"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id BF2B59C8E4; Tue, 28 Jul 2020 23:50:53 +1000 (AEST) Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) by minnie.tuhs.org (Postfix) with ESMTPS id AF1209C8E2 for ; Tue, 28 Jul 2020 23:50:52 +1000 (AEST) Received: by mail-qk1-f175.google.com with SMTP id g26so18688725qka.3 for ; Tue, 28 Jul 2020 06:50:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jainJG9oxSL4nCBhcGOymaoQ0pBgG52c5Eit5JynCd4=; b=CyA0/0MuAqyyuw+mIyrZjrzsprzGRHwP6gbuMhPVNBzUSeYJZcvvPn6WR8mewSL8tl QUe3DqG4zv0D+d+ipRHMGzrGc0GHQKoKiBKjK/uM9Jw/SuYGjpUWqIbWWlzsj2DVClcd LSWZLF3yAp7qyf2Grb/dC8w8VWBZO/qRA6pRE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jainJG9oxSL4nCBhcGOymaoQ0pBgG52c5Eit5JynCd4=; b=N4+vYyoi9fuqjfAxpZUJQbwoV3YrDudSCJFmo1DbC6S5+Q5fDUdYZRJ/3moxgiARRW dp2pH8KBXuIfwat4vMqp4lk9zST7kELudWXCwZ75EsLnzreiQOK12vCVUOateCRnUNs4 sgQ79APSlhMnqMWu/2pT3AZrv4aWU2d4x2EUByoGL8Gj25Zkgy/TnkfgZYHNcfU3h7cb NQjMcQeD9LR4VuoxWaD0/0ucsDZNmLy9rSAaYPpSELsYEg56Vw95h/Sjgrh0t6qYcVsN qsjqO8+hz2W487D0Ssj9/mzhy+arXGMveU+r2zOTp0Sqvq25FkTmz17mYclIKUDhLNbu 7ZTw== X-Gm-Message-State: AOAM532iisExTndUoBGl6YcDByUMZ4iepwnZPVfxsRBj2Ugdd5lI+FPy lEGj7+72+/NGHkHJ287PvgqJySLvt8LoZXpmlpt/tw== X-Google-Smtp-Source: ABdhPJztWcB2KV79O0zcY7vEK6GcQc4gnOJ2dFudZzo5uOQMhp+UNEhKKYDCXzn5UJPLS8GwMZ3Yg+79vubwTTR20XM= X-Received: by 2002:a37:7a01:: with SMTP id v1mr27449059qkc.146.1595944251707; Tue, 28 Jul 2020 06:50:51 -0700 (PDT) MIME-Version: 1.0 References: <7b892386-6856-6bb8-9d87-a628645ecf19@gmail.com> <5d2dd1bb-4c4e-6799-47f5-12faae521eb0@gmail.com> In-Reply-To: From: Clem Cole Date: Tue, 28 Jul 2020 09:50:25 -0400 Message-ID: To: Will Senn Content-Type: multipart/alternative; boundary="000000000000346a5f05ab80baf4" Subject: Re: [TUHS] v7 tar and 2bsd.tar X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000346a5f05ab80baf4 Content-Type: text/plain; charset="UTF-8" Glad it's working. We probably need to create Joy's tarball in the future with the same file ordering he used and get that the Warren. The trick is getting a v6tar that properly works. Maybe one thing we should do is write a tp format 'tape' with the v6tar binary on it and get that in the archives independently. When V7 came out, there was a way to create v6tar (which I suspect is somehow part of Joy's image). The issue is that some of the system calls changed in small but important ways. tar was a much better way to move files around than tp which is why it so quickly became the archive scheme in the Unix community. On Tue, Jul 28, 2020 at 9:38 AM Will Senn wrote: > After much travail, I found a post in some ancient Asian language > (Japanese) and was reminded of Wolfgang's enblock. I didn't bother to > translate, but just did the enblock: > > gunzip -d 2bsd.tar.gz > cat 2bsd.tar | enblock > 2bsd.tap > > I attached the result, et voila: > tar xv0 > tar: bin/ - cannot create > x bin/csh, 40412 bytes, 79 tape blocks > tar: bin/etc/ - cannot create > x bin/etc/htmp, 0 bytes, 0 tape blocks > x bin/etc/install, 81 bytes, 1 tape blocks > > The cannot create messages are filthy lies :). > > That brought it all back to me - just like when I built tar from tape > for v6... sheesh, why does it have to be so painfully difficult to > remember these tricky bits?! > > Anyhow, afterward, I went back, did the translation from Japanese to > English (or google did), and it was good stuff about how to apply > 2bsd.tar to v6: > > > https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Forumin.blogspot.com%2F2014%2F06%2Funix-and-2bsd-on-pdp11simh-2.html > > Thanks for the help and patience. > > Will > > -- > GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF > > --000000000000346a5f05ab80baf4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Glad it's working.=C2=A0 =C2=A0We probably need to = create Joy's tarball in the future with the same file ordering he used = and get that the Warren.=C2=A0 The trick is getting a v6tar that properly w= orks.=C2=A0 =C2=A0Maybe one thing we should do is write a tp format 'ta= pe' with the v6tar binary on it and get that in the archives independen= tly.

When V7 came out, there was a way to create v6tar= (which I suspect is somehow part of Joy's image).=C2=A0 The issue is t= hat some of the system calls changed in small but important ways.=C2=A0 =C2= =A0tar was a much better way to move files around than tp which is why it s= o quickly became the archive scheme in the Unix community.=C2=A0

On Tu= e, Jul 28, 2020 at 9:38 AM Will Senn <will.senn@gmail.com> wrote:
After much travail, I found a post in some ancient = Asian language
(Japanese) and was reminded of Wolfgang's enblock. I didn't bother = to
translate, but just did the enblock:

gunzip -d 2bsd.tar.gz
cat 2bsd.tar | enblock > 2bsd.tap

I attached the result, et voila:
tar xv0
tar: bin/ - cannot create
x bin/csh, 40412 bytes, 79 tape blocks
tar: bin/etc/ - cannot create
x bin/etc/htmp, 0 bytes, 0 tape blocks
x bin/etc/install, 81 bytes, 1 tape blocks

The cannot create messages are filthy lies :).

That brought it all back to me - just like when I built tar from tape
for v6... sheesh, why does it have to be so painfully difficult to
remember these tricky bits?!

Anyhow, afterward, I went back, did the translation from Japanese to
English (or google did), and it was good stuff about how to apply
2bsd.tar to v6:

https://translate.google.= com/translate?sl=3Dauto&tl=3Den&u=3Dhttps%3A%2F%2Forumin.blogspot.c= om%2F2014%2F06%2Funix-and-2bsd-on-pdp11simh-2.html

Thanks for the help and patience.

Will

--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462=C2=A0 7D45 3EAA 5B6D A982 BAAF
--000000000000346a5f05ab80baf4--