I use local seedvault backup and then sync via round sync daily trigger to my Nextcloud WebDav Server (native seedvault was not able to use this, for some reason).
The best advice is often: Use a dot and start a new sentence. The best writers use very short sentences in a row and simple words. They flow easily and do not break reading. This works particularly well in science and for difficult topics.
Most of the best writers today, and aesthetically the baseline expectation. But I personally like the older em dash and semicolon laden styles that used a greater diversity of forms to weave thoughts together.
A stream of short sentences often feels lazy, reductive, and tedious. But it is more forgiving--you can't fail if you don't try. And it inflates word count, similar to verbose Java vs compact Perl.
I find myself using semicolons excessively in my communication with LLMs. Those and nested parenthesis. I do this mostly to avoid having to restructure my words; my thought patterns are accurately reflected, and the machines have no trouble with lispish structure.
I am very happy with Moonlight/Sunshine combo. Runs neatly on my RTX 4000 Pro GPU Server. The only thing I miss is automated resolution adjustment to connected Clients, but I was able to script this with Home Assistent Windows client.
I get your point and this is likely also not what you mean, but I am very happy with a simple git tracking approach that I use across Proxmoxes and VMs [1].
Yeah, I ran into the same wall when setting the system up. I then reverted to the standard mount utility, which also supports id-mapping. But it is really not that known. See the links in the article that point to the source of the idea.
> Network file systems can cause UID/GID mismatches and add network overhead. With VirtIO-FS, I use the Linux kernel's Virtual File System to translate the hypervisor's UID to the guest's unprivileged UID. This avoids exposing the host file structure. I utilize the `X-mount.idmap` fstab option for this. Documentation on this specific implementation is not easy to find. It builds upon the idmapped mounts feature introduced by Christian Brauner in Linux 5.12 [1] and its later integration with util-linux v2.39 into the standard `mount` utility [2].
[1]: https://github.com/brauner/mount-idmapped + https://docs.kernel.org/filesystems/idmappings.html
[2]: https://github.com/systemd/systemd/releases/tag/v254
Thanks I'll give it a shot when I have a free weekend.
I think I may have complicated things by using linuxserver.io images which already require some id mapping trickery on the rootless podman side as they expect to run as root...
Thanks for the feedback! I agree. I do have a comment on this, to explain my choice:
> Podman vs Docker
You may point to Podman here because Podman is natively rootless and doesn't require a daemon and additional workarounds to run rootless. I agree. However, Docker in rootless user nesting is also robust and possible, and I decided to stick to the docker-compose.yml because it is still the industry (and homelab) standard. This minimizes the time I need to translate examples or templates. Docker in rootless and Podman are mostly interchangeable at this level. Both run processes in isolated Linux namespaces on your host VM (not the Hypervisor!).
This is not 100% and may change anytime. I guess, for me, at this time, the difference between Docker in rootless and Podman is just too small, and the time needed to migrate all my docker-compose.yml's too much, to make the jump. Overall, it is not a critical decision for this architecture, more a choice.
Regarding Debian is similar, I just stick with what I am familiar with. Debian also never lost me.
reply