Skip to main content

where did the 21.5 pounds come from?

My new waterproof pack arrived yesterday and I decided to load it up this morning and see what the weight was. You cannot imagine my disappointment when I read the display: 21.5 pounds.


This pack contains everything for an overnight and so a few things were left out.



I did not pack any spare clothes, spare cordage, rain jacket (poncho was sufficient). I will have to add the spoon and trekking poles(not pictured) back in.

Opening the pack


Shelter - tent(750g), footprint(150g), butt pad(50g), mattress(350g), pillow(50g), poncho(300g), bivy(450g), hat, sunglasses, schmog, gloves(300g)
water - 2x 1L(1100g each), water filter and purification(350g)
food(750g)
cook kit(650g) - 3.5oz IsoPro, ION stove, Stanley pot and 1 cup
waste(50g) - ziploc, trowel
survival(250g)
misc(750g)
pack(1133g)

**weighed on an analog kitchen scale and rounded to the nearest 50g.


I included hand sanitizer in my kit because I do not want to transfer germs from my hands to the finished water. It might be a good idea to have a proper general purpose bag because the sanitizer should also be used when cooking or eating.



The stakes and cordage need to go into a different bag. Many of the other items are going to be on my person. Imagine being separated from my bag for only a moment and getting lost.


Instead of toilet paper I have compressed poop towelettes (just add water). I'm not carrying out my poop but the towelettes should be close to the sanitizer and the waste bags. The flashlight should always be on me. I have hand soap in this bag but that would mean giving up some processed water to wash my hands. Insect repellent needs to be some place accessible.


99 of 100 times I'm going to use the lighter. I just tried a water test and the lighter barely passed. So the fero rod should go in my fire kit although a pezo starter might be better than a lighter.

** the lighter is a joke. Once it got wet it would not hold a flame at 50% power and at 100% never held the same level. I tried compressed air and running the flame at 100% in order to evaporate any remaining water but nothing worked.


This is a lot of food for an overnight. The one thing I like about this packaging is that when on the trail the package is the pot and so there is little or no cleanup. However, unless hiking 10-20 miles the calories for a double serving is pretty glutenous. I may need to consider a cozy and a freezer ziploc bag. Depending on rationing there is an overnight and snack here.

The rough estimate on the combined weight is 8533g or 19lbs. Which is pretty close to the 21.5lbs that I got from the bathroom scale and within an acceptable margin of error. Now consider that every 50g is another 50g.

Assuming that I want to get to 15lbs or 6803g that means I need to lose about 1700g. And if I want to get to 10lbs for a day hike I need to get to 4535g shedding over 50% of the weight.

The lighter does not weigh much, I have two of them, but as a backup to a fero rod when I need fire. I'm better with a fero rod and fatwood. ... to be continued ...

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…