From: Ralph Corderoy <ralph@inputplus.co.uk>
To: coff@tuhs.org
Subject: [COFF] Re: Shell script advice: using 'dd' to write multiple media
Date: Tue, 27 Jun 2023 07:33:04 +0100 [thread overview]
Message-ID: <20230627063304.5E1ED220E5@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAP2nic33Y72qL3t=+t54tRzTwYGT4MhCz1qsg0cs5VaLg_f51Q@mail.gmail.com>
Hi Adam,
> My approach would have been to use "split" on the original file
I think it's already been said that the input is a stream and the chunks
should be written to the output media on the fly.
--
Cheers, Ralph.
next prev parent reply other threads:[~2023-06-27 6:33 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 ` [COFF] " Dave Horsfall
2023-06-26 23:44 ` 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 [this message]
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=20230627063304.5E1ED220E5@orac.inputplus.co.uk \
--to=ralph@inputplus.co.uk \
--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).