Skip to main content

buyers remorse the Appellation Trail

I'm not doing the Appellation Trail (AT) any time soon but there are some ideas that I have been reading that leave me with knife buyers remorse.

I have been collecting knives since I started going head first into self-training bushcraft. I'd watch a few videos and then review some of the equipment people were using and then watch a dozen knife and tent reviews. And then the boxes start rolling in from Amazon.

I recently wrote about my knife collection. Some were complete shit. In retrospect they are still complete shit but I also do not need 10 Mora knives. One or two would have been fine and I should just have stopped there.Supplemented by a SAK.

In the meantime I watched a vlog


and although the conclusion is that hammock camping is fun/preferred for the presenter he was quick to explain that it's [a] expensive [b] heavy [c] complicated [d] difficult to get consistent.  I've, separately, commented that hammock camping is not permitted it all campgrounds and that there is a danger in hammock camping with respect to hanging on dead trees or weak roots and so on.

Back to the AT... [a] some segments of the trail do not permit ground campfires [b] in some places fires are only permitted in the fixed shelters [c] and in some segments tools like saws or axes are not permitted. I recently posted that many US National parks to not permit open fires and those that do are only in designated pits.

The author went on to say [a] many thru hikers do not cook on the AT. They bring water and foodstuffs that do not require cooking. [b] he went on to mention things like Hostels which leads me to believe that while water can be found on the trail you're likely to exit the trail to get fresh water. Without heat to purify water you'll need chemicals or a filter system.

Anyway, back to knives.

With yet another place where fires are not permitted my knives are kinda useless. I really only need the few where I can practice my skills in the backyard or the campground fire pit.

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…