Skip to main content

DIY groundsheet grommets

I have a bear paw minimalist 1 on order and it should arrive today or tomorrow. What makes it special is the [a] the configurations(see the videos in the link) [b] the weight [c] the net is attached to the SIL tub. Watching the configuration videos I realized that I could turn the minimalist upside down and use the SIL tub as a tarp. The narrator suggested that this was a "survival mode", however, this could actually be a "rain mode".

My concerns, however, is that the bugnet and the SIL are not as robust as my tyvek footprint. And so why not cut one down to size. And while I'm at it add some grommets to get the stakes exactly where I want them. So I dug out a prewashed tyvek footprint, went to Home Depot to get a grommet kit and proceeded to measure, cut and hammer.

Here is what I started with:

  • roll of gorilla tape
  • marker
  • 4 tent stakes
  • plastic mallet
  • grommet kit
  • tape measure
  • prewashed tyvek (from amazon)
  • insect shield 1 person bugnet from sea to summit

items

I taped the corners with about a 2" square of tape front an back. Then hammered the hole. Then hammered the grommet. When installing the grommet make sure that the smooth side is up and the burr is down.

the first grommet

all four grommets

I spread out the foorprint, hammered in the stakes, attached the bugnet. (the red tabs are supposed to be the head. Even though this is supposed to be a pyramid there must be some bias in the fabric. In this case it fit nicely 4' x 7'.


Finally I attached the peak of the pyramid to a hook above it. Notice the strange shape of the netting? The peak of the bugnet is 36" or 3'. I could have made it more taught, however, I think that it will actually be looser in the field especially since a person would be going in and out. Also trekking pole ridgelines are not as sturdy.


You have to look closely to the peak in order to see the slope of the line from the pyramid to the hook. I will probably cut the excess from the footprint and reuse it as a something to put my pack so it does not get dirty or when... a mini footprint. I'm going to use this footprint for the minimalist by adding shock cord to the loops.

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…