Hi Thomas > looking at your description of ipl_entry computation > - after midnight - makes me search for alternatives.
Mee too :-) Ok, I just looked at the palo source code again. ipl_entry is the relative entry point into the assembly code of the iplboot bootloader code. Because of how palo is built, it ensures, that the entry point is always "zero". That's the reason why genisoimage just kept the zero-intialized value for ipl_entry and didn't changed it. My proposal is: Do the same. Just leave a zero value for ipl_entry. That way there is nothing more for you to do. Since I'm the current palo maintainer I will take care of this too. >> Helge's latest test installer iso images are at: >> 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. :)) Heh - yes. This iso was created with the current genisoimage which doesn't know about version 5 yet. > Regrettably there is 0x00000000 at byte 248, where i hoped for an example of > ipl_entry. Yes, as mentioned above, ipl_entry is just "0". That's correct. I will test your xorriso as soon as possible. Helge -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
