He'll be like: "It's not like you. Please stop doing this 🥺"
You wouldn't be surprised :3
I have to ask: What kind of browser is Android? Do people watch porn from WebView? Wouldn't that just be Chrome?
I do care.
I'm sending ✨ thoughts and prayers ✨
I'd say Newton's 1st is more applicable here
...subscription services? For everything?
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?
"Debate" is used as a foot in the door
Edit: also happy cake day
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
Hibernating my computer and then forgetting about it and booting into a different OS (Fedora Silverblue) on the same partition (BTRFS subvolume stuff). AND THEN TRYING TO RESUME THE HIBERNATED OS (Arch btw).
my filesystem was pretty much unrecoverable and it was my fault
but you didn't actually mention any one of them. For that you can use ! and your Lemmy client should suggest a community
It still won't mention it, but I'll link it
(and I didn't wanna come across as mean)
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 !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
Contribute to fnr1r/ventoy-cpio development by creating an account on GitHub.
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.
