Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Steve Jenkin <sjenkin@canb.auug.org.au>
To: COFF <coff@tuhs.org>
Subject: [COFF] Re: Shell script advice: using 'dd' to write multiple media
Date: Tue, 27 Jun 2023 13:47:22 +1000	[thread overview]
Message-ID: <5C26BE4B-2E6C-4E02-9536-3EA774FB6B47@canb.auug.org.au> (raw)
In-Reply-To: <950C04A3-3D30-48ED-B956-74EDB7C910E3@iitbombay.org>



> On 27 Jun 2023, at 09:44, Bakul Shah <bakul@iitbombay.org> wrote:
> 
> f 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).

Bakul,

Thanks for the note.
I’d not heard of “makeit” before, will go hunt it down.

1. this was the 1980’s, space was always an issue :)

2. There are many cases where you’ve only got a 
    stream. This distributions were the first
    time I hit this problem type.

3. The distributions were a compressed tar or cpio
     of a directory structure, to be exploded at destination.
     There wasn’t a need to fit files onto media.

cheers
steve j

--
Steve Jenkin, IT Systems and Design 
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA

mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin


  reply	other threads:[~2023-06-27  3:47 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 [this message]
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=5C26BE4B-2E6C-4E02-9536-3EA774FB6B47@canb.auug.org.au \
    --to=sjenkin@canb.auug.org.au \
    --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).