The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Riley <paul@rileyriot.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 09:52:44 -0400	[thread overview]
Message-ID: <CAC20D2MdxxoNONNbGvQABQfSktLEuoWtfWGS+ZfM35-JK2JSsg@mail.gmail.com> (raw)
In-Reply-To: <CAD05_j2nL6vHY=ZdnSm5_pQ1_i4SH7xP9imMoX5jhx_Y3wYi0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]

On Mon, Jun 1, 2020 at 6:45 PM Paul Riley <paul@rileyriot.com> wrote:

> Is the disk image independent from the disk hardware? I’d assume that
> different disks may have different block sizes etc, so the disk type may be
> important.
>
A reasonable thought, but no, other than efficiency.  It's just an array of
bytes exposed to the OS.

The good news is that all the DEC systems used 512 byte fixed blocks
(Nothing like the funky Prime, Apollo or Alto tricks of putting some of the
file system metadata into the physical disk format -- if you ever wondered
why some of the original SCSI controllers supported a 1072 byte block size
- it was for Domain/Aegis - 1024 block + 48 byte meta data].



>
> The target system is LSX, a cut-down version of V6 designed to run on the
> LSI-11.
>
Everything should be able to be simulated using is 512-byte blocks.




> There are very few system utilities in the standard build (no mount for
> example). The second floppy is permanently mounted at boot time. I’m
> interested in making source file floppies on my modern system to use on the
> LSX, so I want to be able to create an image file from a source folder tree.
>

You'll have to check the docs, but I thought Heinz supported the RK05
[RKV11 controller].  That will give you 2.5M of 'raw' disk blocks, instead
of floppy.  Open it raw, and use it like mag tape.   If you don't have a
coming format, you can create something and then use dd(1) on the LSI-11
from the RKV11 -- a little clumsy but as a bootstrap, it should work fine.
The RL11 and RK711 controllers (RL01/02, RK07 disk) came later to the
PDP-11 (post 11/34 and 11/60). I think there was an RLV1[12] at some point,
but I don't think DEC even made an RKV71[12] -- however, I'm not up on
late-generation PDP-11 lore and they would have been much later than LSX so
driver support is doubtful.

Good luck,
Clem

[-- Attachment #2: Type: text/html, Size: 3577 bytes --]

  parent reply	other threads:[~2020-06-02 13:53 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 [this message]
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
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=CAC20D2MdxxoNONNbGvQABQfSktLEuoWtfWGS+ZfM35-JK2JSsg@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=paul@rileyriot.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).