(mirror of https://github.com/vyos/vyos-live-build.git) https://git.amelek.net/vyos/vyos-live-build.git/atom?h=stretch-backports 2016-12-02T14:01:28+00:00 2016-12-02T14:01:28+00:00 Raphaël Hertzog hertzog@debian.org 2016-12-02T14:01:28+00:00 urn:sha1:58fd378005400ca4592f21e74f105625344a72b3 2016-07-31T13:09:13+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2016-01-18T03:15:47+00:00 urn:sha1:c4327f61384910014b3914f125521577c97e5d79 The binary parts of grub-pc are left for the original binary_grub-pc. As a consequence both /boot/grub/grub.cfg and /boot/grub/loopback.cfg files will be present in any Debian Live CD. This might be useful to be reused from binary_grub-* bootloaders. 2016-07-31T13:08:11+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2016-01-18T03:07:48+00:00 urn:sha1:9d1a983cc8fe12966d1a2c24a6ee0cfb419b3ce5 * 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. 2015-08-29T21:56:41+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2015-08-21T21:54:46+00:00 urn:sha1:d515ae56842f9420ff4c629eac18904f7beef2e8 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. 2015-05-04T18:37:00+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-05-04T18:37:00+00:00 urn:sha1:9bf7c99eed0dc01567c83b3464b3a57fdc7d1186 2015-05-04T18:33:00+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-05-04T18:33:00+00:00 urn:sha1:f93fa286d5e7348150aab4874794f7d96dac0894