From 7ad8dbf42ef166696fb6d422dcebf3158b3fe526 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Wed, 29 Sep 2010 08:55:30 +0000 Subject: [PATCH] Updated partition offset wike about GRUB experiment --- libisoburn/trunk/doc/partition_offset.wiki | 34 +++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/libisoburn/trunk/doc/partition_offset.wiki b/libisoburn/trunk/doc/partition_offset.wiki index 2056c324..a39b09ee 100644 --- a/libisoburn/trunk/doc/partition_offset.wiki +++ b/libisoburn/trunk/doc/partition_offset.wiki @@ -104,10 +104,42 @@ cutting off the first partition_offset blocks of 2 KB: -------------------------------------------------------------------------- +Another test was made with GRUB 2 by downloading +{{{ + bzr branch http://bzr.savannah.gnu.org/r/grub/trunk/grub +}}} + +Before building GRUB 2, the file +{{{ + util/grub-mkrescue.in +}}} +was edited to replace in the options of the xorriso command: +{{{ + --protective-msdos-label +}}} +by +{{{ + -partition_offset 16 -no-pad --no-emul-toc +}}} +Then GRUB 2 was built and installed. + +The resulting image from +{{{ + ./grub-mkrescue -o image.iso +}}} +was put onto USB stick. It passed the same tests on Debian +as above RIPLinux example. It boots to a GRUB prompt. + +Due to options -no-pad --no-emul-toc the image is about 300 kB smaller than +the image produced by original grub-mkrescue. Else it would have grown by +about 130 kB. + +-------------------------------------------------------------------------- + Open questions: - Shall the partition of an isohybrid image be marked bootable ? - Currently xorriso keeps the 0x80 mark of an eventually imported MBR +Currently xorriso keeps the 0x80 mark of an eventually imported MBR resp. the 0x80 mark which xorriso eventually sets by its own MBR preparations. - If not to be marked bootable: