Skip to main content

axes, saws, and knives; oh my!

I got it wrong ... in fact I have no idea what right is. I thought:
  • with a saw that I would not need an ax
  • with a longer/heavy duty blade I would not need an ax because I could baton and scrape
and so my kit started looking heavy duty and frankly I went overboard.
  • I got an ax anyway
  • a bowie
  • 7in full tang
  • 4.5in full tang
  • folding knife as an EDC
** full tang and non-folding were all part of the initial driver

I started testing this set but processing some very soft and dry wood. Except where the branches once were the wood was ultra soft, the bark flew off in every direction, and because I did not have a processing anvil I could not really swing any of the implements without being concerned about hitting the concrete below.

And now I encountered a second stream of advice:
  • no coatings on the blade
  • no baton
  • only scandi grind
  • scandi grind on the ax
  • full tang not necessary
  • making feather sticks with a scandi grind ax
  • light weight and strong
And so my thoughts and emotions started to swing the other way. And now I'm disturbed. I watched some youtube episodes of Alone and I recognized many different use-cases. Ax was necessary. Saw was still good but less necessary. Most splitting would be done with the ax and the tinder could be processed with a small blade. The scandi grind is probably easier to field sharpen. Coated knives not to much as you have to polish thru the coating in addition to the task at hand.

So I have no idea which is the best knife or "system". I think it's partly the use-cases you commonly encounter and secondarily which systems you become confident with.

PS: I'm surprised how much recognition the Swedish get for bushcraft. Whether it's Mora, scandi grind or the Swedish Fire Torch, tents, hammocks they seem to be in the middle.

UPDATE:  I forgot to add a few things:

  • serrated blades are time consuming to sharpen
  • dark and camo colors are difficult to see in a pak or on the ground (face it, if you're not in the military or trying to evade capture then bright is better; and if that's not an option then a lanyard is a requirement.)
  • how you wear your know is also very important. [a] inside your jacket [b] clipped on a belt [c] looped through a belt [d] on a lanyard [e] companion mounted [f] mounted to pak
  • plastic, leather or strap case. Compression, velcro or snaps. [a] One of my leather cases disintegrated.  [b] straps are already starting to fray.

Popular posts from this blog

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…

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.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…