

That’s definitely not what I’ve heard, please elaborate.
That’s definitely not what I’ve heard, please elaborate.
Arch is fine… It has good documentation.
NixOS or Gentoo is probably my pick.
The only true “roadblock” I have experienced was when running on the raspberry pi, where the CPU was too slow to do any transcoding at all, and the memory was too small and unupgradable to be able to run much at the same time.
As soon as I had migrated to a proper desktop (the i7-920) I could run basically everything I would regularly want. And from then on it was a piece of cake upgrading. Shut the machine down, unplug, swap the parts, plug in, turn on. Linux has happily booted up with no trouble with the new hardware.
Since my first server was a classic bios, and the later machines was UEFI, then that step required a reinstall… But after the reinstall, I actually just copied all the contents of the root partition over, and it just worked.
The main limiting factors for me has been the amount of memory, the amount of SATA connectors for disks, and whether the hardware supported hardware transcoding.
For memory, ensure the motherboard has 4 sockets for memory, that makes it easy to start out with a bit of memory and upgrade later. For example you could start out with 2x 4GB sticks for a total of 8GB, and then later when you feel like you need more, you buy 2x 8GB sticks. Now you have a total of 24 GB.
For SATA ports, ensure the motherboard has enough ports for your needs, and I would also strongly recommend looking for a motherboard with at least 2 PCIe 16x slots, as that will allow you too add many more SATA or SAS ports via a SAS card.
Hardware encoding is far from a must. It’s only really necessary if you have a lot of media in unsupported formats by the client devices. 95% of my library is h.264 in 1080p, which is supported on pretty much everything, so it will play directly and not require any transcoding. Most 1080p media is encoded in h.264, so it’s usually a non-issue. 4k media however often come in HEVC (h.265), which many devices do not support. These files will require transcoding to be playable on devices that do not support it, but a CPU can still transcode it using “software transcoding”, it’s just much slower and less responsive. So I would consider it a nice convenience, but definitely not a must, and it depends entirely on the encoding of the media library.
EDIT: Oh, I just remembered… Beware of non-standard hardware. For example motherboards from Dell and IBM/Lenovo. These often come with non-standard fan mounts and headers, which means you can’t replace the fans. They also often have non-standard power supplies, in non-standard form factors, which means that if the power supply dies, it’s nearly impossibly to replace, and when you upgrade your motherboard you are likely forced to replace the power supply as well, and since the size of the power supply isn’t standard, the new power supply will not fix in the case… Many of their motherboards also have non-standard mounts for the motherboards, which means that you are forced to replace the case when upgrading the motherboard… You can often find companies selling their old workstations for dirt-cheap, which can be a great way to get started, but often these workstations are so non-standard that you practically can’t upgrade them… Often the only standard components in these are harddrives, SSDs, optical disc drives, memory, and any installed PCIe cards.
As long as it’s capable of booting into Linux, then you can start building a homelab…
Initially I had a 2-bay Synology NAS, and a Raspberry Pi 3B… It was very modest, but enough to stream media to my TV and run a bunch of different stuff in docker containers.
In my house, computer hardware is handed down. I buy something to upgrade my desktop, and whatever falls off that machine is handed down to my wife or my daughter’s machines, then finally it’s handed down to the server.
At some point my old Core i7-920 ended up in the server. This was plenty to upgrade the server to running Kubernetes with even more stuff, and even software transcoding some media for streaming. Running BTRFS gave me the flexibility to add various used disks over time.
At some point the CPU went bad, so I bought an upgrade for my desktop, and handed my old CPU donown the can, which released an Intel Core i5-2400F for the server. At this point storage and memory started to become the main limiting factor, so I added a PCI SAS card in IT mode to add more disks.
As this point my wife needed a faster CPU, so I bought a newer used CPU for her, and her old Intel Core i7-3770 was handed down to the server. That gave quite a boost in raw CPU power.
I ended up with a spare Intel Core i5-7600 because the first motherboard I bought for my wife was dead, so I looked up and found that for very cheap I could buy a motherboard to match, so I upgraded the server which opened up proper hardware transcoding.
I have since added 2 Intel NUCs to have a highly available control plane for my cluster.
This is where my server is at right now, and it’s way beyond sufficient for the media streaming, photo library, various game servers, a lot of self-hosted smart home stuff, and all sorts of other random bits and pieces I want to run.
My suggestion would be to start out by finding the cheapest possible option, and then learn what your needs are.
What do you want your server to do? What software do you want to run? What hardware do you want to connect to it? All of this will evolve as you start using your server more and more, and you will learn what you need to buy to achieve what you want to.
Hard agree…
¯\_(ツ)_/¯ been daily driving Linux for at least a decade now…
But I haven’t found a way to run my HTC Vive on my nvidia gpu and the updater software for my car on Linux… So I still have a dual boot for those
Overcooked (4-player)
Lovers in a dangerous space time (4-player)
Death squared (2-4 player)
Toybox Turbos (4-player)
Trine (3-player)
Keep Talking and Nobody Explodes (infinite player)
Magicka (4-player)
The various Jackbox Party Packs (players depends on which game. Most support 4 players, some up to 100 players, each player must have a phone to play on)
Worms W.M.D (6-player)
Untitled Goose Game (2-player)
Agreed, Talos or k3s are great for home clusters
My home Kubernetes cluster started out on a Core i7-920 with 8 GB of memory.
Upgraded to 16 GB memory
Upgraded to a Core i5-2400S
Upgraded to a Core i7-3770
Upgraded to 32 GB memory
Recently Upgraded to a Core i5-7600K
I think I’ll stay with that for rather long…
I did however add 2 Intel NUCs (gen 6 and gen 8) to the cluster to have a distributed control plane and some distributed storage.
Jellyfin has supported Music and TV shows since the start
Dunning-Kruger is a hell of a drug…
The author of the article is clearly just confusing “encryption”, “cryptography” and “hashing”. Reading the full article makes it clear that the intention was to salt and hash the passwords, not encrypting them.
The OP made the argument that Zuckerberg wanted to know their passwords, such that if the users reused the same passwords elsewhere, then he would be able to log in there and check out their accounts.
For example he could have seen a profile he was interested in, nabbed their password and looked into their email.
Not that he wouldn’t have godmode on their Facebook account, and needed their password to access their account, because of course he could have just accessed those accounts without needing the password.
I have not heard this rumor before, though I wouldn’t be completely surprised if it was true.
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.
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?
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.
Apparently I am too…