(mirror of https://github.com/vyos/vyos-live-build.git) https://git.amelek.net/vyos/vyos-live-build.git/atom?h=stretch-backports 2018-02-14T17:49:36+00:00 2018-02-14T17:49:36+00:00 Raphaël Hertzog hertzog@debian.org 2018-02-14T17:49:36+00:00 urn:sha1:96e73960b3e64bae81294250e5ad531212ef0ac1 /sbin/mkfs.nfts -> /sbin/mkfs.ntfs 2017-09-01T08:29:20+00:00 Matthijs Kooijman matthijs@stdin.nl 2017-08-29T12:50:46+00:00 urn:sha1:72ca3bcb2062fe5cceb4ae9b3855568aaaa7275d To generate an hdd image, binary_hdd first estimates the needed size of the image using du. By default, when du finds multiple hardlinked copies of a file, it counts them only once. However, when the target filesystem is FAT, which does not support hardlinks, these files will take up more space when finally copying the contents, breaking the build: P: Copying binary contents into image... cp: error writing 'chroot/binary.tmp/live/initrd.img-4.9.0-3-amd64': No space left on device cp: error writing 'chroot/binary.tmp/efi/boot/bootx64.efi': No space left on device cp: error writing 'chroot/binary.tmp/efi/boot/bootia32.efi': No space left on device cp: cannot create directory 'chroot/binary.tmp/boot/grub': No space left on device cp: cannot create directory 'chroot/binary.tmp/isolinux': No space left on device To fix this, pass --count-links to du when the target is FAT, to make the space estimation correct. This problem is exposed by commit 9c974b26b (Instead of renaming kernel for syslinux, create hardlinks), which might need to be separately fixed (to not waste space on FAT targets), but binary_hdd should at least handle hardlinks more gracefully. 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.