Skip to main content

The case for a disposable or dispensable hiking kit

I have achieved a level of super pack envy or hiking frustration I'm not sure which. Take a look at these packs.

Both of these packs are considered day packs. They are made from lite material and yet are fairly inexpensive. Under $50. After just a few uses they have started to develop hot spots. The Marmot was leaned against a slab of coral rock and it started to SHRED the material. The G4Free is constructed from a stronger nylon material, however, like some nylon webbing the ends where things are sewn SHRED easily. And there are a few places where there are hotspots.

I suppose I'm about to contradict my own hypothesis... Considering the "ratio" between a SOL bivy and a military or OR bivy is there a backpack in the SOL variety? First of all It would be interesting to know if someone had hiked the AT, FT, CDT or PCT with nothing but an SOL shelter, blanket and bivy. All I know is that it was in the 60s on Fri and in the high 80s last night. I was just getting acclimated on Friday when Saturday cooked me. I tried to use my sleeping bag line but it kept me too hot on Sat and I could not get comfortable on Friday as we slept on a torso length mattress on compressed coral.

So while this was car camping at it's finest... I used my day pack to tool around town. And of course it was filled with useless junk

** while researching... seems SOL has a survivor pack. It's not what I'm looking for but the subject seems a little deflated. There is a problem with the ROI formula when one considers the merits of cuben fiber and zpacks or simple packs.
Boats are nothing but holes in the ocean. Premium hiking gear is but a hole in the mountain.

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…