Skip to main content

Bug Out Bag

A bug out bag is defined as a bag that you might keep in your vehicle or close to the door such that if you have to go into survival mode or at least have the best chance ... you need these things.

The bug out bag shopping list came from this video.

Rule of 3s - Survival
In any extreme situation you cannot survive for more than:
  • 3 minutes without air
  • 3 hours without shelter
  • 3 days without water
  • 3 weeks without food.
The 5 Cs
  • cover
  • cut
  • combustion
  • container
  • cordage
**If you have the technical skills and the time to execute then all you really need is cut and container. You can make everything else depending on the environment. And some tools simply make it easier or are time savers.

I have an amazon BOB List. It's a nearly complete shopping list. It's not the cheapest but it is almost complete in that it's meant for bugging out and not camping. I have a few other lists but no need to be distracted by them. (the wish list does not indicate quantity but there are a few items that need to be duplicated.)


While BOB List was inspired by the video there were a number of things that were missing and in retrospect I think there are a few more. One thing I learned from the History Channel's Alone project is that you gotta have a few days worth of food. MREs are complete and somewhat fun and there are all forts of prepper options out there. Living in Florida they tell us to have 4 days food and water. This is a different type of survival, however, I live near the North New River Canal and the Conservation Levee Greenway. If we have to leave it would be in a hurry and we may or may not have our cars etc...

This is where things get expensive but in the previous list you were prepared to eat the family pet as the end of days was upon you. The reality is the next survival scenario is just a mild inconvenience. But you still have to wait out the storm and so you need some items.

  • food
  • flashlights
  • generate power and or heat - gasoline, biolite stove and solar
  • store power in power bank
  • weather radio
  • walkie talkies
  • amateur radio
  • generator
  • air conditioner
  • cooler(s)
  • water for drinking and flushing
  • maps
  • pens, pencils
  • important numbers
  • family calling tree
  • batteries, rechargeable batteries
  • a daily routine
  • tents, sleeping bags, mattress, sheets, cots
I need to review the NOAA documentation.

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…