WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: isohybrid identification  (Read 3772 times)

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
isohybrid identification
« on: December 03, 2011, 12:17:25 AM »
Is there a command that will identify and report that an ISO has been produced via the syslinux isohybrid program?
   

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10700
Re: isohybrid identification
« Reply #1 on: December 04, 2011, 12:41:30 AM »
Not that I know of. File sees them as isos. "qemu -hda /path/to/iso" will tell the difference though ;)
The only barriers that can stop you are the ones you create yourself.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 10361
Re: isohybrid identification
« Reply #2 on: December 04, 2011, 08:11:59 AM »
Hi SamK
If I understand it correctly, an ISOhybrid basically just has a MBR added to it. Try the following:
Code: [Select]
hexdump -n 2 -s 510 -x -v filename.isoIf I'm correct, a standard ISO will return
Quote
00001fe    0000                                                       
0000200
while an ISOhybrid should return
Quote
00001fe    aa55                                                       
0000200
If that's the case, couple that with  grep  and you'll probably have what you are looking for.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: isohybrid identification
« Reply #3 on: December 05, 2011, 01:18:20 AM »
Hi Rich
Thanks for the idea.
If I understand it correctly, an ISOhybrid basically just has a MBR added to it.
I have looked a ISOhybrid only superficially.  On a test ISO I created the following was observed:

ISO - Pre ISOhybrid
Size reported by the ls command=29,126,656

ISO - Post ISOhybrid
Size reported by the ls command=29,360,128

Perhaps there is something else going on in addition to the MBR?


I have decided against pursuing ISOhybrid at this time. 

The principal reason for this is the way in which mnttool reports it.  The attached screen shot was taken on a machine booted from a USB flash drive created from Multicore v4.0.2 as the Core team produced it in ISOhybrid form.  The USB drive is sdc.  Both sdc and sdc1 are displayed by mnttool.  Either may be mounted independently, but both cannot be mounted concurrently.

For the purpose I had in mind, these may lead to confusion, hence a non ISOhybrid ISO will be used.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 10361
Re: isohybrid identification
« Reply #4 on: December 05, 2011, 05:22:36 AM »
Hi SamK
At least satisfy my curiosity and tell me if the hexdump command produced the expected results.
Quote
Perhaps there is something else going on in addition to the MBR?
I seem to remember reading something about one of the formats being able to boot from a partition
and the other requiring a drive.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: isohybrid identification
« Reply #5 on: December 05, 2011, 07:42:52 AM »
At least satisfy my curiosity and tell me if the hexdump command produced the expected results.
OK - the ISO was created as bootable...

Pre ISOhybrid
hexdump -n 2 -s 510 -x -v name.iso
00001fe    aa55                                                       
0000200


Post ISOhybrid
hexdump -n 2 -s 510 -x -v name.iso
00001fe    aa55                                                       
0000200


I seem to remember reading something about one of the formats being able to boot from a partition and the other requiring a drive.
I tried specifying the --entry parameter of isohybrid as 1 but the mnttool matter remains unchanged.

Time to move on...
   

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10700
Re: isohybrid identification
« Reply #6 on: December 13, 2011, 07:51:54 AM »
I got an email saying fdisk works to identify these - indeed, "fdisk -l tinycore.iso" works.

Thanks to Michael Shigorin.
The only barriers that can stop you are the ones you create yourself.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: isohybrid identification
« Reply #7 on: December 13, 2011, 10:25:49 AM »
I got an email saying fdisk works to identify these - indeed, "fdisk -l tinycore.iso" works.

Thanks to Michael Shigorin.
So it does - thanks it's handy to know.