Skip to main content

review Marmot Kompressor Plus - not so good

Here is my list of stuff:

  • 1L SmartWater
  • 1L water filtering bottle
  • 1 pkg mashed potatoes
  • Fleece Sweater
  • poncho
  • hammock
  • pretzels
  • protein bar
  • 2 pkts peanut butter
  • 2 pkgs GU
  • spoon
  • headlamp
  • compass
  • microtowel
  • hard candy
  • tarp
  • cordage and bits
  • bivy
  • first aid kit
  • water kit
  • stove and cup

my stuff

Here is yesterday's pack, a Klymit Stash 18. Everything fits. Kinda snug. Only the main compartment and the one pocket. Just the drawstring at the top... and it's black. There is a good chance that the contents of the pack is going to be warmed and since the water is inside it's going to be warm too. In my last experience with a hydration bag I found the contents of the straw to be warm.

Today's pack is a Marmot Kompressor Plus #24940. Everything fits and there is plenty of room for a lot more gear. Since it's the same gear as the Klymit and it weighed in at 10lbs this pack is the same and the manufacturer suggests the limit is 20lbs but after wearing it around the house the Marmot has serious limitations.

  1. The platypus meta bottle is made of a silicon and sticks on the side pocket. It's hard to get in and hard to get out. I tried putting it in a ziplock bag and it was easier but only barely because the pocket was not actually deep enough.
  2. I had a similar challenge with my 1L Smartwater bottle. Except here the bottle is slippery and tall. The higher center of gravity allowed the bottle to flip flop.
  3. The front and hood pockets were nice for snacks and urgent use gear like compass and poncho.
  4. I need to complain about the straps again.
Well, after some gear adjustment I was able to get the base weight under 5lbs and the compression straps are functioning better. Also the pack feel better and the sternum strap is also comfortable. And I managed to get the bottles in the side pockets. But without contents to give it structure it's floppy and not very functional.

I kinda wish I had purchased the Klymit 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).


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…