From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25981 invoked from network); 27 Jun 2023 00:25:22 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 27 Jun 2023 00:25:22 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id AE85D402CE; Tue, 27 Jun 2023 10:25:20 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuhs.org; s=dkim; t=1687825520; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post; bh=bq493Hg83FZDW000VyxwyXIVK72VO50QPtfSEy4Az3Y=; b=1ZHT5rIhriJk7y57IV7VarZzkNJPywDBmQuadvMihGL+l4rTSDtyheP8fdH8E2uPNHrGZG pGuxnWDOc4YlxwhgOpbXXm34Wy8Kg2QrgvgI/q7poDdXUMok0VDCn7//Qp5vqfe0PatMuY Vz20P4aLx8DJsktuNnrHHQd+KEzvXHw= Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch [185.70.40.137]) by minnie.tuhs.org (Postfix) with ESMTPS id A72A140151 for ; Tue, 27 Jun 2023 10:25:16 +1000 (AEST) Date: Tue, 27 Jun 2023 00:25:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1687825514; x=1688084714; bh=bq493Hg83FZDW000VyxwyXIVK72VO50QPtfSEy4Az3Y=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=Jb/nwwX/1+nwB+jfGVf+AvfOGEoIZcarCQpFoh9iOzVSE8UqyN89ggQ/Rq9qe44ss yf39dSDAGid9fHqrmffCz555GvaZz9HfU/fEaIQu2noQ7izX8i1mU+MFuORNcLZGB+ WpOPqBn9kyMqscaDZSHcheNyoO3mLob2JHU4LSgtxDVDd9VGP+jeIfwCC2Vsx3Uof3 pRLBs78hQ7GS0aqFzQ91sAn5OkVvthT9kw09ryWTEJpbHpWfi/ruM7SMCr7hYwZU9L 3BKaSjoL46YPMFFmlI6cagQ4Y6ygX4YJW+kRKkBDek4nUHpMBlbs2bgety3t7QjMwq KMR54tP6CILcA== To: steve jenkin Message-ID: In-Reply-To: References: Feedback-ID: 35591162:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID-Hash: ZMBHW33EWJ2O4F62G2DXAPXHNR23V375 X-Message-ID-Hash: ZMBHW33EWJ2O4F62G2DXAPXHNR23V375 X-MailFrom: segaloco@protonmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: COFF X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [COFF] Re: Shell script advice: using 'dd' to write multiple media List-Id: Computer Old Farts Forum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: segaloco via COFF Reply-To: segaloco > There was a =E2=80=98create the distro=E2=80=99 step of the pipeline whic= h gathered the input, > followed by a loop that used =E2=80=98dd=E2=80=99 to block the stream int= o media-sized parts. If you were taking a stream and breaking it up arbitrarily with dd, does th= at imply that filesystem data defining the contents were isolated to the fi= rst 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 individ= ual volume? Granted, I don't have a lot of experience in this area, so I c= ould be comparing apples to your oranges for all I know. - Matt G.