You can now write it to the usb drive with ( WARNING!!!!! Make sure /dev/sdb is actually your usb drive. Setup the loopback device and format it with ext3 with $ losetup -o $OFFSET -sizelimit $SIZELIMIT /dev/loop1 archiso-custom.isoĪt this point your image is ready (finally). This tells you the Start and End of the arch-custom.iso3 partition.īy multiplying both these numbers with 512, you get resp the $OFFSET and $SIZELIMIT for the loopback device. You can do this with $ fdisk -l arch-custom.iso So first you need to show exactly where the partition starts and ends. If you do this wrong, you’ll screw up the image file. But to create the loopback device, you need to tell it exactly where in the image file the partition starts and ends. That loopback device is available as any harddrive and you can create a filesystem in it like you would do with a normal partition. You create a loopback device that points to the partition inside the iso image. This is tricky as the file isn’t an actual block device. I/O size (minimum/optimal ): 512 bytes / 512 bytesĭevice Boot Start End Sectors Size Id TypeĪrch-custom.iso1 * 0 14608383 14608384 7G 0 EmptyĪrch-custom.iso2 172 172 0 0B ef EFI (FAT-12/16/Īrch-custom.iso3 14608384 26142719 11534336 5.5G 83 Linuxįor most of those questions in fdisk (the ones ending with a : without input) I just hit enter, choosing the default option.Īt this point you’re ready to create an ext3 (or other) filesystem in there. Sector size (logical/physical ): 512 bytes / 512 bytes In the end, this is the xorriso command I used to create the iso: iso_label = "ARCH_201601" The documentation below it on xorriso is better, if you combine it with the eltorito stuff lower down. Don’t use the genisoimage command in the docs. ![]() The first problem I encountered was creating the ISO. Also do the part with “modifying the EFI boot image”. I copied it to my homedir (outside the ~/customiso tree) so I can copy it back later if I need to instead of having to unsquashfs the airootfs.sfs file all the time. I didn’t delete the squashfs-root folder though. Then you exit the chroot again, recreate the airootfs.sfs image and copy the new kernel and initrd image to the right places. In there and do other stuff to the Live OS. You can install packages after the step that says mkinitcpio -p linux Download the dual installation iso from the Arch Linux website and read through the docs on how to extract the airootfs.sfs, mount it, chroot to it and modify it. The Arch documentation on remastering the iso tells you most you should know. The three main sources of documentation that helped me setting this up is the Arch Linux documentation on Remastering the Install ISO, the Boot Parameter documentation of ArchISO and a blog post by Joshua Thijssen on creating partitioned disk images. ![]() It took me a while to figure this out, but I got it in the end. One thing I had trouble with though, is getting a custom Live CD that could boot from my USB drive, has a persistence layer so changes are saved when booting, and booted both from UEFI only systems (my laptop) and preferably also BIOS only systems. Even though it is not the easiest n00b distro, in the end the documentation is so good that if you’re new to Linux, you can probably find out how to do most stuff if you’re inquisitive. I am running Arch Linux for a while now and am quite happy with it. Tags: ArchLinux UEFI live remaster iso persistent cow Creating a custom persistent Arch Linux live cd for UEFI and BIOS systems
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |