I’ve been somewhat concerned for a long time at what I’ve always thought to be a frightening lack of compassion and empathy from the huge majority of Americans. Shame on you.

Watch this:


It’s been said before that if you’re not angry, you’re not paying attention. Pay attention. Get angry.

Update: And, now, the narration from the video above. Why? Because it seemed appropriate to transcribe it:

It is no measure of mental health to be well-adjusted to a profoundly sick society.

I’m having a hard time biting my tongue.

As the world teeters on the edge of a financial debt tsunami, and a nuclear, ecological armageddon, I remain one hundred percent in awe by the fact that most of my friends, neighbors, and colleagues — people with whom I work on a daily basis, intelligent professionals — appear to be completely unphased, in fact, completely oblivious to the horrifying events now unfolding globally.

I spent countless hours on multiple conference calls recently with professionals around the country — Fortune 100 folks from the New York City, from the midwest, and LA — at no time during the entire week did any single person on those calls make any mention of the horrifying tsunami or the current nuclear nightmare unfolding in Japan. No mention of the possibility of radioactive fallout reaching our own shores. Or the lack of availability of potassium iodide across our nation. Not one person mentioned the death-blow to the Japanese economy — the third-largest economy on the planet. No mention of the collapsing dollar or the impact that all of this is bound to have on our own economy and future food prices.

Where is the empathy? The compassion? The concern for humanity? Or even on the most basic level, where is their sense of self-preservation? It’s as though these traits have been engineered out of the average detatched American.

And, now, this formerly-honorable nation is unconstitutionally attacking Lybia. Where is the resistance?

If you’re watching this video, you are the resistance.

The majority has checked out. They don’t care. And liberty breathes its last gasp.

The hour is getting very late, my friends. But do Americans even know it?

As John Williams of shadowstats.com has written in his recent special report, “The U.S. economic and systematic-solvency crisis of the last four years only have been precursors to the coming Great Collapse: a hyperinflationary great depression. Such will encompass a complete collapse in the purchasing power of the U.S. dollar. With no viable or politically-practical way of balancing U.S. fiscal conditions and avoiding this financial economic Armageddon, the best that individuals can do at this point to protect themselves, encompasses building a store of key consumables, such as food and water, and moving assets into physical precious metals and outside of the U.S. dollar.”

And, if you know people who still think it’s not Worry Time, please note for them Chris Martenson’s recent economic alert titled, Nuclear and Economic Meltdown in Progress. Chris notes in his emergency alert, “I have not been this concerned since October, 2008.”

Chris writes, “This alert warns you that major world-changing events are now underway and that your personal preparations for an uncertain future should either be completed or take on a new sense of urgency.”

My friends, these are sobering times. Yet so many of the people that we know in our daily lives remain drunk on pop-culture and nonsense. They do not recognize any of these dangers.

For those of us who are paying attention and who are showing the appropriate level of concern for our fellow human beings, our neighbors, and our families, it can feel like we are living in the Twilight Zone.

Friends, we must not lose faith and we must not lose hope, but we must take heed: we must speak out, and we absolutely must prepare.

Indeed. Be mindful of the future.

Linux Sudo Issue?


This post will make sense to probably about eight people on the planet. Posting here just in case I forget or so perhaps it can help explain this problem to the other seven people.

I just stumbled across this odd sudo issue on a couple of my servers when trying to do a password-less sudo through SSH. I want to be able to have a local user called sysadmin sudo a command (apt-get) to update the sources list and, if possible, run an automatic update without any interaction. We have 240 servers, so any sort of automation to make this easier is a good thing. (note: Landscape is not an option for us).

So, the basic thinking was that we would just add a NOPASSWD option to /etc/sudoers for the relevant command on every member server then from a management system (with appropriately-shared SSH keys, of course) we would just issue an SSH to that server followed by the appropriate sudo command, thus:

ssh sysadmin@someserver sudo apt-get update

On most of our systems, that works fine. But on a few, I keep seeing this:

sudo: no tty present and no askpass program specified

Well, that makes a little bit of sense. There’s no interactive TTY when using a one-shot through SSH like we’re doing. But if we add the needed ‘-t’ option to SSH, then we still get prompted for a password, which is contrary to what we put in /etc/sudoers on all of the member servers:

sysadmin        ALL=(ALL) NOPASSWD: /usr/bin/apt-get

So everything looks perfectly fine there, but then I got to thinking about it and remembered a feature of sudoers and started looking a bit closer. I realized that the affected systems had a few additional entries beneath this one. One of them is the Ubuntu-defined “%admin” group:

%admin ALL=(ALL) ALL

Well, sysadmin is a member of “admin”. And the %admin entry says that its members are allowed to run anything with elevated rights as long as a password is entered.


That little feature in /etc/sudoers is that entries are processed first to last. That is, if there’s another entry that applies later in the file, it always takes priority. In this case, the “sysadmin” account was a member of the local “admin” group and, because %admin was after sysadmin in sudoers, sudo was requiring that sysadmin enter a password to continue.

Our solution? Simply move the sysadmin entry to the bottom of the file, save, then try kicking off the command again.


I suppose it helps to understand the function you’re using.