Skip to main content

winter hike gear review

I was planning a hike in Nevada's Incline Village. I started researching my gear choices.

Base layer is Columbia base layer with omni-heat in both the shirt and leggings.

The green pants are just some hiking pants that I planned to use in Florida but tried in the winter. The mid layer is a Columbia softshell with omni-heat.

The outer layer is a froggtogg that is waterproof but with no insulation.

Lastly Columbia omni-heat glove liners, american flag schemog, baliclava, and ski gloves.

Lastly I had a CamelBak 18L pack with some essential emergency gear and some basic food.

I tried this setup in a number of different configurations. I found my core temperature swinging in all directions. At one point I was completely soaked. Also I found that it was not comfortable to just stand still. This setup was effective when moving.

My first hike was a FAIL in that we did not get very far and so during the second hike I skipped the outer layer and stuck with the base and mid layer. But since I was moving and generating plenty of heat I found myself venting the extra heat through the collar. The only challenge might be that the midlayer is not very waterproof.

And my only complaint about the CamelBak is that the straps are small.

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…