Skip to main content

more about hammock suspension systems

Many fine bushcraft experts suggest NOT using 550 paracord for hammock suspension. Many believe that while it's strong enough on it's own there is simply too much stretch.

paramax 1000 and 550 paracord


I tried paramax 1000 by itself and had a number of problems. It would have been a convenient solution but the knot on the tree side fused with the working end and took effort to remove. The rope stretched and was near impossible to get a consistent lay. Finally I added tubular webbing to protect the tree and that just made it bulky. One other attempt included doubling the cord and while that distributed the stretch it was heavier and bulkier. All that was important as I was planning to hammock over water in the everglades.


Good for guy lines but not much else. Black hard to see. Very think, and strong, could easily cut flesh.


Whoopie sling and soft shackle is just plain complicated and still requires something to go around the tree. All this joinery can be risky. The reflective material was chintzy.


I tried singular and tubular webbing. The singular webbing fused just like the paramax. The knots also slipped. The tubular webbing was heavy and bulky although it did not fuse. However, it was slippery and the knots did not hold.


The Yukon suspension system held up nicely. It was much less bulky than the ENO Atlas and the Yukon cinch (not pictured) was even better. Both held the suspension, did not slip and while the cinch version was easily adjustable the segment model was fast. I would recommend a Dutch Hardware webbing hook to prevent the material to material abrasion.


While the packed webbing looks like they might be the same size.  The Yukon version is lighter and actually smaller by volume.

One unrelated item is my rope and s-biner to hank my pack from a tree.


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…