Hi,
if the live.iso has ISOLINUX boot software and an El Torito boot record
for PC-BIOS, then you may apply SYSLINUX program "isohybrid" to it.
To inspect the existing boot equipment of the ISO, run
xorriso -indev live.iso -report_el_torito plain -report_system_area plain
If it reports that t
Thanks, Thomas. The xorriso report indicates that both BIOS and UEFI
boot images are present.
I notice that isohybrid is not present on my system. This might cause
silent failure of the isohybrid step. I suspect that this is another
missing dependency of live-wrapper. I have manually installed
Thomas,
if I manually install syslinux-utils and run "isohybrid -u live.iso",
live.iso is updated in place and boot loading appears to work correctly
as a CDROM, BIOS, or UEFI. My expectation was that "lwr" would perform
this step, as live-build "lb" does.
Note that I then encounter a kernel
Quoting problem? This GRUB2 command line option:
boot=live components
should be:
boot="live components"
Fixing this in the GRUB2 menu progresses the boot a little until failing
to mount something. The ISO image? Anyway, after a complaint that init
was not specified, we drop back to an (initr
On 18/07/16 14:58, Ben Caradoc-Davies wrote:
Quoting problem? This GRUB2 command line option:
boot=live components
should be:
boot="live components"
I take that back. All this does is disable live boot and allows failure
to occur elsewhere.
Kind regards,
--
Ben Caradoc-Davies
Director
Tran
Hi,
> I notice that isohybrid is not present on my system.
One may question the wisdom to put isohdpfx.bin into package "isolinux"
and the equivalent program into "syslinux-utils".
> I suspect that this is another missing dependency of live-wrapper.
Only if lwr already uses it. (Shouldn't ther
