It kinda depends a bit on the user’s background… For someone who is used to windows and how computers in general works, I would probably agree with you.

But for people who are more phone/tablet native, I don’t think something like Fedora Silverblue is actually that bad of a choice. It comes natively with Gnome 3, which isn’t too dissimilar to Android or iOS. Updates are installed in one fell swoop with a reboot, just like Android or iOS. Flatpaks behave much more like an App on Android or iOS, they are self contained, and don’t affect eachother.

I just set up my daughters (9 y/o) first school laptop, and picked Fedora Silverblue, and apart from learning about the save icon, and learning how to store files in a filesystem, she was pretty much instantaneously functional, having most of her prior computing experience on an Android phone.

I really don’t see much benefit to running two clusters.

I’m also running single clusters with multiple ingress controllers both at home and at work.

If you are concerned with blast radius, you should probably first look into setting up Network Policies to ensure that pods can’t talk to things they shouldn’t.

There is of course still the risk of something escaping the container, but the risk is rather low in comparison. There are options out there for hardening the container runtime further.

You might also look into adding things that can monitor the cluster for intrusions or prevent them. Stuff like running CrowdSec on your ingresses, and using Falco to watch for various malicious behaviour.

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.

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>

My personal opinion is that soy milk tastes like grass… I’ve tried it in coffee, alone, on cereal, but I just can’t avoid feeling like someone dumped a handful of freshly cut grass in…

Almond is pretty good on it’s own, but in coffee it tastes like marzipan… It’s not bad, but not the taste I want in my coffee.

Oat is what tastes most like cow’s milk to me.

My home-assistant installation alone is too much for my Raspberry Pi 3. It depends entirely on how much data it’s processing and needing to keep in memory.

Octoprint needs to respond in a timely manner, so you will want to have the system mostly idle (at least below 60 percent CPU at all times), preferably octoprint should be the only thing running on the system unless it’s rather powerful.

If I were you, I would install octoprint exclusively on your Raspberry Pi 3, and then buy a Raspberry Pi 4 for the other services.

I’m running Pi-hole and a wireguard VPN on an old Raspberry Pi 2, which is perfectly fine if you are not expecting gigabit speeds on the VPN.

Oh, I misremembered… It’s only 7 disks in BTRFS RAID1.

I have:

• 12 TB
• 8 TB
• 6 TB
• 6 TB
• 3 TB
• 3 TB
• 2 TB

For a combined total of 40 TB raw storage, which in RAID1 turns into 20 TB usable.

Yep

I never said anything about RAID5. I’m running RAID1.

BTRFS is running just fine for my 8 disk home server.

According to Karl, Billy must pay all the legal fees if he withdraws from the lawsuit. He must also pay the legal fees if he loses. Billy’s only way out of paying would be to win the lawsuit.

So the longer Karl strings him along, the more the fees will mount.

And since Billy doesn’t have a leg to stand on he can either withdraw now, pay a lot of money, and admit he lied. Or he can keep fighting mounting more fees in the slim nope of winning.

Uh… Please enlighten me on what DBUS has to do with DNS…

It’s rather important to understand the performance characteristics for people to know what to expect if they want to switch to Linux.

If games ran at half the FPS on Linux as they would have on Windows, then pretty much no one would be gaming on linux.

If you got 90% performance on Linux, only Linux enthusiasts would take the performance hit.

At 100% performance the choice is completely free, people that got fed up with windows could just switch.

When Linux outperforms Windows, this puts us in very interesting territory, as this might even entice a bunch of people to give Linux a try to see whether the switch is worth the performance. I’m personally quite interested in seeing whether this could be the tipping point for Linux on desktop and laptop to really start taking off.

Sure, there’s also the scratch image, which is entirely empty… So if your app is just a single statically linked binary, your entire container contents can be a single binary.

The busybox image is also more barebones than alpine, but still has a couple of basic tools.

Containers can be entirely without anything. Some containers only contain the binary that gets executed. But many containers do contain pretty much a full distribution, but I have yet to see a container with a password hash in its /etc/shadow file…

So while the container has a root account, it doesn’t have any login at all, no password, no ssh key, nothing.