Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.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: Mon, 26 Jun 2023 16:44:07 -0700	[thread overview]
Message-ID: <950C04A3-3D30-48ED-B956-74EDB7C910E3@iitbombay.org> (raw)
In-Reply-To: <D0AEA7F2-9981-4AAF-8F52-3FCF79089394@canb.auug.org.au>

On Jun 26, 2023, at 4:09 PM, steve jenkin <sjenkin@canb.auug.org.au> wrote:
> 
> 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 space is not an issue, you can use split(1) to divide
the input in N pieces and then use a separate loop to copy
them to the media. If you want to stream the distribution
on stdin but still copy to N disks or whatever, you can
write a simple C program that will prompt the user to switch
media, print out checksum etc. If you want to *not* split
files across media (and no file is greater than media size),
you can use makekit from Rich Salz's cshar (comp.sources.unix
Volume 15).

  parent reply	other threads:[~2023-06-26 23:44 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 [this message]
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=950C04A3-3D30-48ED-B956-74EDB7C910E3@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=coff@tuhs.org \
    --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).