Skip to main content

GDC - gerber daily carry

I really like my Ganzo. It was a recommendation made by Joe Robinet. In the meantime I  have destroyed the blade trying to freehand sharpen it... and I've also managed to partially recover the blade; but that's another story. In the meantime I wanted a second blade preferably one with a glass break but the only vendor on Amazon is taking weeks to deliver. So I've given up on them.

Fast forward I was also looking for a US made EDC and Gerber is one of those quintessential US brand names. They are also branding Bear Grylls a decidedly non-american. But Les Stroud was taken and also non-American. 

And so was born GDC. Gerber Daily Carry.

My understanding is the green ring is part of the GDC branding and as such there may be a few things missing here like the money clip. I'll not be reviewing the Gerber website. So let's look at these items.
  • belt tool- I guess it's for the person who wants to be branded GDC. The buckle and the belt are integrated. And since there is such a high contrast between the tool and the buckle your tool is not very stealthy
  • The zipper pull tools are just that. I suppose the knife or flashlight would work with my car key because I do not have a key ring but that thread is very thin and WILL work it's way off any keyring. I have yet to discover if or why I might need all 4 and where I would put them. By the time I attached them to my keyring I might as well get a Victorinox or a Leatherman.
  • The hook knife seems very sensible so long as it stays in it's sheath until called into action. I'm not sure how well it works when needed to cut a seat-belt and you have RF ignition. Deciding where to put your keys could be critical.
  • I like my Victorinox pocket knives. I usually keep it in my pocket with my wallet. I never put it in the pocket with my phone because the knife's metal parts could scratch the screen. So the Gerber folding pocket knife is practical in that it's rubberized with not exposed metal parts and it has a much larger blade. 
** there is a money clip, not pictured, without considering the blade and the sheath the money clip is very think.

In conclusion I think this line of products is a dud. The best two items are are not any more functional than my existing tools which include a tweezers and a toothpick.

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…