Skip to main content

making coffee is the trail version of making copies

I decided to make some tea this morning but rather than using my electric kettle I decided to use my Solo Stove. The wood I used was birch that I purchase from the grocery store last month. Initially I tried to use my pocket knife to split the wood but that was unreasonable and I thought I might damage the blade since the birch is considered a hardwood. So I used my 8" Mora and was finished in a few minutes. I have a number of butane lighters in my kit but I like to practice with my SOL fire starters.

One serious disadvantage of this stove is that the stove is only a few inches deep. That means the sticks or wood it uses needs to be short. I suppose pine cones might be useful, however, they have tar in the soot. Hacking the wood to the correct size takes work. As much as I like a nice open flame and the ground does not burn there simply might not be enough deadfall to make a fire without a saw and/or ax.

here are my supples. I already processed some of the wood

made two feathersticks with my SAK and there is the SOL fire in the bottom right

making coffee (actually hot water)

steeping the tea. Had plenty of wood
Boil time for 16oz of water was 5 minutes. You can see from above that I did not need much wood at all. This is probably because birch is a hardwood and the bark was still attacked in many pieces.

nature's TV
Feeling good and refreshed. Gonna get a second cup. The wood was nearly completely exhausted. Nothing but crumbs.

"making copies" is a Saturday Night Live skit reference.


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: (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 answer all of the questio…

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…