Skip to main content

Review: Schrade SCHF45

My motive is described here.

The Schrade Bowie knife is a big knife with a huge blade. I'm not certain what benefit there is to this blade design but I decided to buy one because if the settlers in the 1700 could survive on this knife, as I channeled Davy Crocket and Daniel Boone, then I could find a use for it too. I was also thinking an ax was not necessary and that the Bowie could do that job.

I tried processing some birch wedges but it was impossible. The wood was much too hard and going against the grain in any direction only served to dull the blade. I never got to batoning, with the grain, but I imagine it will work great and put into service might fall some standing deadwood.

Unlike the previous Schrade this one has a gunmetal colored blade that might be a coating but is not textured. The 90 degree spine took the firesteel on the first try.

Finally the sheath is hard plastic or poly-whatever. There is no drainhole so it will become a cup if it's raining and it requires taking your belt off to wear it. There are some holes in the case for lashing it to a rucksack. The blade flops and makes some noise in the sheath and the velcro handle lash is pasable but that's it. This knife mist be in the upright or horizontal position.

This knife is a maybe. If I were on the show naked and afraid I think I would not leave home without it. As a replacement for an ax it is a little smaller and fits in my bag and so it might be a better hatchet than an ax.

UPDATE: The bowie made fast work of a troublesome tree. But now I have two huge chips in the blade. I think a hatchet would have been a better tool. As for my missing machete I think I'll put that behind me and move the bowie from my camping kit to the garden tool chest.

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…