From: segaloco via COFF <coff@tuhs.org>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Re: Shell script advice: using 'dd' to write multiple media
Date: Tue, 27 Jun 2023 00:25:10 +0000 [thread overview]
Message-ID: <EXknJVcxk0KaYG8KiBGQtDSTGqr6jVut4JiG78HOi1KOWGfDAY2Oa1bF8KwvO8nFVRdcbjcxa3_1krpL3kmqIiv_MiUNR8gltbG1lIHZd34=@protonmail.com> (raw)
In-Reply-To: <D0AEA7F2-9981-4AAF-8F52-3FCF79089394@canb.auug.org.au>
> 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.
If you were taking a stream and breaking it up arbitrarily with dd, does that imply that filesystem data defining the contents were isolated to the first volume (or however many it took to describe the contents)? Or is there something you could do with dd in that circumstance to amount to more than just bytes in bytes out to prop up a filesystem superblock on each individual volume? Granted, I don't have a lot of experience in this area, so I could be comparing apples to your oranges for all I know.
- Matt G.
next prev parent reply other threads:[~2023-06-27 0:25 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 [this message]
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='EXknJVcxk0KaYG8KiBGQtDSTGqr6jVut4JiG78HOi1KOWGfDAY2Oa1bF8KwvO8nFVRdcbjcxa3_1krpL3kmqIiv_MiUNR8gltbG1lIHZd34=@protonmail.com' \
--to=coff@tuhs.org \
--cc=segaloco@protonmail.com \
--cc=sjenkin@canb.auug.org.au \
/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).