Skip to main content

Review Schrade SCHF37

Most reviews I have watched lately compare one thing to another thing, however, I believe that bushcraft or camping knives can be a very personal thing. They say that in the worst of times it's the knife that can get you out. (or something like that).

I'm going through my knife collection one at a time... and in no particular order:

The SCHF37 was supposed to be my workhorse. When I made the purchase I was going to use my ax and saw to bulk cut my wood. Later I though the ax was over rated. Then the time came to prepare some wood and light a fire and I noticed a few things:

  • feathersticks are required
  • ax is still required
  • batoning is not for all blades and is hard work
  • gassification stoves need 2 - 4 inch sticks. Processing will take a while because you have to get the wood to a sufficient length and width
and so about the SCHF37
  • it's heavy which makes the last stage of processing easy
  • if it's not sharp the hacking requires a lot of energy
  • the coating severs to increase friction and seems to cause the blade to jump when making find feather sticks
  • because the blade is so heavy fine feathersticks are hard to make
  • the spine is 90 degrees but does not shred wood very well unless it's an edge
  • the diamond sharpener is ok
  • the fire steel is ok but using the spine of the knife took some time and the sparks were not as big as I'm used too
Given the length, weight and balance of the blade I found myself using the knuckle position on the blade itself and the section of the blade closest to the hilt.  The few times I was hacking I used the back hand position and the middle of the blade. Given my use case a point was not necessary (YET).

The sheath is made out of nylon strap with a plastic insert for the blade. I could not remove the insert to inspect it but there are some structural issues like getting sand or other junk in it; it simply does not clean well. The belt loop means not having to take your belt off and some cordage will prevent it from flapping. The snap used to keep the blade in the sheath is cheap and is already loose.

If I had to do all over again I would not make this purchase.

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…