Skip to main content

Hammock or tent

That's a tough question and here is how it breaks down:
  • solo, companion or kids (individual or shared) - solo or companion camping is easy when you're using a hammock. Having younger kids in a hammock poses a number of security and technical challenges.
  • use the hammock as a chair? Depending on the orientation of the camp you might not need to brink a chair or a log to sit on.
  • trees available - if there are no trees for at least a ridgeline then you're going to be sleeping naked, so to speak.
  • disaster strikes and a pole breaks or a rope snaps - most kits have spare parts or you should be able to make it through the night. Chances are good you have spare cordage.
  • does your pack get wet - when tenting there is a good chance your pack will fit in the tent or you might be using it as a pillow. And if not it's in the vestibule. When using a hammock you might tie it to a tree, directly under your hammock, inside the hammock if there is room... but you have choices.
  • ground conditions - wet is wet.
  • mattress optional - in the right weather and with the right hammock a mattress might not be necessary.
  • 4-season - this could go multiple ways. There are examples of hammock in the winter but for the most part the camper is relying on a good sleeping bag and insulation from a pad as well as proper fly setup.
  • weight - they are close enough except that the tent get's some economy of scale as things are often integrated.
  • no-poles although the poles could be walking sticks and so they are serving multiple roles. Don't lose or break them.
  • cost - hammocks seem to be cheaper than the lightest tents.
One thing I like is choices and here is one combination I want to try:
  • Guardian basecamp bug net - what makes this interesting is that it has a tub-like bottom. This should keep some ground water from getting to you kit
  • House Fly - this fly is 10x10.
combining the two with or without the hammock gives you some choices whether to hang or not but keep in mind that they are considerably heavy at about 5 or 6 lbs.

However, if it's already raining, like it does in Florida, getting that rain fly into position makes the rest of the setup almost dry.

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…