Skip to main content

Yama Mountain Flat Tarp

I ordered or rather I changed my order to an 8.5'x8.5' flat tarp. I never measured it until today and while I'd need to do it again for the exact numbers I give up. It's almost 9'x9'.

It's funny, before I deployed the tarp this morning I thought it was short as I was expecting a 10x10 and frankly had forgotten what I had ordered. So the measurement was weird... and not what I ordered anyway. But better longer/wider than shorter.

On one corner I used some shockcord to manage the tension. The corner material seems to pull evenly:

But in a different corner I did not use shockcord and the material protested:

Also, no one ever tells you where the seam sealer goes... on the inside or the outside. I always thought the inside because that's where BearPaw and Six Moon seemed to put it. In hindsight makes no sense because the water would penetrate the seam on the outside and rest in the seam until it evaporated or damaged the seam.  It took the yama design, with a d-ring on the inside to make this obvious.

ridgeline underside

ridgeline with sealed seams

Yama logo
I like that Yama included either shock cord or loops on each guy out point. It was simple to add a lineloc, shockcord and cordage. The tarp works well with a hammock in either a-frame or diamond. Being 9-feet square it's also reasonable for ground camping.


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…