vyos-live-build.git/scripts/build/binary_iso, branch stretch-backports

Fix the way the .disk/mkisofs file is created

2017-11-20T21:20:53+00:00

Thanks to Daniel Reichelt for the patch. Closes: #881941

Add .disk/mkisofs file recording the xorriso command line

2017-08-10T12:53:53+00:00

Thanks to Thomas Schmitt for the suggestion.

Drop the --hardlinks option from xorriso command line call

2017-08-07T15:27:32+00:00

Instead of renaming kernel for syslinux, create hardlinks

2016-12-02T14:42:59+00:00

Set xorriso's "modification time" to SOURCE_DATE_EPOCH

2016-11-28T19:58:19+00:00

Thanks to Chris Lamb for the patch. Closes: #831379

Added EFI support by the means of grub-efi

2016-07-31T13:09:13+00:00

This work is based on debian-cd team work and uses, as much as possible, the same mkisofs options than the Debian Installation CD disk does. It assumes that /boot/grub/grub.cfg (and other design items) is generated by: binary_loopback_cfg . It relies on efi-image and grub-cpmodules being setup as build scripts on live-build package. In the future event of these two files being moved to a binary package (they are originally from: src: live-installer) the binary_grub-efi script would have to be rewritten to take the new paths into account.

Handle multiple bootloaders properly in binary_iso . Force mkisofs to add an additional eltorito entry if we have more than one bootloader.

2016-07-31T13:09:13+00:00

Added new multi bootloader helper functions

2016-07-31T13:08:11+00:00

* Added: functions/bootloaders.sh . This file adds bootloader functions that are heavily used in efi scenarios where a bootloader can act as a first or an extra bootloader. Since the introduction of the new switch: --bootloaders you can setup it like this: --bootloaders=syslinux,grub-efi . This means that syslinux is the first bootloader and grub-efi is the extra bootloader. * Added new bootloader functions: Check_Non_First_Bootloader and Check_Non_Extra_Bootloader. These functions let each one of the bootloaders abort the build because they cannot perform a role either as a first bootloader or as an extra bootloader. * Added bootloader functions: Check_First_Bootloader_Role, Check_Extra_Bootloader_Role and Check_Any_Bootloader_Role These functions let bootloaders to force their default role in a single line. At the same time many binary bootloaders were rewritten to make use of the new bootloader role functions explained above. These roles were enforced: binary_grub-legacy : First bootloader binary_grub-pc : Either first or extra bootloader binary_syslinux : Either first or extra bootloader If a bootloader is tried to be used in a role that it's not meant to be used then the build fails because that might lead to a non-bootable system.

Remove repeated LB_PRIMARY_BOOTLOADER definition

2016-07-31T12:59:33+00:00

Multi bootloader support

2015-08-29T21:56:41+00:00

Note: OLDIFS use makes IFS to be reset to "" instead to it being unset. Either we need to detect if old IFS was unset to unset it or we need a proper way of setting it as a local variable. Even more IFS it's not currently used in Check_package (which it's called from: binary_hdd). we should have a clean way of resetting/unsetting IFS when calling Check_package. The other approach it's to explicitly define IFS with its default value in the places inside live-build code where we implicitly suppose that it's going to have its default value.