Dear Timothy, You should try rummaging through some /.ers' trash, you might get lucky and inherit a real computer for you to complain about... Regards, Linux

First, they didn't break 911, they somewhat broke E911. Subtle but important difference. there's 52 LMUs down, which means they can't trilaterate the position of 911 callers from Cell phones on the AT&T network in that area. It's probably a much bigger deal that several cell sites are unavailable. Lets just hope no ones life depends on it.

Elizabethtown College - about 7 miles from TMI as the crow flies (or the wind blows).

My sister went to school there, and after two and a half semesters there she was diagnosed with thyroid cancer.

Lets rewind... The morning of the accident people reported a metallic taste in the air. Turns out that of the gas released, radioactive iodine accounted for an estimated "8 - 12% of the total gases released, implying a minimum of 1 million iodine curies". See: TMI Accident.

I don't believe that people were not harmed by the radioactive release. In fact, stating that it "had little to no effect on the health of people" is a lie. Any arguments based on that lie are faulty.


I am for nuclear power, and I agree that letting bean counters manage a project like that is the wrong way. I'm in agreement with all of the other people here who think that engineers should be listened to. They are the ones with the knowledge after all...

On the other hand, MikroTik devices do suck.

Ever had the pleasure of dealing with one of these pieces of garbage?

Not that Cisco doesn't have problems (FWIW, I admin a fair sized Cisco network), but MikroTik routers give me a feeling in my gut that it's just about to break, any minute now... I could build a better router out of a PC and some NICs (and have - love OpenBSD)...

Disclaimer: my experience with MikroTik is from dealing with a particular Indian Contracting firm that uses them, and they also happen to have incompetent admins (willing to give me admin on their boxes to fix their problems - told 'em to deal with their own gear)... Maybe that's a commonality between MicroTik users?

Sounds like STP was configured poorly and you had a switching loop. I've seen it happen where one switch is configured wrong and make another switch's CPU peg, especially if the other switch decided to advertise itself as the root bridge and it didn't make sense.

:set nohlsearch