Closed JohnVillalovos closed 4 years ago
Hi, I am finishing build scripts and documents, it will take about two or three days (as I can only deal it in my spare time). After that I will commit the scripts and docs.
There are some binrary files in Ventoy's install package, they were downloaded directly from other open source project's website. In this case, I will list the download url and the file's SHA256, you can check them. For example (part of the what I'm writing):
IMG/cpio/ventoy/tool/lz4cat https://create.stephan-brumme.com/smallz4 smallz4cat-x32-v1.4 SHA-256: 13d293ddeedb469f51da41167f79b2cbdb904e681716f6e6191b233dbb162438
IMG/cpio/ventoy/tool/ar
https://busybox.net/downloads/binaries/1.30.0-i686 busybox_AR
SHA-256: f29b7d81a983c0c85d22496f4a833c18f2528a1b666eb7d47c93084c1ed66ae0
......
Awesome. Really looking forward to that. As love the idea of what Ventoy is doing but I have been a bit cautious about using it.
Hi, I have committed the build scripts and documents and updated README.md. You can refer DOC/BuildVentoyFromSource.txt.
I give the corresponding chapter of DOC/BuildVentoyFromSource.txt for the files in the list.
./IMG/cpio/ventoy/tool/zstdcat: ==> 4.13
./IMG/cpio/ventoy/tool/xzminidec: ==> 4.15
./IMG/cpio/ventoy/tool/lz4cat: ==> 5.1
./IMG/cpio/ventoy/tool/ar: ==> 5.2
./IMG/cpio/ventoy/tool/inotifyd: ==> 5.3
./IMG/cpio/ventoy/busybox/tmpsh: ==> 5.4
./IMG/cpio/ventoy/busybox/tmpxz: ==> 5.5
./VtoyTool/vtoytool/00/vtoytool_64: ==> 4.7
./VtoyTool/vtoytool/00/vtoytool_32: ==> 4.7
./VtoyTool/vtoytool/01/vtoytool_64: ==> 4.7 (build in CentOS 5.X, currently not used)
./INSTALL/tool/vtoyfat_32: ==> 4.8
./INSTALL/tool/mount.exfat-fuse_32: ==> 4.9
./INSTALL/tool/mkexfatfs_32: ==> 4.9
./INSTALL/tool/vtoy_gen_uuid: ==> 4.14
./INSTALL/tool/vtoyfat_64: ==> 4.8
./INSTALL/tool/mkexfatfs_64: ==> 4.9
./INSTALL/tool/mount.exfat-fuse_64: ==> 4.9
./INSTALL/tool/hexdump: ==> 5.7
./INSTALL/tool/xzcat: ==> 5.6
./INSTALL/ventoy/ipxe.krn: ==> 4.2
./INSTALL/ventoy/iso9660_x64.efi: ==> 4.16
./INSTALL/ventoy/vtoyjump32.exe: ==> 4.4
./INSTALL/ventoy/vtoyjump64.exe: ==> 4.4
./INSTALL/ventoy/imdisk/32/imdisk.sys: ==> 5.8
./INSTALL/ventoy/imdisk/32/imdisk.exe: ==> 5.8
./INSTALL/ventoy/imdisk/32/imdisk.cpl: ==> 5.8
./INSTALL/ventoy/imdisk/64/imdisk.sys: ==> 5.8
./INSTALL/ventoy/imdisk/64/imdisk.exe: ==> 5.8
./INSTALL/ventoy/imdisk/64/imdisk.cpl: ==> 5.8
./INSTALL/ventoy/ventoy_x64.efi: ==> 4.6
./INSTALL/ventoy/memdisk: ==> 5.9
./INSTALL/EFI/BOOT/grubx64.efi: ==> 5.10
./INSTALL/EFI/BOOT/MokManager.efi: ==> 5.10
./INSTALL/EFI/BOOT/grubx64_real.efi: ==> 4.1
./INSTALL/EFI/BOOT/BOOTX64.EFI: ==> 5.10
./INSTALL/Ventoy2Disk.exe: ==> 4.3
./VBLADE/vblade-master/vblade_32: ==> 4.12
./VBLADE/vblade-master/vblade_64: ==> 4.12
./DMSETUP/dmsetup: ==> 4.5
Closing this. Will add individual issues as attempt to build.
I see the following binary files in the repository. Where is the source code for these files? How can we recreate them? How do we know these binary blobs are safe?