Thanks for posting miniserve <3

I used to do that but I find the UX of that quite annoying because before you can do: systemctl status and see what's up with all the system services. Now you have to do systemctl status -M <user-for-that-stack> for every stack that you're running to get a complete picture.

I haven't found a way around that and would be very thankful for pointers.

This is cool! I once made a project very much like this: https://github.com/svenstaro/genact

Check it out if you like this kind of thing.

Love Genact!! Fantastic job

We do this in Arch Linux. It requires someone handling the registrations which isn't great either.

Seems like something LLMs should be good at. Take the new user info and ask it to vet the account or raise it to a human.

Sadly it has no good ollama support: https://github.com/yetone/avante.nvim/issues/1149

it supports LMStudio and that's way better than ollama anyway.

I tried to find out what this actually does but apart from a video that is very hard to watch on mobile, there's really nothing there that tries to sell me on this. Why not use the readme to do your elevator pitch?

It's absurd. "If you have to ask... then it's not for you!"

I've recently deep-dived into QEMU performance especially in order to cut down boot/bootstrapping times for quickly running tests and I'd like to share some tricks:

- Templating: https://qemu.readthedocs.io/en/v9.1.0/system/vm-templating.h... - virtio-fs: https://virtio-fs.gitlab.io/ - Overlay storage images: https://wiki.archlinux.org/title/QEMU#Overlay_storage_images

Cloud init will handle unique IDs although might add some boot time

You need to get it to re-run, which I'm not sure there is a standard way to do during runtime. Can it even do all its job without a reboot?

Maybe I misunderstood, is this skipping boot as well?

I was thinking the VM would still follow the normal boot process (in which case you can reset cloud init before powering down)

Yes they are saving memory state to a file.

Is there a reason to use 9p over virtiofs in this case? It looks to me as though virtiofs was made exactly with the idea to deal good performance.

NixOS has switched to virtiofs 4 days ago: https://github.com/NixOS/nixpkgs/pull/362081

Not all use-cases are faster with virtiofs.

> Not all use-cases are faster with virtiofs

Aren't they though? Do you have a counter example?

Interesting and may be worth writing a qemu issue about.

The author commented on that in 2022 https://news.ycombinator.com/item?id=33200731

Is 9p compatible with saving VM states? I recently experimented with virtiofs and was disappointed to find it was incompatible so it didn't really work for my use case.

I don't even really need performance, I only really want to be able to grab driver files from a common location and ditch the samba shares.

I made a thing called genact that pretends to be useful but actually isn't doing anything at all: https://github.com/svenstaro/genact

There's also a web version! https://svenstaro.github.io/genact/

This is great!

You could try running rustic on your repository. It should be a drop-in for restic and maybe it's faster? I would actually be very interested in this. Would be great if you could do that and report back.