RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Hello,

a livecd generated by lorax contains both initramdisk and kernel twice. This probably makes the ISO much more bigger:

# find . ! -empty -type f -exec md5sum {} + | sort | uniq -w32 -dD
6b37ecf48c8efff50ef5417105da9d85  ./images/pxeboot/initrd.img
6b37ecf48c8efff50ef5417105da9d85  ./isolinux/initrd.img
f9c5cc6840ab0093475b3b0699f4e58b  ./images/pxeboot/vmlinuz
f9c5cc6840ab0093475b3b0699f4e58b  ./isolinux/vmlinuz

I think the "pxeboot" directory is included by accident, why would PXE files be present on a livecd when there is an option in lorax to build PXE files instead?

SYSLINUX appears to be using kernel from /images directory however Grub2 is using the one from /images/pxeboot.

Correction, grub2 uses the same kernel/initramdisk but grub2 for EFI uses the pxeimage one. I guess all could use the single copy.

They don't actually use up any more space. They are hardlinked to the same data.

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.