Skip to main content

what's for breakfast -- cook kit

Over the years I've had a number of cook kits. I've watched in awe of Andrew Skirka's Chili and Fritos. I've boiled water for coffee, reheated pasta for my kids, made breakfast and so on. One thing I've done is complained about people who go minimalist on their cook kit and I get particularly grumpy about people with aluminium pot covers. On the one hand I'm apologizing and the other I'm not. It's complicated.

I have many stoves. small word burning stove, isobutone stove, 4 different alcohol stoves and a fuel tab stove. They each have their own problems....

Wood/twig stove - these stoves are great and great fun. The challenge is always having or finding dry wood and a safe and permissible place to flame up.

isobutane - these stoves are simply easy. But depending where you are hiking you might not be able to locate fuel. In many ways they are specialized. Certain general camping fuels can be found but still rare. The worst offense is that this stove makes a ton of noise.

alcohol - this stuff is easy to access. But it can get expensive depending on the quantity you actually want to carry and whether you want to buy medical grade.

gel - easier to come by and slightly safer than alcohol but harder to start. Sparkers and fero rods do not work well and I almost spilled it once. Not easy to extinguish.

tab - it's easy to use but so many fails... need a lighter, not easy to extinguish, smells, wrapper trash.

Keep in mind that depending on the ambient temp and the amount of water the amount of fuel to accomplish the task will vary.

The first experiment with the new stove was gel. This stove is multi-fuel capable.


I was not able to light the gel with my sparker or large fero rod. I almost knocked it over. After lighting the gel with a lighter I tested the alcohol function with the sparker.


The lop on this pot is not fastened well. I guess I realized that at some point you have to stop babying your gear and use it like it was meant. As I was using the water to make some breakfast tea I saw the freshness cover for the new can of ground coffee.


Given the heavy gauge I decided to use it as a lid.


That got me to thinking... can I make this smaller? So I made it smaller.


I decided that I was only going to take what would fit in the bag. While I have other stoves this one is low profile, efficient with fuel, multimode, and if I wanted I could replace the blue windscreen with the complementary wood stove.

Notice I have a knife in the kit. That could be relocated to the med kit.

Lastly, while some sort of single wall metal is required to heat your booty trying to drink from it when it's hot is another. Ti is the worst of all so a kettle with a collapsible silicon cup might make more sense. Furthermore, depending on how long you're traveling cold or instant might be better anyway.

Comments

Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

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…