Skip to main content

'C' is for Cut - on the Appalachian Trail

In the Five C's of Survival it is recommended that you carry a knife. However after many countless Appalachian Trail gear reviews not many have talked about full tang, folded or any other cutting edge except in passing. One guy said he carried because it made him feel better and another said a friend gifted him a new one because his was too small. Another said he kept his small Gerber in his cook kit to open freeze dried meals. And one girl made mention that she had one and it appeared to be a Victorinox Pioneer.

The one thing that seems to be common is that the AT is relatively safe in that you probably will never go into Survival mode unless you get lost or possibly some other sort of disaster. (unlike the PCT). In fact one thing that is said about Survival is that you need water and for the most part there is water on the AT. If you lose everything except a container you can still scoop out enough water to get back to civilization. Of course you may have the runs but you will have survived.

So for my first section hike from Springer Mountain I'll take my pioneer, hunter pro, and a classic SD for the kitchen. There is a chance I would take my farmer instead of pioneer but only a small one. Why so many? Because I like to make feather sticks and when stressed I like to sharpen my knives.

BTW: I have not seen anyone mention sharpening stones. Again survival is only a few days away at worst.

Popular posts from this blog

Prometheus vs Bosun

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


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…