You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Fri, Oct 18, 2024 at 03:23:54PM -0300, Fernando Lozano wrote:
Would anyone know why, when we loop mount an iso image, and want to
manipulate its contents to generate a new iso, we must use tar instead of
cp, such as:
sudo tar cf - -C temp-iso . | tar xf - -C new-iso
For example, to create a RHEL installer iso with a custom kickstart file
Why are you using tar? There's an easier way -- just use mkksiso:
Automatically changes the grub menu to use the name of the new kickstart
It was necessary to change ownership of the output ISO to use with virt-installer
From Brian Lane bcl@redhat.com on tech-list
On Fri, Oct 18, 2024 at 03:23:54PM -0300, Fernando Lozano wrote:
Why are you using tar? There's an easier way -- just use mkksiso:
https://weldr.io/lorax/mkksiso.html
The text was updated successfully, but these errors were encountered: