Journal FortKnox's Journal: BBSpot has a satire article that I've experienced (kinda) 8
Read the BBSpot article about BSOD chicken.
Freshman year of college at UC (University of Cincinnati), we did something like this, except it had a very /. twist to it (we crashed a UNIX server). When we had trouble finishing up a program (we had to do everything in UNIX with gcc for our programs), we had a little trick to get an extension...
For some reason, the gcc binary and all libraries existed only on our very poor sun server. So, if we ever had trouble finishing, once... say 11 or 12 at night rolled around and there was still a full ECECS lab full of us trying to finish, we'd call up the other lab, everyone would save what they had, then we'd countdown... 5..4..3..2..1.. COMPILE!
About 35+ people hitting the server all at once, and compiling ALWAYS meant doom for the server. The server would crash (hard), and it wouldn't be up until late the next morning. We'd come into class, and the prof would know the server was down and would give us an extra few days extension on the project. Unfortunately, though, the next year, they got a new server that we couldn't crash, and had to always finish on time ;-)
Speaking of my alma mater, did anyone else watch the UC/TCU football game last night on ESPN? It was one of the best games I've seen in a looong time. The UC quarterback was throwing up mortar with his bricks (no TD, and 4 interceptions), but came back in the last 3 minutes of the game to put it in overtime, then scrambled for a TD and TCU threw up an interception, ending the game. It was just a fabulous game!
Freshman year of college at UC (University of Cincinnati), we did something like this, except it had a very
For some reason, the gcc binary and all libraries existed only on our very poor sun server. So, if we ever had trouble finishing, once... say 11 or 12 at night rolled around and there was still a full ECECS lab full of us trying to finish, we'd call up the other lab, everyone would save what they had, then we'd countdown... 5..4..3..2..1.. COMPILE!
About 35+ people hitting the server all at once, and compiling ALWAYS meant doom for the server. The server would crash (hard), and it wouldn't be up until late the next morning. We'd come into class, and the prof would know the server was down and would give us an extra few days extension on the project. Unfortunately, though, the next year, they got a new server that we couldn't crash, and had to always finish on time
Speaking of my alma mater, did anyone else watch the UC/TCU football game last night on ESPN? It was one of the best games I've seen in a looong time. The UC quarterback was throwing up mortar with his bricks (no TD, and 4 interceptions), but came back in the last 3 minutes of the game to put it in overtime, then scrambled for a TD and TCU threw up an interception, ending the game. It was just a fabulous game!
funny story from my os class... (Score:1)
Several years ago he wanted a few forks, and was the first time he taught the class. Well, one student used a for loop that he thought iterated 10 times and tried it out on the dept system. You can probably figure out the rest from there.
TD (Score:2)
Also he was one to run in the overtime TD.
Re:TD (Score:1)
The sun boxes at ECECS's lab (Score:2)
Hate OT (Score:1)
Re:Hate OT (Score:2)
Re:Hate OT (Score:1)
I was thinking of writing something like that (how UC completely stuffed Ron Dayne), but decided against it
OT: MY Football Game of the Week. (Score:2)
LSU 24
Sorry, but I just had to get that out. :)