Skip to main content

deciding between a 1-day and 2-day pack

At the risk of repeating myself I do not believe in the notion of "Survival Gear" as it pertains to the Florida Trail or any well traveled path with one exception.
Survival gear means there is a better than 50% chance you and your companions are going to perish and that what you need to carry is meant to extend your chances of rescue. The rule of 3s will tell you about you and the rule of Cs will tell you about stuff. SEAL training will tell you that you can take a lot of punishment... That said there is only one true piece of survival gear that offsets the rest. SPOT.
 That might seem a little black or white but it's harsh reality and of course there are some nice benefits especially while hiking in the Florida Everglades.

1-Day Pack (under 7lbs)
  • 18L or smaller pack
  • 1L clean, 1L dirty water bottles
  • water processing kit
  • 1P first aid kit
  • Rain gear
  • food (1lb per day or 1200 calories + 400 per hour)
2-Day Pack (under 10lbs)
  • 18L to 25L pack
  • 1-Day contents
  • extra food
  • optional stove for a warm meal
  • shelter (could be hammock or tent depending on location)
NOTE there are still some exceptions that depend on location. For example whenever I hike Robert's Lake I plan to bring a second pair of shoes. This is not about survival but safety as you could walk out barefoot but it's just no fun.

Hiking in the everglades I carry what I call a 1-Day Plus pack. It's essentially the 1-Day pack with the stove and shelter. The stove is all about making a coffee or mashed potatoes. The shelter is mostly about having some place to sit when the trail is under water; and since the hammock does not have a drain hole I need the rainfly/emergency blanket to keep the rain off. Lastly, the shelter kit includes an "emergency" (see above) bivy. It serves no purpose because I'm not going to b caught in a situation that requires it... it simply makes me feel good and at 4oz I'm OK with that.

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…