Despite moving most of my place-of-work’s computing into the cloud, I still rent an ancient computer for less than $1/day to host several of my projects, including this blog.

It’s been pretty stable, but since I have been gently pushing the hardware, the network card has been failing and starting to hang until the driver forces a hard reset.

The NOC techician I spoke with offered to move it to the secondary NIC (network port), and I agreed. He was kind enough to probe that I had an open (unbridged) IP available, so I set the physical NIC to that address, while leaving the virtual bridged NICs alone other than adding the new interface as part of the bond. As the bridged interface was the default gateway, I didn’t have to do anything else.

#ifconfig eth1 x.x.x.x netmask y.y.y.y up
#brctl addif br0 eth1

30 seconds later, it cut across seamlessly when he physically moved the cable. Didn’t even get an alert, it was that fast.

Removed the old NIC from the bridge (just in case), took down my spare IP from the physical NIC, and we’re back and rocking.

#brctl delif br0 eth0
#ifconfig eth1 del x.x.x.x

Had I not kept myself used to managing physical hardware, this would have taken longer.

Devuan released Daedalus (release equivalent to Debian’s Bookworm) in late August, but I generally wait awhile to adopt things which have a large impact on services.

It went smooth-mostly.

I have a FastCGI backend I run the PHP scripts from, as the majority of my content is semi-static. The only reason I still have an Apache based configuration is for legacy purposes- it wouldn’t take much to rewrite to run under something with less overhead, but utilizing FastCGI, I don’t have the same overhead one would running Apache with PHP statically loaded. That broke.

This is the first time I’ve had Devuan entirely fail to pull in an entire package based upon a major revision change (php8 vs php7). It didn’t seem to notice, and happily broke things. It didn’t take me long to repair, but I did have to reintroduce myself to php-fpm configuration; I don’t use it on a daily basis.

It’s been several years since I’ve been active here; my blog has found it’s way into an extended hiatus for years at times.

Before social media was so popular (this from of my blog dates back to 2003!), we used to do our own thing and assume that others would find a way to syndicate it if they were interested in what we had to share.

For many years in between then and now, I’ve changed my personal views on sharing personal data, what is/isn’t worth sharing, and what just doesn’t need to be on the Internet.

I don’t really feel the need to share every single thing I figure out technically, all of my new tools/toys/etc, and for the most part are not as engaged with the Internet as a whole as I once was.

I am not certain what the future holds; I might eventually turn this into a simple format, like it was back in 1999, or I might address this again in the future.

I’m proud for having kept this data alive (and active) for over 20 years, but sometimes I question why I still maintain several servers just for my own vanity domains.

I go out of my way not to post personal things, but one of my oldest, dearest friends passed today during a minor surgery.

I met him in 2004, and we were good friends ever since then. Heck, I still have an HP 2100 printer he gave me (after he accidentally broke mine). We went through the ups and downs of his wifes’ COPD and other health issues, and eventual passing.

Today at roughly 9AM, Randy passed this mortal coil to once again be with his beloved wife. I’ll miss you my friend.

Today, in 1994, a literal backbone of the internet was turned off.

UCBVAX was one of the more common western backbones for UUCP mail, before the internet was on 24/7 – mail would hop through it to get to the final location. Email worked differently then. You’d tell it how to get there, kind of like GPS on your phone, today.

An email hop would look similar to:

stanford!ucbvax!nexthop!gateway!holwegner.com!shawn

Not only was this unwieldy, but it was a bit difficult- you had to know how to get there!

Herein lies the full text of the final statement, by Cliff Frost.

Path: agate!agateway!CMSA.BERKELEY.EDU!CLIFF
From: CL…@CMSA.BERKELEY.EDU (Cliff Frost {510} 642-5360)
Newsgroups: ucb.net.announce
Subject: Network News: The passing of ucbvax
Message-ID: <199408232058.NAA22782@violet.berkeley.edu>
Date: 23 Aug 94 20:58:00 GMT
Sender: usenet
Distribution: ucb
Organization: The Internet Gateway Service
Lines: 81

