[haiku-commits] Re: r35667 - in haiku/trunk/src/tools: . anyboot
- From: "Michael Lotz" <mmlr@xxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Sun, 28 Feb 2010 19:59:57 +0000
> Author: mmlr
> Date: 2010-02-28 19:51:16 +0100 (Sun, 28 Feb 2010)
> New Revision: 35667
> Changeset: http://dev.haiku-os.org/changeset/35667/haiku
>
> Added:
> haiku/trunk/src/tools/anyboot/
> haiku/trunk/src/tools/anyboot/Jamfile
> haiku/trunk/src/tools/anyboot/anyboot.cpp
> Modified:
> haiku/trunk/src/tools/Jamfile
> Log:
> Adding an "anyboot" buildtool that takes a chainloading MBR, a ISO CD
> boot image
> and a Haiku image and fuses everything to a hybrid MBR/ISO image.
> Since it
> contains a valid MBR, partition table and el-torito CD boot record
> such an image
> should be pretty universally bootable. It can be written to disks,
> USB sticks or
> CDs/DVDs. Since it has a partition table in place it is also possible
> that it
> helps with the non-booting USB sticks where the BIOS (wrongly) assumes
> a
> partition table.
Note that this makes CDs actually run from BFS + write_overlay instead
of ISO9660 + write_overlay + attribute_overlay (which has already been
prepared earlier). At first sight this should perform better, but some
preliminary tests I did back when I worked this stuff out showed the
opposite to be true. It's not too surprising considering that ISO9660
was basically designed for such media. Further testing / benchmarking
will have to be done to see if it is viable to use these images for
releases.
Regards
Michael
Other related posts:
