Talk:Remastering the Install ISO

From ArchWiki
Jump to navigation Jump to search


I recently ran into a situation where I need to create a remastered ISO image for Arch Linux. As was stated in 2007 (yikes), this page is out of date. I'm currently trying to modernize it to work with the current ISO image.

My main issue so far is figuring out the propper form of the mkisofs command. If anyone wants to lend a hand with this, I would greatly appreciate it. --Arcanazar 01:42, 9 August 2009 (EDT)

The current version uses GRUB instead of ISOLINUX. So, it's -b boot/grub/stage2_eltorito.
--Mlu 23:46, 6 March 2010 (EST)
RE: Arcanazar:
I've updated the mkisofs commands section. I, too, ran into problems. The solution was to use the mkarchiso method for generating the image.
--Integer 22:15, 18 September 2014 (CEST)
Thank you for flying xorriso. :)
Nevertheless i believe the variables in the xorriso example should be given as tangible examples. Like iso_label="ARCH_201209". "iso_application" and "iso_publisher" are probably only ornamental. The "-preparer" option could well be omitted. "custom_archiso_dir" should get value ~/customiso.
Variable "workdir" is not really applicable in the remastering situation. Even if you have a file "isohdpfx.bin" on hard disk, it might be of the wrong ISOLINUX version. (This warning applies also to program "isohybrid" which officially has to match the ISOLINUX version in the ISO image. SYSLINUX does not guarantee that MBR and El Torito boot image are exchangable between versions. It is not clear whether really incompatible versions are around.)
In general you rather need the first 512 bytes from the original ISO image file. See for example the dd command in which is about adding a feature to an isohybrid enabled ISO.
This file obtained from the old ISO is a matching MBR template for the ISOLINUX boot equipment in the emerging ISO image. To be used by -isohybrid-mbr ${file_with_first_512_bytes}.
Alternatively there is a file /isolinux/isohdpfx.bin in archlinux-2013.11.01-dual.iso. Most probably a copy of the MBR template used with the mkarchiso run. The mkarchiso code in the web suggests this. Thus to be used by -isohybrid-mbr ${custom_archiso_dir}/isolinux/isohdpfx.bin
Scdbackup (talk) 11:21, 20 September 2014 (UTC)
My proposal for a new text about isohybrid and xorriso can be seen in the second half of my talk page
Scdbackup (talk) 14:38, 25 September 2014 (UTC)
Since no protest was posted, i installed my proposal in the wiki page.
Scdbackup (talk) 13:46, 4 October 2014 (UTC)
I've updated the customization section. File names are current.
--Integer 22:23, 18 September 2014 (CEST)

The "Extracting the Iso" section needs to be updated. unsquashfs no longer produces a folder that contains a mountable image file. Instead it produces all of the contents of the airootfs.sfs. Following the instructions of this article no longer works. I don't have the expertise to correct this. --BeenEncoded (talk) 17:52, 21 October 2015 (UTC)

If you need to run "mkinitcpio -p linux" in the chroot, as described by 2.3.1 (Manually->Customization->Modifying the x86_64 system), it fails saying "==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux'". I'm adding a step to temporarily copy it into squashfs-root, the inverse of the existing step for "If you updated the kernel or the initramfs, copy them over to the system:". I'm also adding steps to remove vmlinuz-linux and initramfs-linux.img from the squashfs-root before running mksquashfs. Jamespharvey20 (talk) 01:31, 10 May 2018 (UTC)

Instead of adding steps to remove vmlinux-linux and initramfs-linux.img from the squashfs-root before running mksquashfs, changed the existing steps for copying these over to the system from cp to mv, and added rm for the fallback. Otherwise, these files are unnecessarily included in the new airootfs.sfs, when they didn't exist in the original, don't need to be there, and won't be used from there.

Jamespharvey20 (talk) 01:46, 10 May 2018 (UTC)