vyos-live-build.git/scripts, branch 1.3.8 (mirror of https://github.com/vyos/vyos-live-build.git)
https://git.amelek.net/vyos/vyos-live-build.git/atom?h=1.3.82021-08-09T14:24:21+00:00add items for grub setup and enable persistence2021-08-09T14:24:21+00:00Kim Hagenkim@sentrium.io2021-08-09T14:24:21+00:00urn:sha1:301cd5b991caded9c84d1ce4bb214ac720ba5796create loop partitions with mknod instead of bind mounting /dev2021-07-29T20:42:06+00:00Kim Hagenkim@sentrium.io2021-07-29T20:42:06+00:00urn:sha1:f81f65598555f88f1b0535807da7418e5326be67create vyos hdd image2021-07-23T13:14:26+00:00Kim Hagenkim@sentrium.io2021-07-23T13:14:26+00:00urn:sha1:ca2a4e78bedd6ec8d6dffd94009163596c1c5e1cUEFI: remove the EFI/debian/grub.cfg, not necessary anymore2018-09-19T10:35:17+00:00Luca Boccassibluca@debian.org2018-09-14T15:38:33+00:00urn:sha1:f108fdfa71c9d66a5ef9dfe7f1f48c170c7f228e
Turns out gcd works fine after adding /boot/grub/grub.cfg in the img,
as that's the path that gets hardcoded, and adding the EFI/debian/
grub.cfg was not necessary, so remove it.
Use gcd{x64.aa64}.efi.signed for amd64/arm64 arch.2018-09-19T10:34:22+00:00Steven Shiausteven@nchc.org.tw2018-08-22T03:43:40+00:00urn:sha1:c22f1f5b71745922ae28df0ebf4b7d1a49d89f55
For secured boot in binary_grub-efi, the gcdx64.efi.signed is
the boot loader for removable device, like CD or USB flash drive,
while grubx64.efi.signed is for hard drive. Therefore for live system,
use gcdx64.efi.signed for amd64 and gcdaa64.efi.signed for arm64.
copy keys to /etc/apt/trusted.gpg.d with appropriate extension for them to not be ignored.2018-09-13T15:25:09+00:00Marcel Partapmpartap@gmx.net2018-09-12T16:00:20+00:00urn:sha1:8403487d4e3bda65cdd2ea6081399f7977325adbHandle includes.chroot files installed over symlinked directories2018-07-27T08:51:49+00:00Raphaël Hertzoghertzog@debian.org2018-07-27T07:46:55+00:00urn:sha1:52908422880f8d5cfa18c577d4138d5449af37f6
With the merged /usr feature now enabled in debootstrap, we have
/bin and /lib which are symlinks to /usr/bin and /usr/lib. If
the live-build configuration provides files in
config/includes.chroot/lib/ or config/includes.chroot/bin/ then
lb chroot_includes will replace the /lib or /bin symlink with real
directories having only the content provided in chroot.includes and
problems will follow... the build will usually fail later with a
cryptic error message (for example a hook failing to execute
/usr/bin/env).
Work around the issue by creating a tarball of the files to install
and by unpacking that tarball from within the chroot with appropriate
options.
UEFI: parse vendor from Grub package metadata2018-06-07T10:34:26+00:00Luca Boccassibluca@debian.org2018-06-06T12:41:35+00:00urn:sha1:316b1281581b188e3353fe59bb40bcb81cbd953f
When using Secure Boot, grub2 as built by Debian will now load a config
file from EFI/$VENDOR instead of having EFI/debian hardcoded.
$VENDOR comes from dpkg-vendor or from the user building grub2.
The vendor string is stored in the control metadata as Efi-Vendor, so
retrieve it when building the EFI image.
Avoid apt-key add and just drop the key in /etc/apt/trusted.gpg.d2018-06-03T21:06:36+00:00Luca Boccassibluca@debian.org2018-06-01T13:29:05+00:00urn:sha1:e5492b1c702858eb26e2b93c65810773ad0bfa85
Only gnupgv is part of the deboostrap set these days, but apt-key needs
the full gpg (with gpg-agent) which is just a recommends.
Instead just drop the key with an .asc suffix in /etc/apt/trusted.gpg.d
which is supported since apt version 1.4
lb clean: remove ONIE image2018-04-17T10:39:26+00:00Luca Boccassibluca@debian.org2018-04-11T19:13:23+00:00urn:sha1:186765e3fd905a2ecd08cd22dd9afdcc581b1d0a