Skip to main content

I just realized I hate computers

Not really but there are aspects of computers that I no longer like or even appreciate and while I think I have evolved over time there are elements of the industry that have not learned a damn thing.

In the early 1980's I reversed engineered Dancing Demon in order to figure out how they accomplished the speed that was simply not there in BASIC.


This program used BASIC as a sort of bootloader for raw byte code which is where the performance came from. Later I would spend a lot of time in CPU and board design, copy protection, simulators, device drivers, TSR, operating systems, BIOS and maybe some other things I've long since forgotten.

  • Transec systems I used an ICE machine to debug copy protection and bypass it. Later I wrote low level DOS extensions to the filesystem.
  • IBM MSD had used for a number of systems including a highspeed simulation of a cluster of single board computers, BIOS for it's Artic Coprocessor; later I moved to the OS/2 team and worked on Video Drivers, AIX for PC, and WorkPlace OS Presentation Manager.
  • At Core International I implemented the disk and tape device drivers connecting the company's hardware to OS/2.
  • NaBanco I implemented a terminal messaging network as a DOS TSR.
What I'm saying is that over the years I have been writing code at a low enough level to understand the hardware and the operating systems. AND I LOVED IT. Tinkering at such a low level was always a thrill. It was especially fun when debugging a problem required an ICE machine, logic analyser or oscilloscope.

Fast forward 35 years; rotate in my chair to my workbench and I see a Dell C6100. It's quiet now and it might remain that way for the time being and longer. Between the IPMI, BMC and dated BIOS I've realized a few things.

These clunky machines are not the future. The cases weigh too much. The power supplies are too big. The Fans are mechanical, noisy, and prone to failure.
And this thing(chip) costs $9.
While the Dell C6100 cost $300 that was not it's original retail price. But regardless of it's original source, likelihood of a MTBF failure, it still requires plenty of sweat equity to get it up and running. More than I'm willing to put into it. I have moved beyond my interest in all things hardware. It also means that, at least Dell, has not learned anything about it's own hardware. The BIOS while simple is complicated and not necessary.

I think I want to use my phone as my computer.

And something similar on the serverside. Maybe some stackable Chip.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…