Skip to main content

buyers remorse the Appellation Trail

I'm not doing the Appellation Trail (AT) any time soon but there are some ideas that I have been reading that leave me with knife buyers remorse.

I have been collecting knives since I started going head first into self-training bushcraft. I'd watch a few videos and then review some of the equipment people were using and then watch a dozen knife and tent reviews. And then the boxes start rolling in from Amazon.

I recently wrote about my knife collection. Some were complete shit. In retrospect they are still complete shit but I also do not need 10 Mora knives. One or two would have been fine and I should just have stopped there.Supplemented by a SAK.

In the meantime I watched a vlog


and although the conclusion is that hammock camping is fun/preferred for the presenter he was quick to explain that it's [a] expensive [b] heavy [c] complicated [d] difficult to get consistent.  I've, separately, commented that hammock camping is not permitted it all campgrounds and that there is a danger in hammock camping with respect to hanging on dead trees or weak roots and so on.

Back to the AT... [a] some segments of the trail do not permit ground campfires [b] in some places fires are only permitted in the fixed shelters [c] and in some segments tools like saws or axes are not permitted. I recently posted that many US National parks to not permit open fires and those that do are only in designated pits.

The author went on to say [a] many thru hikers do not cook on the AT. They bring water and foodstuffs that do not require cooking. [b] he went on to mention things like Hostels which leads me to believe that while water can be found on the trail you're likely to exit the trail to get fresh water. Without heat to purify water you'll need chemicals or a filter system.

Anyway, back to knives.

With yet another place where fires are not permitted my knives are kinda useless. I really only need the few where I can practice my skills in the backyard or the campground fire pit.

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…