Skip to main content

My waterproof pack and contents are still light enough

There is an advantage to having a waterproof pack so long as there are pockets and tie downs. There is also an advantage to having an extremely light pack like a ZPack Zero (4oz) and even though everything fits inside but with proper organization you probably won't notice the missing pockets.
Packs are one of the BIG-3 items you carry.
One recurring recommendation is to have a trash compactor bag as a pack liner. This is meant for non-waterproof bags where the contents might get wet. For example you might stuff your wet tarp at the bottom of the pack and then put your dry clothes inside the pack liner.


My Yukon El Capitan has arrived after being repaired and I filled it with an UltraLight set of gear. This kit assumes that my clothes will be sufficient to keep  me warm at night. As I recently reported that's not likely to be the case. I should have included my SOL bivy and the kit would be complete except that once you use the bivy it's next to impossible to put back in the stuff stack..

Contents:

  • pack
  • hammock, pad, pillow, groundsheet, tarp, stakes, guys and suspension
  • shemog, micro fiber towels
  • DIY hydration hose
  • gaiters
  • first aid
  • cordage
  • water kit
  • poncho/tarp
  • cook kit
  • EDC knife, compass, whistle, fero rod
  • fire kit
  • duct tape (wrapped on water bottle)
  • dirty water bottle
  • maps, guide book and data book
  • bear bag
Consumables:
  • water - 1L
  • instant coffee
  • snacks and dehydrated food (1.5 lbs per person per day)
I have not weighed this configuration yet but my intuition suggests it's under 10 pounds.

NOTES:
  • The tarp will either be dropped because I have the poncho/tarp or because the new Snugpak Stasha tarp is a better fit
  • The SOL bivy will be replaced with a real bivy as it is nearly impossible to put in it's stuff sack.
  • while I was able to get the sleeping pad rolled up there is no point in that. I'll probably leave it open in the future and put the manual pump and patch kit into the first aid kit

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…