What I took from this post is that every living room / home theater setup needs a server rack instead of a HiFi rack. Dudnt matter what you thrown in it, it looks badass.

OK, so people can use the definition instead. In fact it might be more useful.

Absolutely not.

It’s a trap.

- A message from Canada

You tap search on the home screen, you get the Google app.

It’s happening via the Google app.

I see. Makes sense.

If you need to serve only one user at the time, ollama +Webui works great. If you need multiple users at the same time, check out vLLM.

Why can’t it serve multiple users? Open Web UI seems to support multiple users.

There’s a WIP VirtIO driver in a PR but it’s not done yet. VMware’s own VMSVGA is open source if I remember correctly. I wonder if they’ll adapt it to KVM and if they do, whether that’ll be usable in KVM without VMware.

If we get VirtIO 3D acceleration in Windows guests from this, I’d be really happy.

Oh this is very interesting!

You could use a systemd unit file:

[Unit]
Description=docker_compose_systemd-sonarr
After=docker.service 
Requires=docker.service

[Service]
TimeoutStartSec=0

WorkingDirectory=/var/lib/sonarr

ExecStartPre=-/usr/bin/docker compose kill --remove-orphans
ExecStartPre=-/usr/bin/docker compose down --remove-orphans
ExecStartPre=-/usr/bin/docker compose rm -f -s -v
ExecStartPre=-/usr/bin/docker compose pull
ExecStart=/usr/bin/docker compose up

Restart=always
RestartSec=30

[Install]
WantedBy=multi-user.target

You’d place your compose file in the working dir /var/lib/sonarr. Depending on what tag you’ve set for the image in the compose file, it would be autoupdated, or stay fixed. E.g. lscr.io/linuxserver/sonarr:latest would get autoupdated whereas lscr.io/linuxserver/sonarr:4.0.10 would keep the container at version 4.0.10. If you want to update from 4.0.10, you’d have to change it in the compose file.

And there are breaking changes in this Jellyfin release.

Sounds a bit like the drug dealer’s business model.

I think federated non-profit video platforms won’t work on large scale without P2P.

Not noticeable with always-on Tailscale with the default split-tunnel mode. That is when Tailscale is only used to access Tailscale machines and everything else is routed via the default route.

Same here. I literally swapped to Lawnchair to get rid of Google search from my home screen.

Unfortunately it doesn’t support Private Space yet.

One of them. The other is that this is open source which has certain implications that don’t exist exist for Nova.

Exactly. The path for success is clear as there’s clear need and public investment to back it up.

Apps typically don’t interact with the kernel. They interact with a C library like glibc, bionic or musl. So long as the kernel has a POSIX interface you should be able to compile the same app on different kernels. We do this with apps that run on Linux, BSD and QNX for example.

As for Android apps, you could extend that to running the Android runtime on top of different kernels. We did that with the Android runtime on QNX for BlackBerry 10 and we did it in a way that didn’t even require recompilation. That said Wiki says they don’t support Android apps. So if you meant Android apps they simply don’t.