Skip to main content

20 things to carry ... maybe not

As I've mentioned a few times; I'm going hiking and I want to take a few things with me. Some things I will check and others I will carry on. There are a few items that I think are sketchy so I have followed up with the TSA directly.

In the meantime I also read this article and while there may be some good advice in there it's also worth putting on your thinking cap or at least shipping your tools instead of checking them. Here is the list this person presented Dec 2014.

Anything I mark with an OK is still subject to change and interpretation from the TSA.
  1. scissors - NOT OK - there isn't any circumstance where this would be ok.
  2. first aid kit - MAYBE depends on what is in it. Needles and scisors are not permitted without a letter from your doctor
  3. 550 paracord - OK, I would be inclined to include a few large zip ties too but that's not my job.
  4. water purification tables - OK
  5. water filter - OK
  6. collapsible water bottle - OK
  7. extra socks - OK
  8. BIC disposable lighter NOT OK, it does not matter how small the flame is there are no circumstances where this would be ok. Don't even try. Plan to buy a new BIC when you get to your destination.
  9. fero rod - NOT OK, I got the details from the TSA directly on this one
  10. cash - MAYBE, depends on how much and whether you are crossing the border or laundering money
  11. silver coins - MAYBE, depends on how much and whether you are crossing the border or laundering money
  12. N95 masks - OK, but is there is anything in the material that might trigger a second look you might get a few strange stares.
  13. hand sanitizer - MAYBE, check the 3-3-1 rules.
  14. bleach wipes - OK
  15. SAS survival guide - OK
  16. subblock - MAYBE, check the 3-3-1 rules.
  17. space blanket - OK, however the blanket will likely trigger a second search of your stuff due to the reflective nature of the blanket.
  18. compass - OK
  19. mini Cree flashlight - OK
  20. Listerine - MAYBE, check the 3-3-1 rules.
Reading this persons post I think it must have been partly sarcastic because some of the choices are simply wrong. Scissors.


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…