creating a bootable iso for raid BIOS flash

[Polytropon]

On Sun, 8 Jan 2012 01:11:30 +0100 (CET), Marco Beishuizen wrote:
> On Sun, 8 Jan 2012, the wise Polytropon wrote:
> 
> > If this is depending on the name "[BOOT]", there are
> > two ways to deal with special characters in file names,
> > if you need to specify them on the command line:
> >
> > a) use escape sequences:
> > 	-b \[BOOT\]/Bootable_HardDisk.img
> >
> > b) use quoting:
> > 	-b "[BOOT]/Bootable_HardDisk.img"
> 
> I used escape sequences and that works. The "no match" error is gone.

By using [ and ], the shell tries to expand a regular
expression where [BOOT] means "one of the letters B,
O, or T; neither B/Bootable_HardDisk.img, O/Bootable_HardDisk.img
or T/Bootable_HardDisk.img is present, so the shell
fully correctly replies with "no match".

(In a similar fashion, * and ? are interpreted by the
shell.)



> > Also read "man mkisofs" about the boot-related
> > options, especially -b, where
> >
> > 	If  the  boot image is not an image of a floppy, you need to add
> > 	one of the options: -hard-disk-boot or  -no-emul-boot.   If  the
> > 	system should not boot off the emulated disk, use -no-boot.
> >
> > is mentioned. Maybe consider using -G instead of -b?
> 
> I tried the -G option and removed the -hard-disk-boot option and now it 
> created an iso without errors. The size is still 9MB though. I looked 
> inside the original iso and the one generated by me but I really can't see 
> any differences.

Does this image boot successfully?

If you compare your ISO with the original one, file sizes
should be the same for all files; are they? A reason could
be that the original one contains some "metadata" that the
creating program (which will very probably _not_ be mkisofs
as you're using) may have stored there. Things like for
example an application ID, copyright information, media
name. Maybe the original program did use a different
"mechanism" to create the ISO?

You can easily add the file sizes inside the original
ISO and compare them to your sources (which should be
equal) and see where the difference comes from. I think
it will be some file system metadata (remember that the
ISO-9660 file system occupies "invisible" space within
the ISO file).




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...