From: Clem Cole <clemc@ccc.com>
To: Ronald Natalie <ron@ronnatalie.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] DEC RL01/RL02 RX01/RX02 Disk Image Creator
Date: Tue, 2 Jun 2020 14:08:36 -0400 [thread overview]
Message-ID: <CAC20D2MkFcykqhA=K+Wr7Wkwg4wwNg=UsMSamGgvAn4_L4z+Yg@mail.gmail.com> (raw)
In-Reply-To: <D5A39465-802B-4AE2-92DE-84D4BE27CB61@ronnatalie.com>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
On Tue, Jun 2, 2020 at 11:44 AM Ronald Natalie <ron@ronnatalie.com> wrote:
> Except on the RX’s. 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=sync to fill
any write buffer to a complete multiple of 512.
[-- Attachment #2: Type: text/html, Size: 1715 bytes --]
next prev parent reply other threads:[~2020-06-02 18:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 10:18 Paul Riley
2020-06-01 13:01 ` Ronald Natalie
2020-06-01 22:35 ` Paul Riley
2020-06-01 13:04 ` Clem Cole
2020-06-01 22:45 ` Paul Riley
2020-06-01 23:59 ` Ronald Natalie
2020-06-02 4:57 ` Paul Riley
2020-06-02 13:31 ` Clem Cole
2020-06-02 13:52 ` Clem Cole
2020-06-02 15:44 ` Ronald Natalie
2020-06-02 16:26 ` Warner Losh
2020-06-02 18:08 ` Clem Cole [this message]
2020-06-02 18:59 ` Paul Winalski
2020-06-02 19:08 ` Adam Thornton
2020-06-01 15:04 Paul Ruizendaal
2020-06-01 22:54 ` Paul Riley
2020-06-01 15:18 Paul Ruizendaal
2020-06-02 0:14 Noel Chiappa
2020-06-02 1:26 ` Ronald Natalie
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='CAC20D2MkFcykqhA=K+Wr7Wkwg4wwNg=UsMSamGgvAn4_L4z+Yg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=ron@ronnatalie.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).