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=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 11310 invoked from network); 2 Jun 2020 18:09:26 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 2 Jun 2020 18:09:26 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 9FBF49CAD5; Wed, 3 Jun 2020 04:09:24 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 7A4D69CAD2; Wed, 3 Jun 2020 04:09:05 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="E/CWDgh3"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id CC2BF9CAD2; Wed, 3 Jun 2020 04:09:03 +1000 (AEST) Received: from mail-qk1-f177.google.com (mail-qk1-f177.google.com [209.85.222.177]) by minnie.tuhs.org (Postfix) with ESMTPS id 3DFA29C96B for ; Wed, 3 Jun 2020 04:09:03 +1000 (AEST) Received: by mail-qk1-f177.google.com with SMTP id f18so13499931qkh.1 for ; Tue, 02 Jun 2020 11:09:03 -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=1dxdIPq4xjpb2qLHIVq8TKP8S7RRPtOuG2GG5udtFRo=; b=E/CWDgh3BbEMpNbwgPbUy6Miq7Ttazz0Ho0R6AAuGjjhkVq+VjZGZ3dOmk0mmEq5zC zaJFOp6b2EbVtVSu6Ph4cX/AW1fQTBQAkllNE9hkaFUZHua1AogqZAZqYw94dcHDUXJO J50yFXnMh1wMTgzXtfbw4eeTMbLG6QFs9vH44= 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=1dxdIPq4xjpb2qLHIVq8TKP8S7RRPtOuG2GG5udtFRo=; b=OkBU4svOHuBipMWjZ4x9Evpf3QWJNvhbTQrTY7Hz5AZhidbZRZkV0ij+Ajte/auYBY ck6vUb4FVRLhsWFJTY1cCfmPUgpM7N6fItD7bQyeqKo84E5Ea9VEwMq61jYK+xwxjVUU Yjm16JsDNObidyMxVzqPTDLarGo5/35eHPm8JEdJjdSWmY5T1jPhQ1zUmuYv0bX56F2e v9SVxyRpola81CXVVjevvHgaMD4/JPu8DWjBXnMTtBQrsL6NQK5VL6XuHxg3ubnme4Wt jkKLu4g/BJkzhFJxhO2eaukxRRGUIv0olGuQUXO96uumTHeS/KpT6psnb6FAbTQF9vlR y56w== X-Gm-Message-State: AOAM531rorUrQPV736Ot5MPOc5WJhl+n/h6kaLMX8erFebT6YQrwcOGp jvAh3Wkd/w48bwBH4dyj6k4LvMAnaalc+8kK7KyU+j1b X-Google-Smtp-Source: ABdhPJwXJCStO3fkWvwc3Iy39KJRykfwLov7MI1vLllil0zbwU/5MxNIOcSabVx8MH7HrcrUm5Takvu6s2y0IZJF070= X-Received: by 2002:a37:445:: with SMTP id 66mr26841682qke.146.1591121342357; Tue, 02 Jun 2020 11:09:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Tue, 2 Jun 2020 14:08:36 -0400 Message-ID: To: Ronald Natalie Content-Type: multipart/alternative; boundary="00000000000067fbb205a71dce2e" Subject: Re: [TUHS] DEC RL01/RL02 RX01/RX02 Disk Image Creator 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" --00000000000067fbb205a71dce2e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 2, 2020 at 11:44 AM Ronald Natalie wrote: > Except on the RX=E2=80=99s. The RX01 was 128 byte sectors and the later= ones 256 > and a odd interleaving strategy. However, the boot block and the rest = of > the file systems (both UNIX and RT at least) just aggregated the smaller > (logical) sectors together to make a 512 byte one. > Indeed, I was less than precise -- the key is that the SW treats them everything as being in 512 byte 'hunks' no matter the underlying physical formatting/interleaving actually is. The point is that if you Paul is trying to move data from the two systems, just treat the device as a serial byte stream of 512 byte blocks on both sides and you you be fine. That means if using dd, add conv=3Dsync to fil= l any write buffer to a complete multiple of 512. --00000000000067fbb205a71dce2e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Tue, Jun 2, 2020 at 11:44= AM Ronald Natalie <ron@ronnatalie= .com> wrote:
=
Except on the RX=E2=80=99s. = =C2=A0 The RX01 was 128 byte sectors and the later ones 256 and a odd inter= leaving strategy. =C2=A0 =C2=A0However, the boot block and the rest of the = file systems (both UNIX and RT at least) just aggregated the sma= ller (logical) sectors together to make a 512 byte one.
Indeed, I was less than precise -- the key is that the SW tre= ats them everything as being in 512 byte 'hunks' no matter the unde= rlying physical formatting/interleaving actually is.=C2=A0

The point is that if you Paul i= s trying to move data from the two systems, just treat the device as a seri= al byte stream of 512 byte blocks on both sides and you you be fine.=C2=A0 = =C2=A0That means if using dd, add conv=3Dsync to fill any write buffer to a= complete multiple of 512.=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
--00000000000067fbb205a71dce2e--