Live data from Hacker News

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

crocidb.com

121–130 of 241 posts

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

#121
post #119
post #62

The biggest mistake I made was high uptime. arjie.com was up for 10 years plus on a Hetzner VPS so that by the time they wanted to sunset the machine underlying I had no idea what my teenage self had set up. I have the backups but the site hasn’t been up in a decade… Nowadays I build things so that they move and I have moved things about a bit so I know they work.

This reminds me of Ise Shrine in Japan, which is completely dismantled then rebuilt every 20 years. This is top of mind because I recently read Breakneck by Dan Wang. He makes the case that this practice of rebuilding the shrine preserves knowledge that would otherwise have been lost to time. Wang contrasts Ise Shrine with Notre Dame, where rebuilding the roof is apparently quite difficult, perhaps in part due to the…

Thank you for the recommendation! I love that reference, and particularly because I am fond of the story of the shrine for a different reason https://wiki.roshangeorge.dev/w/Constancy_Preference#Concept...

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

#122
post #27

I, too, have a server running 16.04 that I'm afraid to update. It currently has an uptime of 1281 days... at this point I'd feel bad rebooting it

What is there to be afraid of? Don't you have backups?

Also, debian/ubuntu systems can easily be setup to auto update and reboot on a regular basis, leaving you manual maintenance only for the larger version upgrades.

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

#123
post #117

Earlier quoted context omitted.

That's fine, it's not really a crusade. Just my opinion about the right infrastructure for the right use case informed by the objective reasons I gave. If doing more work with more headaches for a solution that costs more and performs worse is your jam, then power to you.

You’ve written nothing objective.

Sure I have. Let me help you by recapping:

1. VPS costs more money. CDN is free for all intents and purposes.

2. VPS has worse availability even when run perfectly.

3. VPS requires more monitoring and maintenance.

4. VPS presents far greater security risk.

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

#124
post #120
post #62

The biggest mistake I made was high uptime. arjie.com was up for 10 years plus on a Hetzner VPS so that by the time they wanted to sunset the machine underlying I had no idea what my teenage self had set up. I have the backups but the site hasn’t been up in a decade… Nowadays I build things so that they move and I have moved things about a bit so I know they work.

Sometimes I leave Architectural Decision Records for personal projects. It feels silly but it honestly comes in handy more times than expected

I keep them embedded in the codebase or an artifact right next to the source.

And the key thing is that i dont need too many details at all. A few cues and its all back in my head.

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

#125
post #117

Earlier quoted context omitted.

You’ve written nothing objective.

Sure I have. Let me help you by recapping: 1. VPS costs more money. CDN is free for all intents and purposes. 2. VPS has worse availability even when run perfectly. 3. VPS requires more monitoring and maintenance. 4. VPS presents far greater security risk.

You don’t need to recap your subjective experience, it’s on full display.

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

#126
post #53
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?

I would say NixOS, where it is trivial to switch across releases, run software from different releases, and perform rollbacks. I have been running NixOS on several servers for more than a decade. No reinstalling, upgrading, or any breaks whatsoever.

I have run NixOS for about eight years on server and desktop and been a nixpkgs maintainer. Yes, most of the time I would agree with you. The fact that you get warnings in the terminal for a lot of incompatibilities and changes when upgrading is a really nice touch and upgrades tend to be smooth. I do not use rollbacks much, but when you do need them they are really handy. Having every configuration in a single file makes you more bold to play around with configurations, which felt really empowering when I first got into NixOS, as I knew it could roll things back and I no longer had to keep notes on how each box was set up to refer to in the case of a reinstall or migration.

However, I have had one machine become unbootable as it could no longer mount its encrypted disks after an upgrade, forcing me to mount a rescue image remotely, mount the disks manually, lift the data out, and do a complete reinstall (migrated the box to OpenBSD at that time). Similarly, NixOS once messed up systemd (or vice versa) so badly that I could not even reboot without forcing a power cycle. Lastly, I have had a package break for my use cases by maintainers enabling so many custom flags by default for a package that they enabled one I have never seen enabled by any other packaging team and that then broke RTSP in "funny" ways. Ubuntu did tend to break things like graphics between releases at times back when I used it, but I have never had any other distribution or operating system throw curve balls like the three things I mentioned here.

