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,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, NICE_REPLY_A,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30399 invoked from network); 20 Jul 2020 18:04:59 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 20 Jul 2020 18:04:59 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id F19689BA58; Tue, 21 Jul 2020 04:04:55 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id DC0349BA30; Tue, 21 Jul 2020 04:04:01 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="Do4tYs1I"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id AD9C99BA30; Tue, 21 Jul 2020 04:04:00 +1000 (AEST) Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com [209.85.210.42]) by minnie.tuhs.org (Postfix) with ESMTPS id 2BBD89BA2A for ; Tue, 21 Jul 2020 04:04:00 +1000 (AEST) Received: by mail-ot1-f42.google.com with SMTP id d4so12946300otk.2 for ; Mon, 20 Jul 2020 11:04:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=FeNTslWA71m7MrW+VfFeSgwZFslVoddMo0T4ralK1UE=; b=Do4tYs1IQjOCQxMVzdDQIGtysQB0uRRG7dKSEwiWYx7JTgJnerdDH949LQ4TkL5tUk wlvSAMfIxaUeJ6RAbHKCvZMffha4ywUzYYfrmW0nANWopOekch12/KhjO9xTTYgn1QK3 omK8OHdGJEEBQHWO4R/8l1nkn1sxEHSjHP/BpdNr/uyPuSYtxxpJacTinMbdNFldMz1h r8afMGq+ibSL1Zzj6F3yIgExhEtRMhemtjPcRUCW9SoDLIomxDM0AhVYoljzn122p36V n38l/GyoSg8WAjhMJZgCPHZF/yznf7QbGGQeQ/5rEenklge2lIMcZeSy4LuJKue1W9Na D+VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=FeNTslWA71m7MrW+VfFeSgwZFslVoddMo0T4ralK1UE=; b=B5HeT7AFaO8SkbKMvDJdVCUAi8uJM2ErNywRiJ7mM737lBm8K8C8UpsJyasW0uPUJy UnELW1qX+w480hdIKZtXXBXM0zGOL2uraa52crdiHdG6ZvYAv19na311q53/kiGENJT5 lOUSNUztbDXQQ+KBz6rMMR2iJ7hI2sa7vUkNr1Ma9DMVohKZFb6k4O0NdItvQu2LNJuE RDrCMf0PxrZVwZzLz3kjxGVpVCNm/ja6yjZ/4222NmsxLW46zcQunavwr8/kObMMjEVq QgsT/pfCnTrk4cUue2mXqYIhI74C2xYr7QpoVqldeET4HhzLenx+HhbGvqkzxXDlHB6E RtWw== X-Gm-Message-State: AOAM533sYBw2jBgmbdJHnEBSFCBczywWiP8qG6a1KgK/jyZjghuY8L5S ttoAW+IE9hbFTZdB/M83E8svD6Jpt88= X-Google-Smtp-Source: ABdhPJwqGE/umVuiQaC2zwVcgef1SeOO+4lp98Jey4h+9dvfWN/UZmsbkOQK8mtWF7Gs5BlzyXWD0w== X-Received: by 2002:a05:6830:151:: with SMTP id j17mr20194966otp.142.1595268238947; Mon, 20 Jul 2020 11:03:58 -0700 (PDT) Received: from terra.local (99-139-148-170.lightspeed.rcsntx.sbcglobal.net. [99.139.148.170]) by smtp.gmail.com with ESMTPSA id f187sm4204512oig.12.2020.07.20.11.03.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 20 Jul 2020 11:03:58 -0700 (PDT) To: Warner Losh References: <327c5b98-c48f-7855-0503-9c0f503af09c@gmail.com> From: Will Senn Message-ID: <2928e03c-8d02-6a15-1f21-dfbf576633ea@gmail.com> Date: Mon, 20 Jul 2020 13:03:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------4C764FB4987D90DE374D80D3" Content-Language: en-US Subject: Re: [TUHS] 211BSD Version in the Unix Archive 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" This is a multi-part message in MIME format. --------------4C764FB4987D90DE374D80D3 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 7/20/20 12:49 PM, Warner Losh wrote: > > You should look at the canonical tuhs archive at > https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/ I'll do that. > So far as I can figure out (and I'm a little bit fuzzy around the > edges), this appears to be patch level 431, at least according to > https://tuhs.v6shell.org/UnixArchiveMirror/Distributions/UCB/2.11BSD/VERSION. > I have a number of questions that hopefully, someone can shed some > light on: > > > > 1. Is it really pl 431? > > > Yes.  It is. Excellent. Thanks for the confirmation. > 2. How can I tell? > > > VERSION is always updated, so it is. If you are in doubt, you can look > at the patch files that's at > https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/Patches/ and > they all update VERSION. Got it. > 3. Is it the latest tape image available (I've seen plenty of disk > images, but those are already installed)? > > > Yes. Well, almost. > https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD_patch457/ has a > tape that's updated to 457, lacking only the last 12 changes. A most > current tape hasn't been regenerated, at least in the archives. A > quick search of github shows there's a few PiDP-11 oriented versions > but I've not looked closely at them. When folks 'regenerate' the tape, is it simply a matter of writing to the tape device from the patched disk inside the 211BSD instance or are there some arcane activities involved? > 4. Is there a howto bring it up to the next patch level document > lying around somewhere? > > > There's two or three efforts to create shell scripts to apply the > patches. I've not looked closely at them all yet... > > I've seen Warner's work on going the other direction and that's > fascinating in it's own right, but I'd like to see about patching > up to latest > > When my work is done, there will be a github repo that has all the > changes applied, one at a time which can be used to generate context > diffs or something else that can be pushed to the PDP-11s that can be > updated. Nice. You said something like this the other day, but at the time, I didn't quite get how relevant it would be. Now that I understand what you're talking about, it sounds great. Will -- GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF --------------4C764FB4987D90DE374D80D3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 7/20/20 12:49 PM, Warner Losh wrote:

You should look at the canonical tuhs archive at https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/
I'll do that.

 
So far as I can figure out (and I'm a little bit fuzzy around the edges), this appears to be patch level 431, at least according to https://tuhs.v6shell.org/UnixArchiveMirror/Distributions/UCB/2.11BSD/VERSION. I have a number of questions that hopefully, someone can shed some light on:


1. Is it really pl 431?

Yes.  It is.
Excellent. Thanks for the confirmation.

 
2. How can I tell?

VERSION is always updated, so it is. If you are in doubt, you can look at the patch files that's at https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD/Patches/ and they all update VERSION.

Got it.

 
3. Is it the latest tape image available (I've seen plenty of disk images, but those are already installed)?

Yes. Well, almost. https://www.tuhs.org/Archive/Distributions/UCB/2.11BSD_patch457/ has a tape that's updated to 457, lacking only the last 12 changes. A most current tape hasn't been regenerated, at least in the archives. A quick search of github shows there's a few PiDP-11 oriented versions but I've not looked closely at them.
When folks 'regenerate' the tape, is it simply a matter of writing to the tape device from the patched disk inside the 211BSD instance or are there some arcane activities involved?

 
4. Is there a howto bring it up to the next patch level document lying around somewhere?

There's two or three efforts to create shell scripts to apply the patches. I've not looked closely at them all yet...
 
I've seen Warner's work on going the other direction and that's fascinating in it's own right, but I'd like to see about patching up to latest
 
When my work is done, there will be a github repo that has all the changes applied, one at a time which can be used to generate context diffs or something else that can be pushed to the PDP-11s that can be updated.
Nice. You said something like this the other day, but at the time, I didn't quite get how relevant it would be. Now that I understand what you're talking about, it sounds great.

Will


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