similar to: Bootable ISO with extra data outside the ISO?

I see there's a memtest on the Linux discs I've created... would it be possible to put another program in place (a module, perhaps?) that can calculate a hash using a certain algorithm (i.e. SHA512 or similar) to validate and print out the hash of the boot ISO before booting it? The integrity of the ISO is absolutely critical. Thanks, Bret

On 05/03/2016 02:31 AM, Thomas Schmitt via Syslinux wrote: > Hi, > > John Lewis wrote: >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch >> >> The show stopper for me was the mkisofs because the closest command I >> had available was xorrisofs and I think a switch was different. > If you have questions about xorrisofs, then just ask me. :))

On 05/03/2016 12:27 AM, Geert Stappers via Syslinux wrote: > On Mon, May 02, 2016 at 11:21:13PM -0400, John Lewis via Syslinux wrote: >> I was trying to follow this tutorial >> https://help.ubuntu.com/community/LiveCDCustomizationFromScratch. i got >> confused with the part about Create an isolinux.cfg file. >> >> The show stopper for me was the mkisofs because the

Hi, Bret Schuhmacher wrote: > I'm going to have to read it > about 20 more times to get my head around what you wrote ?;-) . You are invited to ask for clarifications, if necessary. Have a nice day :) Thomas

Hi, my proposal is based on a mathematical proof (see mail before) and yours is correct too. They cannot but match. Let's inspect your examples: Ady wrote: > ISO size: 1'085'736'960 bytes ( > 1GiB) This are exactly 132 cylinders of 255x63. 132 is divisible by 4. So there is no padding needed. > Cylinders (1st attempt)=132 > [...] > 2120580 / 4 = 530145, so

> > Same result as yours. > > > Have a nice day :) > > Thomas > I was under the impression (apparently the wrong one) that your pseudo-code was adding 4 cylinders to the first example, from 132 to 136, which would be non-optimal. Since I am not a developer, I believe you when you say that such jump won't happen :). Perhaps the code will be more clear to me

Hi, > I only have the vaguest > understand of what the flags in the man page of xorrisofs and xorriso are. The options reflect a long tradition of program mkisofs and the winded road of boot firmware entry points in ISO 9660 filesystems. So one cannot expect to find much of a common system in them. > there doesn't seem to > exist a hello word like exercise that is simple and

I was trying to follow this tutorial https://help.ubuntu.com/community/LiveCDCustomizationFromScratch. i got confused with the part about Create an isolinux.cfg file. The show stopper for me was the mkisofs because the closest command I had available was xorrisofs and I think a switch was different.

Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso

Hi, On 29/07/2014 23:19, Thomas Schmitt wrote: > A good opportunity to brag with xorriso's boot inspection > features (since xorriso-1.3.8): Yes! I've upgraded libburn, libisofs and libisoburn so now I can play with it too ;) > I forgot to advise (or misadvise) -isohybrid-apm-hfsplus with > the image /isolinux/efiboot.img . So we only got one APM > partition here. A

Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz

Hi, we are the developers of an alternative to mkisofs: program xorriso from libburnia-project.org . The current development cycle is about support for creating bootable CDs, DVDs, BDs. So we look for testers and for advise about ISOLINUX specifics. The example from the ISOLINUX wiki is supposed to work if you replace "mkisofs" by "xorriso -as mkisofs". I.e: xorriso -as

EFI systems typically don't support booting off ISO 9660 filesystems, even if written to USB sticks. This patch adds support for generating a GPT that covers the stick as well, with an additional partition entry pointing purely at the secondary El Torito image. When burned to CD the secondary El Torito will be used as an EFI boot image, and when written to a USB stick the GPT partition

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

I have an issue with cdrecord though and I can't figure it out. I use Webmin, which basically just creates an iso and then uses cdrecord to burn it and it worked fine with previously installed CentOS 4 (I wiped and reinstalled about 8 months ago). This is the command that Webmin tries to execute... cdrecord -v dev=0,0,0 speed=4 -isosize \

On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB

Hi there guys! I want to set up Puppy-Linux to run off a 2GB USB key-drive in native mode (I.e. not as a virtual machine, which I'm finding runs too slow on my system, under XP.) To test it out, I want to run off a 150GB USB HDD. Now this drive is NTFS formatted and way bigger than the 1GB file structure limit that I read about in the Syslinux documentation. There's only one

HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The

Hi, Jernej Simon?i? wrote: > As long as you have cygwin with development tools installed, it's just > ./configure && make. autotools magic. I myself have few clue of contemporary MS-Windows. > https://eternallybored.org/misc/xorriso/xorriso-1.4.2-cygwin32.zip Thank you for flying xorriso. > > > oscdimg.exe -a -m -o -j1 > > >

Thomas Schmitt via Syslinux said on Sat, Oct 24, 2015 at 12:56:49AM +0200: >Needed is a EFI FAT image > 32 MiB and a new xorriso (available >on demand). My test script on RHEL 7.1 creates that even if I could make it smaller as the kernel + initrd fits in less than 32 MB. So let me make that try first ! o I changed myline in the script to dd a 30 MB image file, burt the ISO with it, and