Well, if that's the case, then it was a troll of a troll :-)

On Monday, September 29, 2014, Mike Hammett via Af <af@afmug.com> wrote:

> Trolling two people that clearly do not think highly of our senior senator.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
> ------------------------------
> *From: *"Jason McKemie via Af" <af@afmug.com
> <javascript:_e(%7B%7D,'cvml','af@afmug.com');>>
> *To: *af@afmug.com <javascript:_e(%7B%7D,'cvml','af@afmug.com');>
> *Sent: *Monday, September 29, 2014 7:27:31 PM
> *Subject: *Re: [AFMUG] Arson attack on FAA datacenter
>
> To what are you referring? I'm pretty skeptical of mainstream media FYI.
>
> On Monday, September 29, 2014, Mike Hammett via Af <af@afmug.com
> <javascript:_e(%7B%7D,'cvml','af@afmug.com');>> wrote:
>
>> Do you live under a bridge?
>>
>>
>>
>> -----
>> Mike Hammett
>> Intelligent Computing Solutions
>> http://www.ics-il.com
>>
>> ------------------------------
>> *From: *"Jason McKemie via Af" <af@afmug.com>
>> *To: *af@afmug.com
>> *Sent: *Monday, September 29, 2014 7:23:11 PM
>> *Subject: *Re: [AFMUG] Arson attack on FAA datacenter
>>
>> Little bit of haterism going on here, he's one of the better ones IMO.
>> Does he not hang out upstate enough for you guys?
>>
>> On Monday, September 29, 2014, Mike Hammett via Af <af@afmug.com> wrote:
>>
>>> +1
>>>
>>>
>>>
>>> -----
>>> Mike Hammett
>>> Intelligent Computing Solutions
>>> http://www.ics-il.com
>>>
>>> ------------------------------
>>> *From: *"George Skorup (Cyber Broadcasting) via Af" <af@afmug.com>
>>> *To: *af@afmug.com
>>> *Sent: *Monday, September 29, 2014 5:07:43 PM
>>> *Subject: *Re: [AFMUG] Arson attack on FAA datacenter
>>>
>>> Damn, why couldn't it be Durbin that slit his own throat.
>>>
>>> On 9/29/2014 5:04 PM, That One Guy via Af wrote:
>>>
>>> im going with isis on this
>>>
>>> On Mon, Sep 29, 2014 at 4:44 PM, Nate Burke via Af <af@afmug.com> wrote:
>>>
>>>>  This is only a couple miles from our office.  They had all the local
>>>> news choppers up in the air over it on Friday.  I was surprised that it
>>>> didn't garner more national coverage.  I guess since it wasn't the terror
>>>> threat of the day, it didn't get any traction.  Just a disgruntled
>>>> employee.  Even the first reports said it was not a terrorist act.
>>>>
>>>>
>>>> On 9/29/2014 4:36 PM, Forrest Christian (List Account) via Af wrote:
>>>>
>>>>  Oh yeah,
>>>>
>>>>  I'm in Chicago for a few days.  Flew in on thursday before this
>>>> happened.   My wife flew in on Saturday and ended up with a nasty delay in
>>>> MSP since there were very very few flights flying into the affected area,
>>>> which basically includes both chicago airports, and the two airports up in
>>>> wisconsin.  Thousands of flights cancelled over the last couple of days.
>>>>
>>>>  That's the big news here.
>>>>
>>>> -forrest
>>>>
>>>> On Mon, Sep 29, 2014 at 3:24 PM, Eric Kuhnke via Af <af@afmug.com>
>>>> wrote:
>>>>
>>>>> Anyone see this?
>>>>>
>>>>>
>>>>> http://posttrib.suntimes.com/30167722-537/flight-delays-to-continue-after-arson.html#.VCnNuOeXtGE
>>>>>
>>>>>
>>>>> http://www.metafilter.com/143174/ATCSCC-ADVZY-020-DCC-ZAU-09-26-2014-ZAU-GROUND-STOP
>>>>>
>>>>>
>>>>>
>>>>> On Friday, ATCSCC Advisory 20 of 26-Sep-2014 went out. When operators,
>>>>> controllers and airport managers saw the title, a gasp of disbelief was
>>>>> heard. The problem was simple enough to state in three words, and complex
>>>>> enough to cancel thousand of flights and cost hundred of millions of
>>>>> dollars: ZAU ATC ZERO
>>>>> <http://www.fly.faa.gov/adv/adv_otherdis.jsp?advn=20&adv_date=09262014&facId=DCC/ZAU&title=ZAU+GROUND+STOP&titleDate=09/26/14>
>>>>> .
>>>>>
>>>>> ZAU
>>>>> <http://en.wikipedia.org/wiki/Chicago_Air_Route_Traffic_Control_Center>
>>>>> is the call sign of the Chicago Air Rout Traffic Control Center (ARTCC),
>>>>> which covers <http://www.fly.faa.gov/Information/west/zau/zau.htm>
>>>>> northern Illinois and Indiana, southern Wisconsin, western Iowa, and south
>>>>> eastern Michigan. There are two "sides" at an ARTCC. ZAU-LO handed traffic
>>>>> destined for airports in the covered area, ZAU-HI handled traffic
>>>>> overflying. Both were amongst the busiest in the country. ZAU-HI was busy
>>>>> with traffic from the east to west, as well as European traffic heading to
>>>>> Houston and Dallas-FW, ZAU-LO had to feed in traffic from airports like
>>>>> GYY <http://en.wikipedia.org/wiki/Gary/Chicago_International_Airport>,
>>>>> MKE
>>>>> <http://en.wikipedia.org/wiki/General_Mitchell_International_Airport>,
>>>>> RFD
>>>>> <http://en.wikipedia.org/wiki/Chicago_Rockford_International_Airport>,
>>>>> PIA
>>>>> <http://en.wikipedia.org/wiki/General_Wayne_A._Downing_Peoria_International_Airport>,
>>>>> and the two busiest airports in the area; Chicago Midway International
>>>>> <http://en.wikipedia.org/wiki/Chicago_Midway_International_Airport>
>>>>> and O'Hare International
>>>>> <http://en.wikipedia.org/wiki/O%27Hare_International_Airport>, one of
>>>>> the busiest airports in the world.
>>>>>
>>>>> On Friday morning, Brian Howard, a contract employee of the FAA and
>>>>> holding full credentials to the ZAU datacenters, set a fire in the telecom
>>>>> room, destroying 23 of the 29
>>>>> <http://posttrib.suntimes.com/30167722-537/flight-delays-to-continue-after-arson.html>
>>>>> rack and disconnecting all the controller stations from the associated
>>>>> radars and radio transmitters needed to watch and guide traffic through 
>>>>> the
>>>>> busy sector. As the consoles dropped offline, the ZAU duty manager had no
>>>>> choice -- they called ZZZ, the FAA command center
>>>>> <http://www.fly.faa.gov/flyfaa/usmap.jsp> and reported ATC ZERO -- no
>>>>> controllers available, control center offline.
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>  --
>>> All parts should go together without forcing. You must remember that the
>>> parts you are reassembling were disassembled by you. Therefore, if you
>>> can't get them together again, there must be a reason. By all means, do not
>>> use a hammer. -- IBM maintenance manual, 1925
>>>
>>>
>>>
>>>
>>
>

Reply via email to