Show newer

It is interesting to me that ULTRIX 4.5 -- from 1995 -- still has a bunch of executable binaries in /etc. It also has no /sbin, and most of what I'd expect to be in /sbin is in /etc, much like Unix v6/v7.

I remember that Linux machines had MAKEDEV and a couple of other scripts in /etc in that time frame, but I think by 1995 /etc on Linux was almost exclusively data.

An aperture card! Used as a very early image tagging/sorting system, you'd have microfilm mounted in a punch card, so you could have a regular punch card organizer/sorter find your images. The DoD loved them because they could store tons and tons of engineering blueprints in an organized, computer-sortable and -searchable way.

Image source

Why yes, yes I _am_ compiling all of CDE on a first gen Raspberry Pi model B rev 2. Why do you ask?

No, I don't expect it to finish before tomorrow.

Looks like Debian dropped the X font server. :-(

A DEC VXT 2000 graphics terminal from the early 90s. Basically a diskless VAX netbooting an X server.

17 days in, maybe I should have used more than one core?

Show thread

@freakazoid @jens @jauntywunderkind420 @rubenerd We need to remember that TCP is an attempt to emulate a serial byte-pipe over an unreliable network; that is, it's whole reason for existence is to preserve the semantics of the leased lines that the Internet was first built upon.

UDP was an encapsulation that basically exposed raw IP to clients, with the addition of a port to allow for application multiplexing over a single network cable.

It seems to me, as with people who saw fit to route SSH over HTTP (not even joking) because some network operators are too lazy to manage ports on behalf of their users, we have yet another network-stack-on-a-network-stack solution with the datagram extension. You're just re-inventing UDP ... on top of (ultimately) TCP.

You're not alone, though; the BEEP (nee BXXP) protocol attempted to do the same exact thing. It was summarily dismissed by the community as needlessly redundant.

When will people just bite the bullet and tell network administrators, "Look, you have to manage ports. Do your F'in job."

Protocols like QUIC and BEEP are solving non-problems; or, more precisely, problems of their own creation. I wholeheartedly believe that it's actually easier to push and adopt protocols like QUIC and BEEP than it is to fix the root cause. But, it only offers asymptotic levels of benefits. Eventually, it will cease to be economical to do so. But, by then, it will be too late. Infrastructure will have become immutable by then.

In my opinion, it is our duty as technologists, programmers, and systems architects to push back on this unchecked re-encapsulation HARD.

Them: I get the appeal of Free Software, but sometimes I want something that Just Works™, without needing to fuss with it.

Me: M-x emacs-uptime

Emacs: 128 days, 21 hours, 26 minutes, 26 seconds

Reading Steven Bourne's The UNIX System, I noticed in an example that the Bourne shell read command can do destructuring binds. I'm sure I knew that at one point in time, but I had surely forgotten it ... and I have a lot of shell scripts with unnecessary set $line statements.

Did Freenode really just dump EVERYTHING and tell me to re-register?

Been cracking Stephen Bourne's password from his 1983 book The UNIX System for a few days now because ... because.

The default binding of C-c C-v for the org-babel prefix keeps causing me to C-x C-c since it's exactly one position off.

Show older
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko