Skip to main content

DIY Just a couple of tarp things

I really like my 2GoSystems Reflex 100 but depending on what I'm doing my snugpak 9x5.5' packs smaller and weights less. The only problem, except for Snugpak's customer service and product support, is that the tarp is missing a few tie outs. Since I do not have a sewing machine I'm pretty much stuck with my own whits.

simple clip from Dutchware
The toggle forces the jaw together applying pressure to the target between the jaws. My Snugpak nylon tarp is too thin on it's own so I used SilNet glue to stick a small patch of webbing to the tarp in the place where a tieout should have been. The glue has been left to cure using the clip as a vice. Now I'm ready to pitch it and see what happens.

SilNet glue to hold the webbing on one side

One problem with my tarp setup, overall, is that when I deploy my SeaToSummit Bugnet there is nothing to hang the net from unless I deploy a ridgeline and sometimes that is just not practical. One recommendation was to use a circular velcro tab and then create a loop from some velcro wire ties. Depending on the adhesive on the dots this could be a cool setup since the bugnet is under 3oz.

small hook and loop
My last project is just an experiment because I do not have a sewing machine. Using some lineloks and some SilNet glue I applied to the webbing and folded it back on itself. Then I used a number of clips to apply pressure and hopefully the glue will seep into the webbing. This setup will let me use two lines per ridge pole.

3-6 hours to dry.


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…