Skip to main content

MacBook Air with 64GB disk can't to shit

I've paired my MBA down to the bare essentials and it's just performing like crap. No matter what I do every week I spend a few hours trying to delete more and more less essential applications. One thing that cooked my goose is that one of my deepest dependencies is XCode and I had uninstalled it. As a side effect I would get random popups asking me to reinstall XCode and the command line extensions. Just no fun at all even though I had anywhere from 5 to 15GB free depending on what was in the trash.

Today I decided to start my SSD upgrade but that did not go well. I performed a time machine backup and while it seemed to be backed up it had not. The restore failed. So I had to reverse everything I had performed and do another backup onto a different disk.

The checklist looked like:

  • timemachine backup everything
  • install the new SSD
  • power up + CMD+R
  • format the new drive
  • install the OS and make sure it's the same version
Same version?
  • log into the machine with a new (different) temporary userid
  • launch finder and navigate to apps/utilities
  • launch the migration app and follow
Different version?
  • Log into the machine with a new (different) temporary userid
  • upgrade the OS to the same version as the timemachine backup
  • you'll reboot a few times
  • log into the machine with a new (different) temporary userid
  • launch finder and navigate to apps/utilities
  • launch the migration app and follow
when restoring from the timemachine backup there is are some options to restore users, delete users and so on. Read it carefully.

UPDATE It has been a few days since the drive upgrade. The machine is doing the same work it was doing before the upgrade. Only one app seemed to be wonky with two instances running at the same time. I hope I deleted the correct one.

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…