GitHub - fnr1r/ventoy-meta
github.com
Contribute to fnr1r/ventoy-meta development by creating an account on GitHub.

Posting this since quite a bit has changed since I last posted about this on [email protected].

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

  • moonpiedumplingsEnglish
    1·
    23 hours 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.

      • moonpiedumplingsEnglish
        1·
        23 hours 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.

          • moonpiedumplingsEnglish
            1·
            23 hours ago

            I never got uefi images booting properly on those grub multi boot utility drives. Granted the last time I bothered with it was like 10 years ago now

            I haven’t had any issues with Ventoy, everything I’ve attempted to boot works. Doesn’t matter how it does it if it works.