No need for a physically separated network, that’s what VLANs are for

That sound like you need a more serious setup, where you can control the network priorities and set a QoS, so the devices that you use interactively get priority over the other devices.

So as far as I understand, you have

• Outer router (Comcast), which has WiFi enabled
• Inner router (your own), which has WiFi enabled, and further meshes with other WiFi mesh devices (or is the mesh separate?)
• A plain switch, for stuff you want cabled and fast

Is that correct?

Why not get the WiFi in the Comcast router disabled, and use your inner network exclusively, such that both WiFi and ethernet devices are on the same network?

That’s what I did with my network, and I even got the ISP to put their modem/router into bridge mode, so it’s completely transparent.

That makes perfect sense, and switching is definitely annoying then… But the person I responded to said they had multiple WiFi networks at home… E.g. Not on holiday

Why on earth would you have multiple WiFi networks in your home?

You might need some workarounds for it to work. I’m using Sway as my window manager, where the missing piece war the “for_window” bit on this page.

https://github.com/flameshot-org/flameshot/blob/master/docs/Sway and wlroots support.md

Depending on your desktop environment/window manager, you might need some different workarounds.

For me it captures all the screens and let’s me pick the region, even when crossing over two screens.

Which OS are you using? And if Linux, are you running Wayland or X?

Beautiful!

Not OP , but regarding zsh, it has much better auto completion, and suggestion support. Additionally you can theme your prompt much more, see for example powerlevel10k

The dependencies get drastically easier if you use Docker. Likewise many, but not all of the upgrade issues also get fixed with Docker.

This, but for playing VR games

Thank you 😊

Immutable distros were originally very focused on servers, and more recently distros for workstations has stated gaining more interest as the concept has matured.

With the advent of cloud computing “immutable infrastructure” started becoming more and more popular. This concept started out as someone sitting down and grabbing a normal Linux distribution, and installing all the necessary bits for the server purpose they needed. Then baking that into an image. Now you could launch new copies of that machine whenever you felt like it, and they would behave exactly the same. If any of them started doing something wonky, you just destroyed it and launched a new copy. This was very useful for software developers and operations people who could now more easily reason about how things behaved. And be sure that the difference in behaviour wasn’t because someone forgot to enable a setting, install a tool, or skipped a step in the setup.

On the software development side, you also simultaneously saw more and more developers make use of functional programming methods, and al’ng with those immutable data structures. Fundamentally, instead of adding an item to a list, you make a new list with all the old and the new items in it. You never change the data after it’s creation. Each “change” is a new copy, with the difference already built in.

Then containers started becoming popular. Which allowed software developers to build a container image on their local computer, and then ship that image to a server, where the image behaved exactly as it did on their local machine. This also meant that the actual OS became less and less important, as everything needed by the container was already bundled in the container. The containers also worked as “immutable”, since everything you would install or change within the containers would be immediately lost when the container was destroyed, and recreating it would be exactly as when the image was built.

The advent of containerised workloads, gave rise to a lot of different Linux distributions. Since the containers pretty much only needed the Linux kernel from the OS, it was pretty easy to make a container-centric operating system. And in turn lock down everything else, even completely omitting having a package manager. Stuff like CoreOS, Flatcar, Rancher OS, and many others were immutable linuxes that only catered to containers. I don’t know the exact mechanism for all of these, but at least the original CoreOS and Flatcar make the actual system read only, and on top of that had two man partitions, one of the partitions would be the current system, and the other would be where updates were downloaded. Once an update was downloaded and ready, you just rebooted the machine, and it would be running off the updated partition. Which also meant easy rollback if you got a broken update. You could just boot off the other unupdated partition.

Containers were however rather ill suited for desktop applications, as there were no good way to provide a GUI. You could serve up a Web page, but native GUI apps were tricky.

That’s where Flatpak, Snaps and all that came, which essentially brings the container mentality to normal desktop apps. This brought immutability to individual apps, as they brought their own dependencies. And therefore didn’t have to rely on the correct versions of dependencies being available on the machine.

The logical next step was of course to add immutability to workstation distributions. This is where the popularity of Fedora Silverblue, NixOS, and many others really started taking shape.

I believe Fedora Silverblue uses ostree to make the system “immutable”. Of course you can still make changes to your system, but the system is built to be completely aware of the state before and the state after, this is what’s called “atomic”. There’s no such thing as a partially installed package. There is only the state before installing something, and the state when the thing is fully installed. You can roll back to any of the previous states, to recover from a broken update or misconfiguration. This also makes trying out new things with no risk. Trying out a new desktop environment, and it broke your system? Just roll back. Accidentally uninstalled a critical package? Just roll back. What to try out a new display manager? Just apply the config and roll back if you don’t like it.

SteamOS also does the thing with multiple partitions, and even allows you to turn off the immutability. Other distributions aren’t as lenient. There’s no way to turn off the immutability in NixOS or Fedora Silverblue.

I have a few cheap cameras that can handle both WiFi and ethernet, they support an SD card, and they do continuous recording regardless of connection type.

I actually don’t know whether timeshift can just run easily from a live USB, but I don’t see why not.

But of course that also requires you to have installed and set up timeshift before (which is obviously a good idea)

It’s quite a different deal when the whole operating system it built around a timeshift-like concept.

Depends what you break. Sure kernels are easy to fix like you mention, but what if you bork your display manager?

ZFS doesn’t really support mismatched disks. In OP’s case it would behave as if it was 4x 2TB disks, making 4 TB of raw storage unusable, with 1 disk of parity that would yield 6TB of usable storage. In the future the 2x 2TB disks could be swapped with 4 TB disks, and then ZFS would make use of all the storage, yielding 12 TB of usable storage.

BTRFS handles mismatched disks just fine, however it’s RAID5 and RAID6 modes are still partially broken. RAID1 works fine, but results in half the storage being used for parity, so this would again yield a total of 6TB usable with the current disks.

SSD longevity seems to be better than HDDs overall. The limiting factor is how many write cycles the SSD can handle, but in most cases the write endurance is so high that it’s unreachable by most home/NAS systems.

SSDs are however really bad for cold storage, as they will lose the charge stored in their cells if left unpowered too long. When the SSD is powered it will automatically refresh the cells in the background to ensure they don’t lose their charge.

Since you are talking about pods, you are obviously emitting all your logs on stdout and stderr, and you have of course also labeled your pods nicely, so grepping all 36 gods is as easy as kubectl logs -l <label-key>=<label-value> | grep <search-term>