From: Adam Thornton <athornton@gmail.com>
To: Paul Winalski <paul.winalski@gmail.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 12:08:23 -0700 [thread overview]
Message-ID: <3A17BE73-777A-4CF2-8D55-A5C802FC767D@gmail.com> (raw)
In-Reply-To: <CABH=_VQnSnRASpeX84fwAosGyYi=zzxc4_o8KD9JYNoFWekCow@mail.gmail.com>
> On Jun 2, 2020, at 11:59 AM, Paul Winalski <paul.winalski@gmail.com> wrote:
>
> On 6/2/20, 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.
>
> At least they all supported fixed-length sectors. Was there ever a
> Unix implementation that supported IBM-style CKD disk devices?
If you count Linux, sure, Linux for the S/390 and zSeries.
If you don’t…well, for one brief shining moment before IBM squeezed too hard on the price and Oracle bought Sun instead, there was an OpenSolaris port to the zSeries, and it did support 3390 type devices.
I may have had something to do with that latter device driver.
Adam
next prev parent reply other threads:[~2020-06-02 19:08 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
2020-06-02 18:59 ` Paul Winalski
2020-06-02 19:08 ` Adam Thornton [this message]
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=3A17BE73-777A-4CF2-8D55-A5C802FC767D@gmail.com \
--to=athornton@gmail.com \
--cc=paul.winalski@gmail.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).