Hi,
uploaded is a new (semi-stable) development snapshot
http://www.gnu.org/software/xorriso/xorriso-1.3.7.tar.gz
with the new features for PALO on HP-PA, which are now promised to
stay compatible in future releases.
MD5: 961939a15cdb2b9893fbe25f453d9ac4
Version timestamp :
To Helge Deller:
Please check-read my descriptions of header versions 4 and 5 beginning at
doc/boot_sectors.txt line 975
resp.
http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt#L972
for terminology, unclear or false statements, ...
Thanks
Hi,
the proposed patch for the boot sector documentation looks at the
topic from the PALO user perspective. But the perspective of the
file boot_sectors.txt is the one of an ISO 9660 producer.
So i would like to re-arrange the info.
How about this for the command line part ? Would it be
the proposed patch for the boot sector documentation looks at the
topic from the PALO user perspective. But the perspective of the
file boot_sectors.txt is the one of an ISO 9660 producer.
So i would like to re-arrange the info.
How about this for the command line part ? Would it be
Hi,
How to recognize a PALO that is newer ?
It should be palo 1.92 or higher.
... PALOHDRVERSION ...
I could update it to 5.
I think it is appropriate.
Readers of libisofs docs and of PALO could make a clear connection.
We shouldn't make xorriso more complicated than necessary.
Yeah.
Hi Thomas,
On 04/09/2014 05:53 PM, Thomas Schmitt wrote:
How to recognize a PALO that is newer ?
It should be palo 1.92 or higher.
... PALOHDRVERSION ...
I could update it to 5.
I think it is appropriate.
Readers of libisofs docs and of PALO could make a clear connection.
Ok, committed.
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
Hi,
Because of how palo is built, it ensures, that the entry point is always
zero.
That's very convenient for all of us.
I will test your xorriso as soon as possible.
Lemme check whether defining the macro
Libisofs_enable_unreleased_hppa_palO
in libisofs/libisofs.h of the current GNU
Control: tag -1 +pending
On Mon, Apr 07, 2014 at 09:04:06PM +0200, Helge Deller wrote:
Package: debian-cd
Version: 3.1.14
Severity: normal
Tags: patch
debian-cd is currently broken for the hppa/parisc architecture.
The attached patch to the tools/boot/jessie/boot-hppa file fixes three issues:
Hi Thomas,
On 04/08/2014 , Helge Deller wrote:
I will test your xorriso as soon as possible.
Attached is the diff to xorriso-1.3.7 which I used to test.
Up to now I only tested on x86_64, testing on hppa is still needed (but will
work most likely).
As you can see from the diff, your code was
Package: debian-cd
Version: 3.1.14
Severity: normal
Tags: patch
debian-cd is currently broken for the hppa/parisc architecture.
The attached patch to the tools/boot/jessie/boot-hppa file fixes three issues:
1. The bootloader on hppa is palo. Remove one line in the script which tries
to move a
Hi,
in january we had a conversation about xorriso and PALO.
I implemented the boot sector as learned from genisoimage:
version number 4 and the short command line at byte 24 to 151.
Further there is the proposed version 5 with long command line at
byte 1024 to 2047, and the yet unexplained
Hi Thomas,
On 04/07/2014 10:03 PM, Thomas Schmitt wrote:
in january we had a conversation about xorriso and PALO.
Yes, I did not forgot it :-)
I implemented the boot sector as learned from genisoimage:
version number 4 and the short command line at byte 24 to 151.
Further there is the
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
Hi,
looking at your description of ipl_entry computation
- after midnight - makes me search for alternatives.
I would have to duplicate a non-trivial part of PALO
which then would have to be validated against the
original code. From then on, i would have to maintain
it without having much clue.
15 matches
Mail list logo
