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

  • moonpiedumplings@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    21 days ago

    The current problem with ventoy is that proprietary blobs are essentially an unauditable possible security backdoor.

    This product is entirely proprietary, including the hardware, and even worse.

      • moonpiedumplings@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        21 days ago

        They are not explicitly designed to boot ISO’s?

        Also, price. I’m not gonna pay quadruple the price for something that can be done entirely in software.