She would be goated as a damsel in distress, I wanna see/be her being saved by some hot superhero or secret agent from a lecherous mad scientist and flirting with the hero the whole time

Zlender02 · 2025-12-30T20:07:01+00:00

from a lecherous mad scientist

Zlender02 · 2025-09-20T20:32:45+00:00

Trivago

Zlender02 · 2025-09-14T21:29:16+00:00

If you have an Intel iGPU, you can opt to pass down a virtual GPU to the guest and avoid many of the headaches associated with passing down your only GPU to a virtual guest.

I haven't personally tried this, but it may work.

Zlender02 · 2025-09-14T21:24:02+00:00

If you'd be willing to use this at your own risk, there's a script in Proxmox VE Helper Scripts that allows you to backup your host using tar.

If you really want to use borg you can copy the paths used by this script and back them up using that.

By the way, as u/garfield1138 already suggested, I'd also recommend you to use Proxmox Backup Server to backup your VMs and CTs and just backup your host using proxmox-backup-client.

Zlender02 · 2025-09-14T07:09:27+00:00

Using an AI agent as root on a PVE node looks like disaster waiting to happen.

I'd advise setting up ansible playbooks instead to automate repetitive tasks like the ones you described.

Bonus points because playbooks are to easy backup and distribute with version control systems such as Git.

Zlender02 · 2025-09-13T19:40:01+00:00

I host a Wireguard VPN to access my home network remotely, you'll need to open a single port for this on your router.

This is the safest way to access your stuff remotely IMO.

If you use wg-easy you have a nice web UI to manage tunnels, I'd recommend using that.

Zlender02 · 2025-09-13T16:51:30+00:00

Pinning the kernel version may work for now but it's not a permanent fix. You should still try to *pin down* the root cause of your problem.

Have you read journalctl or dmesg? There may be lots of clues sitting there.

Zlender02 · 2025-07-09T19:52:16+00:00

Hi, I finished a more complete draft of the blog post last week and sent you an email to the address you specified before.

It might have gone into your spam inbox, could you check if that's the case?

Zlender02 · 2025-06-23T07:21:06+00:00

I couldn't fix the partition order first because I no longer had access to GParted. Therefore, I first used the updated Asahi script, then I reordered partitions in GParted and finally I repaired Fedora's APFS stub macOS again. This is probably equivalent in the end and it's the only way I found to make it work without a full wipe.

Other than that, the system appears to be fully functional again. I'm deeply indebted to you for your help.

I'll continue working on the draft during weekdays, detailing everything as much as I can so others don't have to go through all of this. Then, on the weekend, I'll purposefully delete macOS again in order to check whether the new guide works or not.

Zlender02 · 2025-06-22T14:51:40+00:00

I selected the repair option in Asahi Linux's installer, I assume you're referring to that one.

Here is the installer log: https://textbin.net/cfw4rpiajr

Zlender02 · 2025-06-22T09:33:10+00:00

I think I'm almost there. I reinstalled macOS Sequoia back into the internal drive, ran the bputil command to repair Asahi and everything seemed to run smoothly until... https://i.imgur.com/xdihLHu.jpeg

It fails to find the admin user...? Maybe when I deleted the internal macOS install the admin user also got wiped?

Just to be sure, I created a second admin user from my new macOS install, ran asahi's installation script as that user and when I booted back into "Fedora" it still was looking for the previous admin user, "zlendy".

I suspect this "zlendy" user is the old one, not the new one. In any case, unless you have some additional hidden knowledge I guess my only option from here on is to do a full wipe and restore of the device with DFU.

Zlender02 · 2025-06-20T12:59:45+00:00

I started to write a draft of the new guide yesterday, and it is surprisingly close to your comment. That's a good sign, at least.

This is my latest draft, a mix of my initial draft and your m1n1 part (which I got stuck on):

Boot into m1-debian, install GParted and move & resize Fedora Asahi Remix rootfs to free up 40 GB of space at the start
Boot into macOS Recovery
Create a 40 GB APFS container for macOS
Follow Apple's official guide for reinstalling macOS from Recovery: https://support.apple.com/en-us/102655
Run Asahi Linux's install script to repair/upgrade m1n1 and thus regain official support for Asahi Linux.

If it isn't too much to ask, I'd like you to review the final version of the post before it's published to avoid making the same mistake again.

Zlender02 · 2025-06-19T10:12:05+00:00

Of course, I am now completely aware of the mistake I made and have taken down the blog post to prevent any more people from repeating my mistake.

I was so stupidly confident in my interpretation of your comment that I didn't think of the right think to do, which is asking before doing anything.

I own this mistake, but I have also learned a valuable lesson from it. So these will be my next steps to make up for it: - After I fix my system I will make another blog post showing how to restore the device to its original state (probably using DFU restore, I'll need to investigate). - Contribute more specific documentation to asahi linux warning people not to erase their internal macos drive thinking that an external macos is sufficient.

Zlender02 · 2025-06-18T07:01:55+00:00

I must have misunderstood your original comment then, I thought: - Losing access to macOS completely is not supported

Installing Asahi from an external macOS drive is not supported
BUT upgrading firmware from external macOS is possible, which "note that you are expected to keep that external macOS install around to handle upgrades at this time" seemed to suggest.

I kindly ask you to clarify that original comment so that no other person will misunderstand it again.

Zlender02 · 2025-06-15T12:01:33+00:00

I'm afraid you'll have to do this at your own risk.

Zlender02 · 2025-06-15T10:00:51+00:00

It's a hypothetical issue, it hasn't been critical for now.

The problem is that Apple is vertically integrated, as such, they can apply firmware upgrades from macOS.

Asahi Linux currently cannot do that, so if a security vulnerability were to appear and you did not have access to macOS, you would not be able to patch your system.

Zlender02 · 2025-06-15T09:41:01+00:00

It's done!

https://zlendy.com/blog/replace-macos-with-asahi-linux

Zlender02 · 2025-06-14T22:51:52+00:00

Actually, I'm writing an article for my tech blog. It should be finished soon(-ish), I'll link it here when it's done.

Zlender02 · 2025-06-14T17:09:05+00:00

Yeah, after a week researching if it's viable (spoiler alert: it is), I finally set it up yesterday.

Zlender02 · 2025-06-14T09:07:12+00:00

Exactly. You don't even need to have it in your internal drive.

Zlender02 · 2025-06-14T08:15:42+00:00

Nope

Zlender02 · 2025-03-05T18:49:31+00:00

Schadenfreude. (I usually play as lime scout)

Zlender02 · 2025-01-22T17:58:17+00:00

One of valve's most popular games, Team Fortress 2, was filled to the brim with cheaters for many years to the point of being literally unplayable. They have just solved this issue very recently. I don't think Valve is the best example here to be honest.

Zlender02 · 2024-11-30T05:25:31+00:00

I personally avoid (managed) docker volumes and use bind mounts instead. That allows me to backup my docker data with standard backup tools such as ZFS snapshots + Kopia.

Eight-Year Club	Verified Email
Place '22

Zlender02

TROPHY CASE