What’s the value of this advice? You can google the same thing in about 2 minutes. People usually expect real-world experience.
nitrolife
- 0 Posts
- 12 Comments
Joined 3 years ago
Cake day: June 28th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
because it’s pretty hard to recommend anything you don’t use. Seeking advice on a distribution in geek forums, therefore, is a losing plan right from the start. It’s smarter to install whatever you want and then come to the forums with your problems.
1·3 months agoIf you’re installing an HBA at home, it’s better to immediately install something like a Noctua NF-A4x10 on it. You should also immediately check the type of hardware initialization. If the system boots into EFI and the HBA is old and only supports BIOS, there may be problems. Otherwise, everything works perfectly with almost every device.
I’ve been running all my servers and my work computer on Arch since around 2018, ever since Ubuntu started shoving snaps everywhere. Even the instance I’m writing this from is running Arch. Overall, everything is great. The instance has 98-99% uptime. No issues with the work PC either.
UPD: While rereading the post, I remembered that rabbitmq was recently broken in the repositories. But everything was solved with a two-minute rollback and blocking of the version in pacman.
UPD2: I build packages with my hands periodically. It’s not like I haven’t done the same thing on Ubuntu or CentOS. On Arch make PKGBUILD really more easy then spec file for CentOS or deb structure for ubuntu. On Ubuntu this is really awful.
Never mind what’s ideal, in reality, one of my servers is running on a Core 2 Duo T7600 and when I installed ubuntu on it, it took 24 minutes to boot due to the unzipping of the base snap image in ubuntu server. Older hardware does not become faster just because os requirements change. And yes, I left ubuntu as soon as snap came out, i think that was 2018.
UPD: and of course I’m not going to change one of the local servers just because Canonical decided to release another system. Thanks. For 20 years the processor has been routing packets and will do so for another 20 without any problems. Just switched to another OS.
SNAP in the recommended packages of the ubuntu-server metapackage. Ubuntu installs all recommended packages by default. So SNAP is in the server installation, moreover, it can’t even be simply removed without completely blocking in apt policy.
SNAP also doesn’t work well with old hardware because of compression. It’s ironic to recommend system riddled with incompatible compression to someone who explicitly wrote in a post that they would be using outdated hardware.
If you’re planning to use old hardware for hosting, don’t use Ubuntu. SNAP will kill performance.
So your choice is Debian.
P.S. VPS is already a Virtual Private Server and you can’t install ProxMox or any virtualization on it. If you want experiments, look into containers.
In any program, you still have to execute a challenge somewhere. No program will issue certificates without that. In the case of certbot, you can simply write a small post hook that will transfer the certificates to cloudflare.
Just don’t expose SSH to internet. It’s a complex protocol with many CVEs. And you realyy don’t need access to SSH from anywhere. Replace access from ineternet to a WireGuard tunnel that has almost zero attack surface area and properly configured iptables rules. And that’s it.
I think the problem has been slightly exaggerated. If you’re not hosting several dozen services, you can reduce your attack surface down to one Nginx server. For an even stricter setup, just enable mTLS.
Yes, I installed an LLM at home. I use it for many useful things:
I have a RX9070XT and llama-swap to switch models on the fly. I’m thinking about installing a second RX9070XT so that I don’t take away the translation capability from my lemmy instance while I stress the other neural network with other tasks.