Skip to main content

Backpacking vs Hiking

Recently I read an article which tried to compare backpacking to hiking based in the length of time on the trail. I take issue with that comparison because AT, CDT, PCT and other thru-hikers travel at least 2100 miles. Similarly another writer suggested that a section hiker traveled a minimum of 500 miles. Furthermore the first author also addressed food, food quality, and cost. Apparently one or the other thinks that freeze dried meals are too expensive and another talked about how his 8 oz isopro only lasted 4 days. And yet another addressed the shelf life of various foods.

On the one hand I'm frustrated because I'm new to the concepts and execution but my intuition is screaming from every vantage.  For example, freeze dried Mac-n-Cheese only requires boiling water. Getting to a boil takes about 4-6 minutes and about 1oz of alcohol. On the other hand Craft with regular noodles requires a 9 minute boil which will take at least 3oz more fuel. This is going to translate additional weight for fuel.

In their packaging....
  • Mountain House - 8oz, 3 servings, 320 calories per serving, 
  • Annies's - just under 8oz, 2.5 servings, 260 calories per serving
  • Cliff Bar 250 calories
  • Nutella 200 per serving (2 tbl spoon)
  • Mixed nuts 200 calories per serving
  • harvarti 100 per serving
Annie's calorie measurement likely includes the butter and milk you have to add and the Mountain House does not have to be adjusted. 

Looking at this page I have determined that I will burn a minimum of 279 calories per hour. I'm setting a goal of 12 miles per day @ 2mph. That means I need a minimum of 1700 calories a day for the activity. My maintenance calorie level is about 1800 per day accounting for sleep cycles and recovery I probably need between 1200 and 1800.

So let's error on the side of caution and say I need 3000 calories a day. The Mountain House MNC provides nearly 1000 calories in one meal. The bigger challenge is getting the balance without cooking.

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…