Skip to main content

review klymit 18 backpack

In a recent post I write about 1-day and 2-day load out. The 18L pack I was testing with was from Klymit. The pack is available from Amazon and at a pretty good price, however, there are some things you need to know.

First, there is only one pocket on the back; and it's a small pocket. I managed to fit a few essential items. Spoon, 4 packets of GU, micro towel, compass and whistle. When on the trail there should be room for my keys(no hook) and wallet.

Therefore the first deficiency is the lack of side mesh pockets for carrying water. To be fair the back is hydration bag capable but my position is that hydration bags are a risk. Next, the presenter suggests that the pack can hold 20lbs of gear. That might be possible based on the materials, straps, and construction; however at 9.4lbs the pack was just barely comfortable. And so the next issue is that in the demo the stash rode high on the shoulders, however, most professionals recommend low on the hips without bouncing. Lastly, the narrator indicated that the pad could be removed and used as a seating pad or pillow. I imagine that is true, however, as I was fiddling with the air-frame it seems that I would have to dump the contents of the pack in order restore the air-frame. There is no mention of weight capacity and since it is essentially an air mattress there is no mention of a ground sheet which would be a good idea if you have to dump the contents.

And a few last minute nits:

  • there is a draw string at the top but the pack does not have a hood. While it might be water resistant the gathered material still leaves room for rain
  • the air-frame is cool on my back
  • the chest straps are pesky and there is no whistle.
  • I bought the black but I think I would have preferred the yellow. There is something to be said for being able to see inside the pack even though it's small enough to limit the number of items. Black absorbs heat and is less visible
  • I decided to leave out my Thermarest sitting pad and and add a footprint. I have considered using my Thermarest instead of the mattress.
  • I had to change my loading strategy. Instead of least used first I went with heaviest first.

It's not a bad pack I just don't like it enough to buy the yellow.

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…