linux-live/bootfiles
root 7e856fcc5a if /target/boot is analogous to /boot, then the ESP would usually get mounted to
/target/boot/EFI and the bootloader would end up in somewhere like:
/target/boot/efi/EFI/Boot/

That looks insane. However as we're not actually mounting the ESP, we can
cut out the empty mountpoint (/boot/efi)? This is either a great idea or a terrible one
I'm not sure which.
2019-09-28 18:42:24 +00:00
..
efi-files feat: uefi support 2019-07-17 21:59:27 +03:00
bootinst.bat if /target/boot is analogous to /boot, then the ESP would usually get mounted to 2019-09-28 18:42:24 +00:00
bootinst.sh fix: wrong efi folder 2019-07-17 22:13:08 +03:00
bootlogo.png ugly boot logo ensures your will put here better one for your live kit 2012-09-05 23:51:54 -05:00
extlinux.x32 add extlinux 32bit 2017-12-15 04:03:49 -05:00
extlinux.x64 add 64bit extlinux 2017-12-15 04:36:00 -05:00
isolinux.bin recompile to support booting from /linux/boot directory 2017-12-12 09:55:09 -05:00
ldlinux.c32 recompile to support booting from /linux/boot directory 2017-12-12 09:55:09 -05:00
libcom32.c32 recompile to support booting from /linux/boot directory 2017-12-12 09:55:09 -05:00
libutil.c32 recompile to support booting from /linux/boot directory 2017-12-12 09:55:09 -05:00
mbr.bin bootinst improvements 2012-11-11 11:36:54 -06:00
pxelinux.0 update syslinux to version 6.03 2017-12-12 09:37:24 -05:00
syslinux.cfg Disable apparmor by default 2019-06-19 13:11:01 +02:00
syslinux.com update syslinux to version 6.03 2017-12-12 09:37:24 -05:00
syslinux.exe update syslinux to version 6.03 2017-12-12 09:37:24 -05:00
vesamenu.c32 recompile to support booting from /linux/boot directory 2017-12-12 09:55:09 -05:00