The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Riley <paul@rileyriot.com>
To: Clem Cole <clemc@ccc.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 06:45:07 +0800	[thread overview]
Message-ID: <CAD05_j2nL6vHY=ZdnSm5_pQ1_i4SH7xP9imMoX5jhx_Y3wYi0w@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PpiYOHW8m=Pg0LgUifEV1iZ46z4ZUVrqAE8nFBqoMAqQ@mail.gmail.com>

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

Clem,

Thanks for your help. You’ve correctly interpreted my question.

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.

The target system is LSX, a cut-down version of V6 designed to run on the
LSI-11. 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.

Paul

On Mon, 1 Jun 2020 at 9:05 pm, Clem Cole <clemc@ccc.com> wrote:

>
>
> On Mon, Jun 1, 2020 at 6:19 AM Paul Riley <paul@rileyriot.com> wrote:
>
>> Is there a Windows or Linux utility to create a disk image in any of the
>> above formats, from a local folder tree?
>>
> What I think you are asking, is there a utility for a modern OS that will
> walk a local folder tree on my OS and create a new file whose structure is
> that of the file system for OS <insert yours here>.
>
> The issue is not the device as much as the OS and disk file layout.    As
> far as UNIX (or simh at the OS level) is concerned, the disk is just a
> linear array of bytes, addressed by blocks.  The physical format is not
> seen by UNIX.
>
> There are numerious utilities, as well as 'foreign file systems' that are
> available.   For instance, many Unix's can write RT-11 and MS-DOS format
> with standard utilities.   It really depends the OS.  That said,
> if the target OS is modern enough to support NFS or Samba, the easiest way
> might be export the file system from local system, and then running a
> simulated OS, 'mount' the file system.
>
-- 
*Paul Riley*

Mo: +86 186 8227 8332
Email: paul@rileyriot.com

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

  reply	other threads:[~2020-06-01 22:45 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 [this message]
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
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='CAD05_j2nL6vHY=ZdnSm5_pQ1_i4SH7xP9imMoX5jhx_Y3wYi0w@mail.gmail.com' \
    --to=paul@rileyriot.com \
    --cc=clemc@ccc.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).