(mirror of https://github.com/vyos/vyos-live-build.git) https://git.amelek.net/vyos/vyos-live-build.git/atom?h=crux 2016-07-31T13:08:11+00:00 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. 2016-07-31T12:59:33+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2016-01-19T23:53:53+00:00 urn:sha1:0624064d44ed811aec5c43fabfd7b928688ed8e1 2016-06-18T17:36:16+00:00 Kristian Klausen klausenbusk@hotmail.com 2016-06-17T21:14:41+00:00 urn:sha1:489a09ba92328cef846598a15329e9ff91519e3c e2fsprogs 1.43 enabled ext4 "64bit" feature as default, which broke ext4 HDD images as EXTLINUX doesn't support it. 2016-05-26T19:26:36+00:00 Kristian Klausen klausenbusk@hotmail.com 2016-05-26T19:26:36+00:00 urn:sha1:a8cc7084279116870bc0e37e0836ac7e1f5b780a dash doesn't support parameter expansion it seems. So implemented with "tr" as in binary_syslinus. 2016-05-26T15:34:22+00:00 Kristian Klausen klausenbusk@hotmail.com 2016-05-26T15:34:22+00:00 urn:sha1:ddc6659002b751e3eea0ca42bb22e52279cc4288 Fix #773833 2016-05-26T15:33:20+00:00 Kristian Klausen klausenbusk@hotmail.com 2016-05-26T15:33:20+00:00 urn:sha1:090c6f3ceaef0c344b822063012c08c1e50fba88 This reverts commit 5161dcdf3bb50a8be7385f86fdfc60b0eb700bfa. 2015-12-15T13:59:49+00:00 Maximilian Mehnert maximilian.mehnert@gmx.de 2015-09-23T08:59:28+00:00 urn:sha1:2c118b384c8b14f96e3a60160e90399c71a1b103 2015-09-23T08:48:46+00:00 Maximilian Mehnert maximilian.mehnert@gmx.de 2015-07-16T07:58:46+00:00 urn:sha1:46920d22bd3a31241baa504bc178343c760a4812 Some BIOSes dont't boot from partitions starting at sector 1024. Some are even more peculiar and only start from sector 63. This patch adds an option for the binary_hdd target to manually configure the partition start. 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-08-27T08:17:22+00:00 Carlos Zuferri chals@chalsattack.com 2015-08-27T08:17:22+00:00 urn:sha1:d43874c405ca468fc72158da6280c6b11755a3e6