>Hi. On install CD of Linux distros, we find out some image >files for creating boot disk. For example, there are three >image files in CD of Red Hat Linux 7.1. > >-rw-r--r-- 2 0 0 1474560 Apr 09 03:37 boot.img >-rw-r--r-- 2 0 0 1474560 Apr 09 03:37 bootnet.img >-rw-r--r-- 2 0 0 1474560 Apr 09 03:37 pcmcia.img > >When we/they make ISO9660 image file using ``mkisofs'', we >use ``-b '' and ``-c'' options with ``mkisofs'' for bootable >CDs. Well, I hava one quiestion. How can I find what the >image file was uesed on making ISO9660 image file? > >That is, when I look at > >-r--r--r-- 1 0 0 2048 Apr 09 04:08 boot.cat > >in bootable CDs, that ``boot.cat'' was linked with boot.img?, >bootnet.img?, pcmcia.img?, how can I find out?
CDs that are bootable on PCs are defined in the 'El Torito' standard - they d The 'El Torito' standard (used by bootable CDs on x86 PCs) doesn't use (or care about) file names, but uses the location (extent) of the file on the CD. The boot catalog file contains the extent(s) of the bootable file(s) - the El Torito spec (try http://www.cdrfaq.org/) will detail the format of this file. The mkisofs source files eltorito.c amd iso9660.h contain details on how mkisofs creates bootable CDs. You can find the extent of the first bootable file on i386 Linux by doing something like: od -d -j 40 boot.cat The first integer is the starting extent of the first bootable file. Then run: isoinfo -i /mnt/cdrom -R -l and look for file name that corresponds to that extent (given between '[ ]'). James Pearson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
