From: segaloco via TUHS <tuhs@tuhs.org>
To: Arno Griffioen <arno.griffioen@ieee.org>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: [TUHS] Re: 5ESS UNIX RTR Reference Manual - Issue 10 (2001)
Date: Wed, 12 Jun 2024 16:30:48 +0000 [thread overview]
Message-ID: <c6krO4Bd40gpzokuqR3OBxKoJXzaAwVpv4FCQgejNlF1fzElZtROzDgH61E4mLYZcKsG4DR5M7b-JLd33XsMCHvJP-g0wCjk-OGsAQkYXIU=@protonmail.com> (raw)
In-Reply-To: <ZmlfScQiiHIMbV8l@ancienthardware.org>
On Wednesday, June 12th, 2024 at 1:41 AM, Arno Griffioen via TUHS <tuhs@tuhs.org> wrote:
> On Wed, Jun 12, 2024 at 09:12:04AM +0100, Ralph Corderoy wrote:
>
> > And then perhaps there's a command to extract the ISO from the bin/cue
> > files.
>
>
> 'bchunk' is one that does exactly that.
>
> Also 'fuseiso' allows mouting a BIN/CUE file/image as a regular filesystem to
> read the files if you just want to use them as-is.
>
> Bye, Arno.
bchunk is likewise my tool of choice for that sort of thing. I think what I'll go with is the bin/cue for completeness but also a zip of the contents composited together. Someone who specifically needs the disc image data can probably figure out bchunk and then an archive will be present in a form navigable through archive.org's interface with the composite pieces from each collection (i.e. a merge of the discs for a multi-disc set). That should hopefully satisfy various needs.
- Matt G.
prev parent reply other threads:[~2024-06-12 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 6:06 [TUHS] " segaloco via TUHS
2024-06-11 6:59 ` [TUHS] " Kevin Bowling
2024-06-12 1:37 ` Jim Carpenter
2024-06-12 3:34 ` segaloco via TUHS
2024-06-12 5:43 ` Andrew Warkentin
2024-06-12 7:01 ` Wesley Parish
2024-06-12 8:12 ` Ralph Corderoy
2024-06-12 8:41 ` Arno Griffioen via TUHS
2024-06-12 16:30 ` segaloco via TUHS [this message]
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='c6krO4Bd40gpzokuqR3OBxKoJXzaAwVpv4FCQgejNlF1fzElZtROzDgH61E4mLYZcKsG4DR5M7b-JLd33XsMCHvJP-g0wCjk-OGsAQkYXIU=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=arno.griffioen@ieee.org \
--cc=segaloco@protonmail.com \
/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).