Hi, > > Because our discussion stalled, i did not publish the enhancements > > of libisofs API and xorriso CLI with the recent release 1.3.6.
> That's really sad! > It would have been easier for me, if you would have added them, even > if they were not perfect. Ah no. It's a tiny bit inconvenient. You may either test with xorriso-1.3.5 or enable it by macro in 1.3.6 and 1.3.7. Withholding the API and CLI is much better than releasing them in incomplete state, and having to create new ones after testing. We would need to prod debian-cd for upgrading xorriso, anyway. It is still on 1 year old xorriso-1.2.6 with its known GPT CRC bug. > > So if i get a definition of "ipl_entry" at byte 248 to 251, > It seems, that ipl_entry can be calculated like this: > (see lib/elf32.c or lib/elf64:) > [...] > http://mkhppa3.esiee.fr/ I will use the netinst image for practicing. The command line looks truncated: HP-PA cmdline : 0/vmlinux initrd=0/ramdisk panic_timeout=60 panic=-1 debian -installer/allow_unauthenticated=true mirror/http/hostname=debian-p It seems you need the header version 5. :)) Regrettably there is 0x00000000 at byte 248, where i hoped for an example of ipl_entry. Can you tell me the correct value for the bootloader file in the ISO ? So i have a test for my own computation. > load the elf-header of the Linux kernel (vmlinux or vmlinux64), Kernel ? Doesn't it belong to the "bootloader file" at ipl_adr (byte 240 to 243 in my cheat sheet) ? At least that's what i understand from function write_bootloader() in palo.git/tree/palo/palo.c . I.e. in your debian-7.0-hppa-NETINST-1.iso HP-PA bootloader : 159295488 45056 /install/iplboot If it belongs to a kernel: to which one of both ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
