- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
Posting this since quite a bit has changed since I last posted about this on !technology@lemmy.world.
Here’s a rough breakdown of the current status:
- shared Ventoy components: build and seem to work, needs more testing
- grub / menu - builds
- EDK II apps / UEFI chainloader and more - builds
- iPXE / BIOS chainloader - builds, with fixes for newer toolchains
- ISO9660 and UDF drivers - TODO
- Ventoy CPIO / Linux ramdisk: builds; I deemed musl xzcat unneeded, so I skipped it; needs more testing
- wimboot / Windows chainloader (?) - stalled, I lack the necessary knowledge to work on it
- geom-ventoy / FreeBSD disk mapping kernel module - is being worked on, slowly; not ready for testing
- anything else is a TODO
This should be enough to boot Linux with just what’s built manually, but I haven’t tried that yet.
Secure Boot is just done by using a pre-built bypass package. I’ll deal with that later.
Having more people testing this would be nice. :)
Cheers
What is the ventoy blob thing and why is it important?
TLDR: There’s binaries instead of source code in the repo, which makes it hard to near-impossible to verify what it’s doing. And the instructions for building those is lacking.
GH issue: https://github.com/ventoy/Ventoy/issues/2795
Oh really? You’re saying its a security risk?
It is a risk as seen in the exploit in xz utils.
What’s ventoy?
A tool to make bootable Live USBs out of operating system ISOs.
I think that’s not quite right, otherwise you could say that Rufus is the same. Ventoy is a Live USB tool that allows you to drag and drop ISOs onto a storage device and boot them without needing to image the device at all. It has its own interface that it boots into, that lets you select which ISO to then boot up.