Nur weil Kabel den Anschluss verlieren, darf man sie nicht direkt ausschließen!
- 0 Posts
- 41 Comments
Joined 2 years ago
Cake day: June 15th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Will you share pictures of your latest Gundam dioramas with us?
Quick, be fast and setup a binary cache so that he can substitute nixos.org with you.
Trust me, it’s the only way.
31·3 months agoThere is radicle - for which you could run five nodes and have them seed each other.
Well state includes (for most configs I’ve seen) the persistence of user paswords, known_hosts, wifi auth, /home, /var, nix-channels, nixos-generations, disk encryption passwords, secrets in general, docker/podman, VMs, …
Luckily most gui toolkits have a way of disabling CSD. For gtk/libadwaita I recommend something like Gradience to generate a theme with corners of your liking.
What’s the difference between opaque and transparent+blur?
I’m not sure if I can donate to LixOS, yet…
3·5 months ago25 W idle * 1 year = 219kWh
ANS * 0.21 EUR/kWh = 45.99 EUR
I’d say that’s still a significant amount, even if you subtract from that amount the time you use the computer.
I’m curious, how do you run the 4x3090s? The FE Cards would be 4x3=12 PCIe slots and 4x16=64 PCIe lanes… Did you nvlink them? What about transient power spikes? Any clock or even VBIOS mods?
I’m also on p2p 2x3090 with 48GB of VRAM. Honestly it’s a nice experience, but still somewhat limiting…
I’m currently running deepseek-r1-distill-llama-70b-awq with the aphrodite engine. Though the same applies for llama-3.3-70b. It works great and is way faster than ollama for example. But my max context is around 22k tokens. More VRAM would allow me more context, even more VRAM would allow for speculative decoding, cuda graphs, …
Maybe I’ll drop down to a 35b model to get more context and a bit of speed. But I don’t really want to justify the possible decrease in answer quality.
I’m running such a setup!
This is my nixos config, though feel free to ignore it, since it’s optmized for me and not others.
How did I achieve your described setup?
- nixos + flakes & colmena: Sync system config & updates
- impermanence through btrfs snapshots: destroy all non-declarative state between reboots to avoid drift between systems
- syncthing: synchronise ALL user files between systems (at least my server is always online to reduce sync inconsistencies from only having a single device active at the time)
- rustic: hourly backups from all devices to the same repos, since this is deduplicated and my systems are mostly synchronised, I have a very clear record of my file histories
The added info from
pvis also nice ^^
It’s affected by the write-hole phenomenon. In BTRFS case that can mean that perfectly good old data might corrupt without any notice.
You might get
sued.
PenTUIn