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,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 6924 invoked from network); 3 Aug 2023 23:15:04 -0000
Received: from minnie.tuhs.org (2600:3c01:e000:146::1)
  by inbox.vuxu.org with ESMTPUTF8; 3 Aug 2023 23:15:04 -0000
Received: from minnie.tuhs.org (localhost [IPv6:::1])
	by minnie.tuhs.org (Postfix) with ESMTP id 6C1434172C;
	Fri,  4 Aug 2023 09:14:59 +1000 (AEST)
Received: from mx2.mythic-beasts.com (mx2.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1])
	by minnie.tuhs.org (Postfix) with ESMTPS id 6597841721
	for <tuhs@tuhs.org>; Fri,  4 Aug 2023 09:14:51 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=quintile.net; s=mythic-beasts-k1; h=To:Subject:Date:From;
	bh=U8RqHCCw6A97eS9P3SG+ZKCo2S9jmVuPr4oJv77kEI0=; b=KsTF1YXnWf940dWMThUxyWpvX6
	5U5VNayNNnxyQKlc3/iJTn+M1Tof0yy/vUJj7U1VjBVJrQH0GQoeb9k/0uKVuCETW7g5tfMczErRJ
	AsEihzqU+Ej6VrNvkuczWsMT2tjgRM71QW+g4/rieAcj1vLhLKdEiPcaPjFCzyycMOEIh4SKvFy3/
	6CKLuMapLAzXeiyCn7D8uTxkxVCyytiUkVnoYUV+a4SQ04vaxhMOCVcxzStHFwhz3hcvmdwD3Nd+i
	aoB4rM5kiI2jWU7FCx539J7Vp0IlQIO9+i/41zl3+/Rt7YlQ4PQE//Gqp/76po7CY7qOd0W5ZjRLs
	mC7s7ceQ==;
Received: by mailhub-hex-d.mythic-beasts.com with esmtpsa  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <steve@quintile.net>)
	id 1qRhWr-003lVG-7K
	for tuhs@tuhs.org; Fri, 04 Aug 2023 00:14:49 +0100
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Steve Simon <steve@quintile.net>
Mime-Version: 1.0 (1.0)
Date: Fri, 4 Aug 2023 00:14:35 +0100
Message-Id: <1746F115-5095-497A-A477-2C69ECDB881D@quintile.net>
To: tuhs@tuhs.org
X-Mailer: iPhone Mail (20F75)
X-BlackCat-Spam-Score: 4
Message-ID-Hash: ZNSRWZPPHF3JLCJTQI3N24KGYVFPBMQD
X-Message-ID-Hash: ZNSRWZPPHF3JLCJTQI3N24KGYVFPBMQD
X-MailFrom: steve@quintile.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.6b1
Precedence: list
Subject: [TUHS] Re: Split addressing (I/D) space (inspired by the    death of the python... thread)
List-Id: The Unix Heritage Society mailing list <tuhs.tuhs.org>
Archived-At: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/message/ZNSRWZPPHF3JLCJTQI3N24KGYVFPBMQD/>
List-Archive: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/>
List-Help: <mailto:tuhs-request@tuhs.org?subject=help>
List-Owner: <mailto:tuhs-owner@tuhs.org>
List-Post: <mailto:tuhs@tuhs.org>
List-Subscribe: <mailto:tuhs-join@tuhs.org>
List-Unsubscribe: <mailto:tuhs-leave@tuhs.org>


not quite split i and d but i do have a memory of some code which could run i=
n three parts as overlays.

this could have been through exec=E2=80=99ing the next overlay with an appro=
priate argv and a pipe or file of data, or, perhaps there was some kernel su=
pport for overlays in early unix.

anyone seen evidence of this?

sadly i cannot remember where i saw it, i want to say it was a versatex prin=
ter driver but i am pretty sure that is rubbish.

-Steve