Ariel Millennium Thornton @arielmt@computerfairi.es

The only FreeBSD architecture still vulnerable at the OS level is i386 (32-bit Intel CPUs), which will make vintage computing interesting.

My Palm IIIxe is also not affected by the Year 2038 problem. Instead, it's got different time bugs that mean I won't be able to keep my radical leftist agenda on it past 2032.

Time bugs!
The Doctor's new nemesis!

https://en.wikipedia.org/wiki/Time_formatting_and_storage_bugs

Today, January 19th, 2023, is the fifteenth anniversary before the Year 2038 rollover, when the number of seconds since the Unix Epoch (1970-01-01 00:00:00 UTC) becomes too large for a signed 32-bit integer.

Unready applications dealing with long-term planning or scheduling, even those running on ready operating systems, are already feeling the effects, for example, by predicting children born today to graduate high school in 1903.

https://en.wikipedia.org/wiki/Year_2038_problem

tl;dr: til '--exclude-dir=..'

Related, I once accidentally pwned an entire college lab of NeXTstations without touching a keyboard.

My home directory's ownership got messed up, the sysadmin was struggling to catch all my files in the fix commands, and I pointed out that my home dir's dotfiles needed the fix as well. The sysadmin got bit by the same ".*" bug on that 1992 day I got bit by today, but on the chown command.

I love needing to grep thousands of files in 50 dot-directories recursively, and my first clue the 50yo ".*" gotcha bit me is a read-permission error for a file in an ancestor directory after a long wait.

i have spoons again

@SteelWool Now it is. The server ran out of space, and I had to take it down again a few times to migrate and verify data. Sorry about that.

@miserable_complex864 Yes. The server ran out of space, and I had to take it down again a few times to migrate and verify data. Sorry about that.

Mere days after the winter solstice, it's unseasonably warm outside. However, it didn't feel quite *this* warm.