• 1 Post
  • 9 Comments
Joined 4 months ago
cake
Cake day: February 20th, 2025

help-circle
  • My theory for what happened is:

    There might have been some delayed writes on Arch, but that’s no the main issue.

    When booting into Fedora and running an update, the state of the filesystem changed to the point that when resuming Arch, it put the filesystem into an extremely inconsistent state (where the Arch system might have cached (meta)data that was changed since hibernation).

    Also, to clarify, I still managed to recover my data, but the FS was not mountable and btrfsck couldn’t do shit. And I’m still using that Arch install to this day. XDDD







  • 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:

    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