Friday, Aug 19, 1994, at approximately 2PM, Berkeley Time, a group of
programmers gathered in the old CS department computer room,
fourth floor of Evans Hall, amongst the scattered remains of network
wiring, ancient hardware, ghosts of legends, and general debris, for
a mysterious and moving ceremony; a rite of passage for a computer,
and perhaps its human caretakers. A semiologist could write a thesis
on this event, but here we confine ourselves to the facts.

What actually happened on Friday is that Keith Sklower and Eric Allman
halted the computer that had carried the name of “ucbvax.berkeley.edu”
for the last several years of that venerable name’s history. Then
Kirk McKusick turned the power off, an honor due him as he was the
first person to turn the power on to that particular piece of hardware.

Shortly before this, Keith gave a brief history of ucbvax, and
told us that although the machine was retiring, it would be following
recent local tradition by immediately coming back to work in another
capacity—as a card-key access system controller for the UC Police
department. (See below for Keith’s history.)

Keith’s eulogy was followed by Eric Allman’s moving tribute:

Alas, poor Ucbvax! I knew him, Horatio. A machine of infinite jest, of most excellent software. He hath borne my mail in his queue a thousand times. And now how abhorred in my imagination it is! My gorge rises at it. Here hung those disks that have spun I know not how oft. Where be your news now? your dialins? your routes? your flashes of congestion that were wont to set the department on a roar?

The assembled multitude of T-shirted and blue-jeaned programmers
(more than a few of us also sporting just a touch of silver in the
hair) applauded enthousiastically, then dug into the carrot cake
and diet pepsi generously provided by Keith.

Cliff Frost Network Services

ps Keith’s brief history:

In the summer of 1978, the computer science department took delivery of the campus’ first Digital Equipment VAX computer, obtained via a grant from NSF (due in large part to the efforts of Prof. Richard Fateman). In fairly short order, it was running a variant of UNIX developed by Bell Labs. (Local CS people were interested in adding virtual memory support, which ATT UNIX lacked, which eventually led to the widespread interest in BSD, but that’s a different story). The people at Bell Labs offered to have their computer call up ours in order to facilitate research collaborations, using the UUCP protocol. We had to choose a node name, and “ucbvax” seemed to follow their naming conventions. Netnews and the birth of usenet followed closely. After a couple or 3 years, the mail-handling and news functions of the departmental vax were chewing up more than half the cycles, so it was decided to segregate those functions onto a separate machine (when the opportunity arose). So, “ucbvax” became VAX/750 devoted specifically to those functions. For a long time, it was one of two gateways between the ARPANET and the Berkeley Campus. After the load on ucbvax-the-750 began to exhaust it’s capacity, there was talk of replacing it with some flavor of SUN workstation, but a DEC sales person got wind of this and thought it would be much better for DEC if ucbvax were to stay a vax, and managed to “upgrade” the 750 to a decstation 3200, which was its final incarnation. At the time it was turned off, ucbvax was the last operational vax in the computer science department, so to stretch the truth only a little, it was both the first and last VAX in the computer science department at UC Berkeley.

pps The actual power-down was delayed by about 20 minutes from the scheduled 2PM time, because of having to move about 74 pieces of queued email to another machine for eventual processing.

ppps Although ucbvax’s IP addresses are retired, there is still a significant amount of email traffic being supported under that name, rerouted earlier in the day (through the magic of MX records) to a machine supported by Information Systems and Technology’s department of Data Communication and Network Services. This computer is named, with full cognizance of the irony, “nak.berkeley.edu”.

ucbvax left us before the world wide web, but remains a memory to those of us who used, but never had direct access to it. I hope you’re still scanning keycodes, UCB – the Internet would never be where it is without you.