fnrir

joined 4 months ago
[–] fnrir@lemmy.blahaj.zone 28 points 1 week ago* (last edited 1 week ago)

EDIT: I got Onion'd

[–] fnrir@lemmy.blahaj.zone 4 points 2 weeks ago

I do care.

I'm sending ✨ thoughts and prayers ✨

[–] fnrir@lemmy.blahaj.zone 3 points 2 weeks ago

I'd say Newton's 1st is more applicable here

[–] fnrir@lemmy.blahaj.zone 8 points 2 weeks ago (1 children)

Rust: do you mean Self or self?

[–] fnrir@lemmy.blahaj.zone 1 points 2 weeks ago

Okay. I get it. It's also not that funny.

[–] fnrir@lemmy.blahaj.zone 2 points 2 weeks ago (1 children)

...subscription services? For everything?

[–] fnrir@lemmy.blahaj.zone 4 points 2 weeks ago* (last edited 2 weeks ago) (7 children)

The maybe use public transport? If you REALLY need to use buy car - buy one.

Also: families were not mentioned before in this thread. Is driving around with your partner and 5 kids and a couch a daily occasion?

[–] fnrir@lemmy.blahaj.zone 3 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

"Debate" is used as a foot in the door

Edit: also happy cake day

[–] fnrir@lemmy.blahaj.zone 4 points 3 weeks ago

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

 

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

 

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.

view more: next ›