Re: arm64 and isohybrid
On Wed, Feb 04, 2015 at 03:12:30PM +0000, Steve McIntyre wrote:
>On Sat, Jan 31, 2015 at 10:24:17AM +0000, Steve McIntyre wrote:
>>On Thu, Jan 29, 2015 at 11:41:57AM +0100, Thomas Schmitt wrote:
>>>After reading its /.disk/mkisofs, i re-pack it by
>>> # A dummy MBR template as substitute for isohdpfx.bin
>>> dd if=/dev/zero bs=432 count=1 of=null.mbr
>>> mount -o loop debian-jessie-DI-b2-arm64-netinst.iso /mnt/iso
>>> xorriso -as mkisofs \
>>> -V 'Debian jessie-DI-b2 arm64 1' \
>>> -r -o test.iso -J -joliet-long -cache-inodes \
>>> -isohybrid-mbr null.mbr \
>>> -e boot/grub/efi.img -no-emul-boot -isohybrid-gpt-basdat \
>>> all Jigdo options
>>> -eltorito-alt-boot is a separator which is needed only if
>>> already a boot image was defined by -b, -e,
>>> or alike
>>> -isohybrid-gpt-basdat works only if -isohybrid-mbr is present
>>> -isohybrid-mbr gets as input the dummy MBR template. So SYSLINUX
>>> is not needed.
>This may look valid, but gdisk and other code I've used don't cope
>well with the PMBR being broken. I can mount partition 1 fine for the
>normal ISO contents, but partition 2 seems broken and I can't mount
>it. Maybe an offset bug(?), or things are being too confused by the
>GPT-MBR disconnect here.
In fact, no. If I specify "-c isolinux/boot.cat" too, that fixes
it. efi.img is being modified otherwise, it seems?
Steve McIntyre, Cambridge, UK. firstname.lastname@example.org
Is there anybody out there?