My general impression of NixOS is that the core is solid, but that nixpkgs just has such a large number of things that it supports that the maintainers struggle to test them all and can not anticipate the interactions between all the packages and options. The default Julia package being so broken that it produced incorrect mathematics due to nixpkgs' insistence on allowing you to swap out the Blas library and also having turned off the unit tests for example springs to mind. This was shipped to end users for a long time before I noticed it by accident by enabling the unit tests and stepped in to clean it up. It all feels very "Gentoo", which was indeed an inspiration for NixOS by the way.

Now, return to that last sentence in the first paragraph that I wrote about feeling empowered to tinker, ultimately, I feel like you should try to resist that urge as it is what pushes you into the untested fractal of possible configurations that NixOS allows you to explore. My other main operating system is OpenBSD, where the mentality is "Stick to the defaults or suffer the consequences"; with NixOS, I feel like everyone's box is more or less a tailored suit, which comes with both its ups and downs.

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

#127
post #117

Earlier quoted context omitted.

You’ve written nothing objective.

Sure I have. Let me help you by recapping: 1. VPS costs more money. CDN is free for all intents and purposes. 2. VPS has worse availability even when run perfectly. 3. VPS requires more monitoring and maintenance. 4. VPS presents far greater security risk.

u/grebc if money is subjective to you, then you're free to send me some as you objectively won't miss it.

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

#128
post #81
post #62

The biggest mistake I made was high uptime. arjie.com was up for 10 years plus on a Hetzner VPS so that by the time they wanted to sunset the machine underlying I had no idea what my teenage self had set up. I have the backups but the site hasn’t been up in a decade… Nowadays I build things so that they move and I have moved things about a bit so I know they work.

"The biggest mistake I made was high uptime" Quite. I'm old enough to remember machine uptime being a badge of honour. However, being older and not really wiser, I look for service uptime these days. Yes we did have similar back in the day, that's why MX and the like DNS records exist. Old school clusters were pretty esoteric but the lessons were learned (split brain n that) and that's why we still argue the toss wit…

There is something like live patching.

One reason mainframes and micros are still around us, is that you can change almost everything between hardware and software without downtime.

It is also available in commercial surviving UNIXes, and as paid for feature in some Linux distros, although not to the extent that those grandparent systems are capable of.

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

#129
post #62

The biggest mistake I made was high uptime. arjie.com was up for 10 years plus on a Hetzner VPS so that by the time they wanted to sunset the machine underlying I had no idea what my teenage self had set up. I have the backups but the site hasn’t been up in a decade… Nowadays I build things so that they move and I have moved things about a bit so I know they work.

> The biggest mistake I made was high uptime. arjie.com was up for 10 years plus on a Hetzner VPS so that by the time they wanted to sunset the machine underlying I had no idea what my teenage self had set up. I have the backups but the site hasn’t been up in a decade

LLMs have solved this problem, they’ll happily deal with the software archaeology on your behalf. This is the kind of task they really excel at.

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

#130
post #128
post #81

Earlier quoted context omitted.

"The biggest mistake I made was high uptime" Quite. I'm old enough to remember machine uptime being a badge of honour. However, being older and not really wiser, I look for service uptime these days. Yes we did have similar back in the day, that's why MX and the like DNS records exist. Old school clusters were pretty esoteric but the lessons were learned (split brain n that) and that's why we still argue the toss wit…

There is something like live patching. One reason mainframes and micros are still around us, is that you can change almost everything between hardware and software without downtime. It is also available in commercial surviving UNIXes, and as paid for feature in some Linux distros, although not to the extent that those grandparent systems are capable of.

I’ve long wanted that amazing uptime and virtualization and huge I/O and all that cool stuff mainframes offered, but on the desktop or in the closet, with modern CPUs.

I think I’m gonna hafta keep waiting...

Post reply on HN