Mittens take away too much dexterity for many things. But a 3-finger glove is the perfect compromise: https://www.snowsportprofessionals.com/wp-content/uploads/2017/11/8272aca90cb09ec2c85ef324e10933f57f500daf.jpg

Since all of these politicians are at the same time ensuring that they are above the law, I don’t think you can count on getting them arrested.

Am Danish. This is fairly accurate, a solid 60% of Danish is just random guttural sounds. This documentary however misses that the remainder is 30% raw deadpan sarcasm, and 10% English words pronounced in an awful accent.

To contrast and compare, this is an average modern Swedish television quiz show: https://youtu.be/lzv6ljgwgzs

Dunno… Maybe because the companies are not in charge of running the country?

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.

This is not correct.

The T-54 entered production in 1947

The T-62 entered production in 1961

The T-72 entered production in 1970

The T-80 entered production in 1976

The T-90 entered production in 1993

The years are pretty close to the names, so the can be used as a rough estimation, but they can’t be used as exact years.

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.

Factorio. I saw transport belts in my dreams.

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 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.

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.

I read that the ash is actually quite bad for fertilising plants… And it might even hinder the plants growth… I don’t have the source handy, unfortunately…

So if you want to be environmental, your best bet is probably to be composted (only legal en very few places) or buried in a cardboard coffin.

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.

I personally trust Asus, EVGA (Rip), Gigabyte, Palit, PNY, Sapphire and XFX when buying graphics cards.

My current card is a Geforce GTX 1060 6GB from Asus that I bought in 2017, and it hasn’t skipped a beat.3A

I’m perfectly satisfied with the theory that bender simply is 430.04% or more in total.

Computer hardware

Reminds me of DEFCON

This is pretty cool, but I’m wondering why… Sure there’s lots of systems that make use of A/B partitions, which is a pretty good move, but with BTRFS you could have it all in one partition with an A/B subvolume, and they would even be able to share extents that are common between the two (meaning drastically reduced disk space requirements), while still maintaining the ability to boot into either…

Depending on how much changes you might even keep many more than just two subvolumes. On my machine I run BTRFS with snapper, which takes periodic snapshots, as well as before and after every time I install or uninstall a package, with the ability to boot into any of the snapshots if a change somehow botches my system.