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
      arrow-up
      0
      ·
      edit-2
      2 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.

    • fnrir@lemmy.blahaj.zoneOP
      link
      fedilink
      arrow-up
      0
      ·
      4 days ago

      Interesting. Sadly it only supports FAT32, NTFS and EXFAT with no Linux filesystems.
      And Ventoy is free. It’s hard to argue with free.

    • pogmommy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 days ago

      Yeah, bought the st300 after having repeated issues with ventoy not properly mounting disk images causing multiple Linux distro installs to fail. My st300 might be one of my best investments as a technician just for how seamless and simple it is to use.