Skip Navigation
Posts
3
Comments
23
Joined
3 mo. ago
  • The classic rethorical strategy of drawing your opponent as pregnant.

  • Remember that time conservatives said they needed guns to defend themselves from a tyrannical government?

  • There probably is, hence "bipartisan critics"

  • I disagree in the long term. He'd disappear, but the problem would persist. Someone else would eventually take his place.

    That being said, he's clearly harmful and I can't come up with a better solution, so...

  • Update: I managed to build wimboot after cherry-picking some patches.

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

  • Pretty much. I do have some releases, but considering Nix's philosophy you probably should. Ventoy-CPIO should build fine, if the right toolchains and dietlibc are in PATH. Ventoy-boot relies on overlay mounts though, so it might not build within Nix.

  • On Linux installation is done through a series of scripts and vtoycli. I haven't worked on that yet, but there's build scripts there that should do the trick, but since they build it for multiple architectures, you'll have to run just the stuff for your arch (probably x86_64).

    sth like:

     bash
        
    cd vtoycli/fat_io_lib/release
    gcc -specs "/usr/local/musl/lib/musl-gcc.specs" -O2 -D_FILE_OFFSET_BITS=64 fat*.c -c
    ar -rc libfat_io_64.a *.o
    cd ../..
    gcc -specs "/usr/local/musl/lib/musl-gcc.specs" -Os -static -D_FILE_OFFSET_BITS=64 -Ifat_io_lib/include fat_io_lib/lib/libfat_io_64.a *.c -o vtoycli_64
    # Optional
    strip --strip-all vtoycli_64
    
      
  • Focus on yourself first. I do have a Ko-Fi, but I don't promote it much.

  • 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

  • Linux @lemmy.ml
    fnrir @lemmy.blahaj.zone

    Progress update on the Ventoy blob problem

    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

  • Instructions unclear. Dick stuck in graphics card.

  • Do it

  • The Beast in my ass

  • Smash. Next question.

  • Permanently Deleted

  • Not just AI companies, but pretty much if not all big tech companies in the US. Wait, still not broad enough...

  • Wayland isn't viable for everyone yet... but at least they merged the window icon protocol.

  • Technology @lemmy.world
    fnrir @lemmy.blahaj.zone

    Looking for feedback: Ventoy CPIO

    Hello. I'm working on Ventoy CPIO, a replacement ramdisks for Ventoy. My goal is to create a sane build system (first for building ramdisks, then for the entire project), and solve the infamous issue of having blobs in the repo.