#1430 PR merged: Adapt chrp-boot option when xorrisofs is used

Labels: enhancement, fixed / solved / done, minor bug

schabrolles opened issue at 2017-07-25 19:26:

  • xorrisofs use -chrp-boot-part option to generate PPC boot while
    mkisofs use -chrp-boot

We need then to change the -chrp-boot by -chrp-boot-part when using with xorrisofs

  • tested with SLE12 on ppc64le system

jsmeix commented at 2017-07-26 07:40:

I assume this fixes
http://lists.relax-and-recover.org/pipermail/rear-users/2017-July/003465.html

... rear on SLES 12 SP2 on Power (LE).
... xorriso : FAILURE : -as genisofs: Unsupported option '-chrp-boot'

@schabrolles
as always many thanks for all your various contributions
that improve ReaR in particular on POWER architecture!

schlomo commented at 2017-07-26 07:53:

Good catch, I can easily imagine that there are a lot more issues with "just" using xorrisofs instead of mkisofs. On my Ubuntu 17.04 amd64 for example xorrisofs supports the -chrp-boot option, but maybe you have an older version:
image

I am therefore wondering if we shouldn't slowly start to use xorriso natively instead. Maybe requiring xorriso is again something for the future ReaR version that does away with the old legacy stuff ☺

jsmeix commented at 2017-07-26 09:22:

FYI:
On SLES12-SP2 I have

# xorrisofs -version
xorriso 1.3.4    ...

# xorrisofs -help 2>&1 | grep -- -chrp
  -chrp-boot-part    ...

and on openSUSE Leap 42.1 I have

# xorrisofs -version
xorriso 1.4.0    ....

# xorrisofs -help 2>&1 | grep -- -chrp
  -chrp-boot-part    ...
  -chrp-boot    Alias of -chrp-boot-part

If you wonder why xorrisofs on Leap 42.1 is newer
than xorrisofs on SLES12-SP2 regardless that
SLES12-SP2 was released later than Leap 42.1:
In general SLES service packs do not provide whole software
version upgrades (but only bugfixes) unless there is a good reason
for a version upgrade to avoid backward incompatible changes.

To link related issues:
Regarding requiring xorriso in a future ReaR version cf.
https://github.com/rear/rear/issues/1360#issuecomment-300517148
and regarding dropping support of old legacy stuff cf.
https://github.com/rear/rear/issues/1390

[Export of Github issue for rear/rear.]