Skip to main content

Cordage for your tarp or tent

One of the required items in the "Five C's" is "cordage" but other than a passing recommendation to use 550 paracord that's about where the recommendation stops. In recent weeks I had been testing 550 and 750 paracord, string, bankline, zing-it or catzeye.

I'll start with some of my troubles here.
  • zing-it or catzeye is strong but just too slippery to use with prusik knots
  • bankline is terrible as a ridgeline because it stretches and the goop stains everything
  • string does not handle water well and breaks easy
  • by the time you put that sort of tension on a 750 knot the fibers melt making it difficult to untie
  • 550 is about 4mm in diameter and for all that weight and volume it's normal uses are limited; granted the diameter makes it easy to handle and it is strong... but you're not putting 550 pounds of pressure on a guy line.
not included in the list is "Reflx; reflective guylines" from litesmith. It comes in 3 diameters including 1.1mm, 1.5mm, and 2.3mm. I now have 100ft of all three sizes.

you have to look closely to see the size differences here as their distance from the lens varies enough to distort the relative sizes.

the real size differences
What is great about this line is that it works well, is strong and holds a knot. 100ft of each of different sizes do not take much volume, they are strong, and highly reflective. Just look at the next picture.

1.1mm Reflx - the reflection of light makes it appear thicker than it actually is.
 
The only complaint that I might have with the 1.1mm line is that undoing a knot is painful or just difficult. I decided to use line-lok adjusters and they worked better than I expected... that and I also moved the stakes for more macro adjustments.

I still like paracord, however, 80, 120, 275 are probably better for my needs. As for Reflx... I'm not trying to be stealthy so glow in the dark packs and cordage are OK with me.

Comments

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: http://www.eeti.com.tw/drivers_Linux.html (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 setup.sh answer all of the questio…

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…