Greetings,
FYI
The following xorriso (1.5.4) command fails on RockyLinux 9.0 and 9.1. It does not fail on RockyLinux 8.7. It fails on both macos and linux. xorriso -indev Rocky-9.1-x86_64-minimal.iso -report_system_area as_mkisofs
This is surprising since it's a very common pattern to determine how an ISO was built. Then this information is used when remastering the ISO. This technique works perfectly with debian, ubuntu, and all flavors of redhat/fedora EXCEPT rockylinux. It works perfectly with all versions of almalinux.
It would seem the way the ISO is built changed from 8.7 to 9.x, and it is somewhat unconventional. There are likely very good reasons why it's done unconventionally. But it might be best if this approach did not cause the aforementioned command to fail.
Cheers, Robert Nielsen robert@dakota.org
In Rocky Linux 8, genisoimage/mkisofs/other utilities are used by pungi (an older version) when being constructed. With the new build system, we had to make a choice: A) Use methods that are being superseded by xorriso in Fedora ELN or B) future proof on xorriso for all releases beyond version 8 and avoid using the mkisofs personality. We went with option B to be prepared for a possible deprecation/removal of the aforementioned tools in the coming years. Fedora recently has added xorriso support to pungi for example: https://pagure.io/pungi/blob/master/f/pungi/createiso.py#_121 and their Fedora ELN ISO's report "SORRY" severity when using as_mkisofs, just as ours do. This does not affect how the images operate, as far as we can tell. (As an aside, you are the first to report an issue with "report_system_area")
The process essentially works like this:
1) lorax is used to make the initial boot.iso images 2a) Pungi creates new extra images using the data generated by lorax and graft points (RL8) 2b) Empanadas (our toolkit) reuses the boot.iso generated by lorax to make the extra images (RL9+)
Pungi typically uses genisoimage/mkisofs alongside graft points that were generated elsewhere. Our toolkit also generates graft points, but we use a much smaller dialog and attempt to reuse how the boot.iso was initially made in lorax. With this, it is possible something may get "missed" in translation.
The method is a bit unconventional, sure.
If you are able to provide input on what switches we can add to make "as_mkisofs" work for you and others, then we are open to it. Though I would encourage avoiding any mkisofs personality usage. You can find our templates here: https://git.resf.org/sig_core/toolkit/src/branch/devel/iso/empanadas/empanad...
-L
On Wed, 30 Nov 2022 at 13:51, Robert Nielsen via rocky-devel < rocky-devel@lists.resf.org> wrote:
Greetings,
FYI
The following xorriso (1.5.4) command fails on RockyLinux 9.0 and 9.1. It does not fail on RockyLinux 8.7. It fails on both macos and linux. xorriso -indev Rocky-9.1-x86_64-minimal.iso -report_system_area as_mkisofs
This is surprising since it's a very common pattern to determine how an ISO was built. Then this information is used when remastering the ISO. This technique works perfectly with debian, ubuntu, and all flavors of redhat/fedora EXCEPT rockylinux. It works perfectly with all versions of almalinux.
It would seem the way the ISO is built changed from 8.7 to 9.x, and it is somewhat unconventional. There are likely very good reasons why it's done unconventionally. But it might be best if this approach did not cause the aforementioned command to fail.
Cheers, Robert Nielsen robert@dakota.org
rocky-devel mailing list -- rocky-devel@lists.resf.org To unsubscribe send an email to rocky-devel-leave@lists.resf.org
-
Louis Abel -
Robert Nielsen