A number of comments have claimed this: recompile with 64-bit time_t and the problem goes away. Unfortunately, for many apps it's not quite as simple as that.

Certainly, for those apps which only deal with time information internally, and in a transient fashion, this will be sufficient to eliminate the problem.

However any program which persists UNIX timestamps in files, or sends UNIX timestamps as part of a networking protocol, or basically anything which sends the data structure outside the application is still going to require work on how to handle the migration.

What happens if your app is required to talk on the network? If there are few enough machines involved, then sure, you can upgrade all of them at once, but if it's a large or distributed operation, there needs to be a transition plan. How will older clients and newer clients interoperate?

If data is saved, how will the recompiled application interpret old files? Does it need a way to distinguish them? Can old data be automatically converted? Are there cases where old data may be compromised? (e.g. those 30 year mortgages probably have the wrong end-date stored...) How will we handle those cases?

What about situations where time information is used to prime other calculations - is it okay to affect those other calculations? Serial numbers, PRNGs, UUID generation, etc - the situation has to be assessed. Many cases might be fine, but you can't make a blanket statement for all cases, so each calculation must be vetted.

In the end, the result is that there is work to do. Much of it will be easy to fix, but the assessment still needs to be done.

Vader did say that, however

Vader: No, Luke. I am your father.

Except that he didn't, we just remember it that way... He says "No, I am your father".

https://www.google.com/search?q=No+Luke+I+am+your+father

It's one of the standard misquotes... Like all these "quotes" which never happened:

  * Luke, I am your father.
  * Play it again, Sam
  * Elementary, my dear Watson
  * Beam me up, Scotty
  * Are you feeling lucky, punk?
  * I want to suck your blood
  * Me Tarzan, you Jane
  * Here's another fine mess you've gotten us into
  * Greed is good

Nice map.

In the past, http://mapvisage.appspot.com/fires/FireMap.html did a pretty comprehensive job...

And the Australian Government runs http://sentinel.ga.gov.au/ which has even more information available...

Also: http://www.hanselman.com/blog/ConfiguringTwoWirelessRoutersWithOneSSIDNetworkNameAtHomeForFreeRoaming.aspx

http://forums.whirlpool.net.au/forum-replies.cfm?t=1143019

http://superuser.com/questions/122441/multiple-access-points-for-the-same-ssid

http://www.velocityreviews.com/forums/t3972-ssid-for-multiple-access-points.html

And conversely, if people CAN stream videos and play mp3s without major configuration and grief, who cares what version the Linux kernel is at?

(Nerds like us, that's who...)

FTFY:

Almost, but not quite...

International Committee for Robot Arms Control
http://icrac.net/

Call to boycott killer robots
http://www.monash.edu.au/news/show/call-to-boycott-killer-robots

Sparrow, R., 2012, "Just say no" to drones, IEEE Technology and Society Magazine [P], vol 31, issue 1, IEEE, United States, pp. 56-63
http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=6163996 (not free - some excerpts at http://www.intropy.co.uk/2012/07/just-say-no-to-drones.html )

"No evil robots"
http://www.cs.sfu.ca/~vaughan/noevilrobots.html

Sounds like the old Magnatune idea... http://en.wikipedia.org/wiki/Magnatune

Seriously? I previewed and everything! :-S

At a guess, the link was probably supposed to be http://csimadmax.deviantart.com/art/she-rarity-199414368 and accidentally got an extra 6 appended to it...

At a guess, the link was probably supposed to be and accidentally got an extra 6 appended to it...

"Great, the government raising the cost of yet another service,"

The government is stopping subsidizing a service which should never have been subsidized, by closing an unnecessary loophole.