Re: xorriso and the "-md5 on" option
On Sat 21 Dec 2019 at 14:24:28 -0700, Charles Curley wrote:
> On Sat, 21 Dec 2019 20:34:42 +0000
> Brian <ad44@cityscape.co.uk> wrote:
>
>
> I trust you have already pulled in and used the checksum file(s) for the
> iso itself. If those fail to verify, there isn't much point in
> proceeding.
Indeed.
> > I am extracting files from a Debian ISO as follows:
> >
> > xorriso -osirrox on -md5 on -indev debian-10.2.0-i386-DVD-10.iso
> > -extract pool/main test/
>
> xorriso strikes me as a bit of overkill. I usually just mount the iso
> image and treat it as a read-only file system. But as long as it
> works for you... .
>
> The first thing I do after mounting it is verify the checksums in situ
> in the image. Something like:
>
> mount foo.iso /mnt
> cd /mnt
> shaXXXsum --q -c filename.shaXXXsums
>
>
> >
> > Will the files in test/ have the same md5sum as the ones in the ISO?
> > Obviously, I am looking to obtain uncorrupted files.
> >
> > What will the output show if there is a problem with extraction?
> >
>
> Each the output line for each file that fails will have the word FAIL
> in all caps. You can use the --quiet option (--q for short) to have the
> program spit out only problematic results.
Basically, I want to compare the MD5sum (or shaXXXsum) for each
file in the ISO with the MD5sum for each extracted file. Either
during extraction or afterwards.
--
Brian.
Reply to: