Skip to main content

Bug Out Bag in Seattle

We were in Seattle for 9 days as a tourist. From time to time we went on extended drives from 1hr to 3hrs. Many of the longer drives were in the east where we were on single lanes, in the mountains, and most of the time we were alone.
On one occasion we were driving back to Bellevue when a deer jumped out and crossed the road. Had we not been paying attention we could have crashed ... the next car might not see us is we went over the edge of the road.
 What did I carry and what did I use?
  • first aid kit - USED, I'll probab ly get a smaller kit and put my flashlight and SAK in it
  • 2x micro towels - USED
  • folding knife - NO, next time I'll bring my SAK instead
  • sharpening stones - NO, leave it at home
  • cordage and zip ties - NO, too many bad actors out there and on the rise
  • flashlight - USED
  • lightweight rain jackets - NO, personal sheler is a must
  • stroller rain cover - NO, leave the stroller at home too
  • stuff sack with snacks - USED
  • 2x small travel games - USED
  • tarp - NO
  • nylon beach blanket with stakes 10x10ft - USED, on a beach because there was so much sand and the blanket cleaned easier than I expected the thermal blanket would; the kids still managed to get sand on the blanket.
  • thermal blanket 10x10ft - USED on grass because it was thicker than the nylon blanket but could have used stakes as the minor gusts still turned the corners
The extra space in my 30L bag was used for things we purchased, sweater, but no kids toys except for the two mini travel games. This bag was about survival and not play.

HINT - your B.O.B. has to be a bag that you're willing to carry no matter the situation. You cannot stare at your BOB in the car and think, I'll just leave it in there while we eat dinner. All-in or all-out.

That said, when I was in the airport I noticed that there was a guy that I would say was probably "an operator". He had no bags or things to carry. What was on him was all he seemed to need. That, to me, seems to be all you should need. I think I could managed with a 20L sling instead of a pack.

One thing that was missing was a high capacity power bank like the 26K Anker and a dual port car charger. I already have a 5 port charger but a 6-port high speed charger for base camp is a plus.

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…