[-] Byter@lemmy.one 2 points 1 month ago

Try to use open source software. Harder for it to disappear.

[-] Byter@lemmy.one 5 points 2 months ago

I use it all the time for hot drinks and soups.

[-] Byter@lemmy.one 6 points 2 months ago

Sorry to break it to you, but that's a bot.

[-] Byter@lemmy.one 28 points 2 months ago

At least it's level on a table because of the bar

[-] Byter@lemmy.one 14 points 2 months ago

I have access to Into the Breach and Slay the Spire on Android but not in my Steam library. I'd enjoy first party support in playing them on my Deck.

[-] Byter@lemmy.one 11 points 2 months ago

Android games on Steam Deck.

[-] Byter@lemmy.one 2 points 3 months ago

The OP didn't mention Proxmox in their post. I've been speaking generally, not about any specific OS. For example, Nvidia's enterprise offerings include a license to use their "GRID" vGPU tech (and the enabled feature flag in the driver).

[-] Byter@lemmy.one 2 points 3 months ago

Why? Product segmentation I suppose. Last I looked, the Virtio project's efforts were still work-in-progress. The Arch wiki article corroborates that today. Inconsistent behavior across brands and product lines.

[-] Byter@lemmy.one 10 points 3 months ago

I've also wanted to do this for a while, but there were always a few too many barriers to actually spin up the project. Here's just a brain dump of things I've seen recently.

vGPUs continue to be behind a license. But there is now vgpu_unlock.

L1T just showed off PCIe "fabric" from Liqid that can switch physical devices between machines.

Turning VMs on and off isn't as slick as either of the above, but that is doable today. You'll just have to build all the switching automation yourself. That could just be a shell script running QEMU/libvirt commands, at a minimum.

[-] Byter@lemmy.one 5 points 4 months ago

Thanks for asking. Not sure how I toggled that on...

[-] Byter@lemmy.one 30 points 4 months ago
[-] Byter@lemmy.one 1 points 4 months ago

I'm not sure I understand your question.

Eat has its own major mode which is used when you open a standalone buffer via the eat function.

When it's embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) -- and many of those can be closed with q, yes.

I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I'll admit I don't really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.

7
Chasin' Tail (lemmy.one)
view more: next ›

Byter

joined 1 year ago