Skip to main content

Review: Schrade SCHF42D

As I started outfitting myself for my next unscheduled camping trip I started watching bushcraft videos trying to decide what features I wanted in a knife. With a little foreshadowing many of those check boxes are gone.

Assuming I was going to use a saw and a bushcraft knife to process wood my list looked like:

  • full tang
  • cordage loop
  • non-serrated edge
  • balanced
  • non-folding
  • large blade (5")
At the time I was on the fence between the Mora and the SCHF42D. At the time I was not able to determine if Mora was Morakniv. There were other vendors selling other knives that were so similar and I was already seeing ghosts on eBay and Amazon so I went for a less common route.

In hind-site the blade is coated but it's not textured so there is no additional friction but the blade was not sharp from the factory. I've managed to put an edge on the blade and it fulfills the bullshit paper test but it is very hard to sharpen. My Smith's Pocket sharpened started off ok but is now sharpening unevenly. Finally it was the first knife of the group that gave me a victory when creating feather sticks.

I have a few regrets:
  • leather sheath, does not clean well and can dull the blade
  • I'm starting to rethink about the usefulness of an ax and so a blade this big might not be necessary. I think my kit will include a folding saw, a Silky, an ax or hatchet, and a knife
  • The blade is coated and while it seems to be some sort of electrolysis and not adding to the overall thickness of the blade or adding friction it likely means that the blade is prone to rusting.
  • The color of the blade is not conspicuous and it could be easily lost at dusk. One could always attach ome reflective or glowing cordage but that's not the point.
  • Batoning is nor the ideal use-case
  • recent chips in my bowie knife suggests I need a harder blade
I've also underestimated the potential of my old and trusty Case Mako folder and my new Ganzo folder.

I think the SCHF42D is going to be the knife I leave at the bottom of the tackle-box for those moments when I forget or misplace everything else.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


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…