From: Dave Horsfall <dave@horsfall.org>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: Shell script advice: using 'dd' to write multiple media
Date: Tue, 27 Jun 2023 09:21:39 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2306270916210.50080@aneurin.horsfall.org> (raw)
In-Reply-To: <D0AEA7F2-9981-4AAF-8F52-3FCF79089394@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Tue, 27 Jun 2023, steve jenkin wrote:
> In the mid 1980’s I worked for a small Australian outfit that did
> “Unix”.
Neology? Softway?
> One of the things we did was distributing software, which required
> writing to many media.
[...]
> There was a ‘create the distro’ step of the pipeline which gathered the
> input, followed by a loop that used ‘dd’ to block the stream into
> media-sized parts.
Sounds like you want to put "dd" into a loop, driven by the block size and
the media size, then using the "iseek" option on the input file to burrow
through it.
I would use "expr" for the arithmetic because I've never bothered to
learn the Bash syntax :-)
Or have I missed something?
-- Dave
next prev parent reply other threads:[~2023-06-26 23:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:09 [COFF] " steve jenkin
2023-06-26 23:21 ` Dave Horsfall [this message]
2023-06-26 23:44 ` [COFF] " steve jenkin
2023-06-27 21:01 ` Dave Horsfall
2023-06-26 23:32 ` Clem Cole
2023-06-27 4:43 ` Steve Jenkin
2023-06-26 23:44 ` Bakul Shah
2023-06-27 3:47 ` Steve Jenkin
2023-06-27 15:50 ` Steffen Nurpmeso
2023-06-27 16:07 ` Steffen Nurpmeso
2023-06-27 0:25 ` segaloco via COFF
2023-06-27 6:23 ` Ralph Corderoy
2023-06-27 6:28 ` Adam Thornton
2023-06-27 6:33 ` Ralph Corderoy
2023-06-27 7:53 ` steve jenkin
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=alpine.BSF.2.21.9999.2306270916210.50080@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=coff@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).