Live data from Hacker News

Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

crocidb.com

21–30 of 241 posts

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#21

I'm in the same boat. I have 2 old servers that I let get "too" old, and now I'm afraid to touch them to update them. However, with some of the shenanigans that the Linux distributions are pulling around age verification/attestation, I'm considering bailing on them entirely. Note, I did try Artix, but when it broke last week after a restart (in which evidently something had gone wrong with an earlier kernel update),…

My servers/VMs typically run either FreeBSD or Alpine. A Debian here or there where needed (proxmox, VPS that doesn't support Alpine, corp stuff, etc).

I've also got a couple of test systems running Chimera - going to wait until it hits stable before relying on it too much though. Experimenting a bit with AerynOS too.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#22
post #15
post #4

Slightly off topic: What's currently the free Linux distribution with the longest support cycle? For a while I used CentOS 7 on all of those small VMs, because it got security updates for a really long time. With minimal risk of breaking things on updates. PS: after a bit of research Alma/Rocky Linux are probably the best choices for now. 10 years of support. But are they maintained well?

> But are they maintained well? Alma has a few affordances as it's no longer RHEL source compatible, which means it could ship priviledge escalation fixes with new kernel updates faster. Rocky responded with an extra, optional to enable, security repo to provide mitigations to the exploits while waiting for RHEL to downstream. Look pretty well maintained to me. If only judging by recent events.

Thanks!

I don't care much about being fully RHEL compatible, or no ABI changes at all. I just want a system that gets security fixes quickly with as little chances of breaking things as possible.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#23

I'm in the same boat. I have 2 old servers that I let get "too" old, and now I'm afraid to touch them to update them. However, with some of the shenanigans that the Linux distributions are pulling around age verification/attestation, I'm considering bailing on them entirely. Note, I did try Artix, but when it broke last week after a restart (in which evidently something had gone wrong with an earlier kernel update),…

> However, with some of the shenanigans that the Linux distributions are pulling around age verification/attestation...

You've been misled.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#24
post #4

Slightly off topic: What's currently the free Linux distribution with the longest support cycle? For a while I used CentOS 7 on all of those small VMs, because it got security updates for a really long time. With minimal risk of breaking things on updates. PS: after a bit of research Alma/Rocky Linux are probably the best choices for now. 10 years of support. But are they maintained well?

Probably Debian or Ubuntu. The question is...why do you care that much? I've upgraded Debian stable (both pure and with some cherry-picked backports) and Ubuntu (non-LTS and LTS) systems in place and rarely broken anything, for years and years. When stuff has broken it's been a quick google and then slapping myself for not having read the upgrade guide. I do generally wait about 2-3 weeks before upgrading, giving tim…

I had unattended-upgrades cripple our VMs

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#26

Boggles my mind that people pay money to host hugo static sites on a VPS, which is objectively inferior and harder in every meaningful way compared to hosting for free on GitHub pages or S3+CloudFront.

s3 + cloudfront takes approximately 2 extra steps every deploy, and about 10 extra steps that are easy to screw up at setup time. It's not a trivial drop-in, but yes, once it's done it's _really_ done.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#28

Boggles my mind that people pay money to host hugo static sites on a VPS, which is objectively inferior and harder in every meaningful way compared to hosting for free on GitHub pages or S3+CloudFront.

some people (myself included) like hosting their own stack for fun or for learning.

There's additional concern with tying your work to something like github it makes it more of a pain to pull it off and put it somewhere else.

I'm not really sure what you mean by objectively inferior. It's trade offs like everything in this field.

As far as harder, I don't really think the lift for a personal VPS is that high. Again it's a fun hobby project for most. It's fun to run your own stack.

If you want to opt into the github cloudflare goodness that's fine they're good services but I wouldn't say it's better or degnegrate others for not doing that.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#29
I enjoyed my foray into trying FreeBSD for my personal server. There's something cool, clean, simple and "punk rock" about it. But I gave up as my main pain points were:

- PM2 was buggy on FreeBSD, which I used to manage my processes

- An alternative, using `rc.d` to run daemons was just so hard to get logs working.

- The firewall required too much self configuration to get it right with all the best security practices (ie. What does one do with ICMP.) I was missing something like a template with the defaults that come with UFW, for instance.

Re: Blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

#30

Boggles my mind that people pay money to host hugo static sites on a VPS, which is objectively inferior and harder in every meaningful way compared to hosting for free on GitHub pages or S3+CloudFront.

s3 + cloudfront takes approximately 2 extra steps every deploy, and about 10 extra steps that are easy to screw up at setup time. It's not a trivial drop-in, but yes, once it's done it's _really_ done.

You can make it zero deploy steps beyond git push with CodePipeline, and vibecoding makes the annoying config setup trivial if you know like 20% of what you're doing. There is really zero reason to be using a VPS for this unless you hate money, want your site to choke during once-in-lifetime opportunities to go life-changingly viral, and like contributing to the global population malicious botnets.
Post reply on HN