The intention was to get a Linux ISO to boot from a HDD, you copy all files and folders from the optical disk (or mounted ISO) to the FAT volume of the HDD, rename its ISOLINUX folder to SYSLINUX, rename the contained isolinux.cfg file to syslinux.cfg, then "syslinux" the FAT volume and it will write a Syslinux boot sector to the volume which will then load and run the live fileset from FAT not much differently than if it was on an optical disk. The other parts of the Syslinux Project are Extlinux for network booting, and of course Syslinux proper for booting from FAT partitions. Which means the ISO when burned to an optical disk or mounted will have an ISOLINUX folder in the root of its filesystem, and within that folder will be the boot files which allow it to boot as an optical disk. The master image is simply written bitwise to the target regardless of differences in the "heads & sectors" that might be native to the target USB device, which can be a show-stopper when it comes to bootability, or it can compromise erase-block alignment which can dramatically slow the performance of an otherwise good master file set.īootable ISO's are made to boot using the Isolinux proper approach, one part of the overall Syslinux Project. Things like Etcher or dd are nonideal when the "drive geometry" of the master that was imaged is not fully compatible with the target USB device and/or its bootability. Ignorance is not complete failure, just minor lack of awaremess sometimes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |