Skip to main content

sharpening stones

I was watching a bushcraft demonstration of sharpening a bushcraft knife using a Nagura and  DC4. And having no appreciable skills sharpening knives I bought these stones right away.

In the demo my mentor used the DC4, and a little spit to create a slurry from the Nagura. And after he was finished he wiped the DC4 on his pant leg and said one could use the Nagura directly on the blade. As I started sharpening my EDCs I noticed that the Nagura was getting stained. Luckily I bought the stone on Amazon and there is a way to ask questions from the seller.

From what I understand from the seller's response the slurry was the right approach. There is a need to keep the Nagura flat. Then again that might mean using a second stone to keep the Nagura flat. It was also recommended that the Nagura be carried in it's box (not with my purchase) or in a ziplock bag.

In the midst of the confusion I also purchased a WorkSharp.

Keeping the blade at the correct angle is simple enough. At some point it should become second nature. It's also small enough that it'll fit in my pack without being a bother. In fact I'll carry both.

Finally, while a different bushcrafter commented that fire was nature's TV he also said that knife sharpening your knife is just one of those things you do with your down time. It's relaxing and calming.

Making your own sharpening stone from sandpaper and carpet tape.

Mors makes the point.... 10 strokes on coarse, 30 strokes on fine, 300 strop. Watch the end of the video, stopping is meant to generate heat which knocks down the floppy bit. Stropping is meant to get the blade shaving sharp. If you can cut paper then skip coarse. a knife can be sharp enough that it cannot bite into the paper.

According to Mors, a sharp blade can last 20hrs. I'm not sure if that means 20hrs of use or just holding for 20hrs. Seems a bit weak that ambient temperature and humidity would dull a blade in 20hrs.

I'm getting some additional comments on the caring for the Nagura stone. Seems that creating the slurry on the DC4 is the way to go. On the other hand Mors demonstrated using double sided carpet tape and some high grit sandpaper to make my own stone. (and a belt as a strop).

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…