[Husker] Tom's Legacy - Response to jeff volk

[Kenneth McKillip]

Jon -

You always try to sneak in a jab at the talent Frank recruited.

Last time when presented with data you said you were wrong.  Why try it
again?

-----Original Message-----
From: husker-bounces at tssi.com [mailto:husker-bounces at tssi.com] On Behalf Of
jon johnston
Sent: Wednesday, December 05, 2007 9:00 AM
To: Jeff Volk
Cc: husker at tssi.com
Subject: [Husker] Tom's Legacy - Response to jeff volk

On Dec 5, 2007, at 8:47 AM, Jeff Volk wrote:

>
>
> Seriously, let's just say that the Pelini experience doesn't work. As
> the guy who hired him and was so vocal about what needed to change in
> the program (walkons, Nebraska kids, etc.) what is the risk to Tom's
> legacy IF this is a total flop?

Hmmmm.... you know, you come in here, put all your grenades in one  
basket and throw them at once. It's just not fair, man, so I'm picking  
the pieces I'll respond to.

So there.

Tom's legacy..... well, no matter what happens, Tom will always be one  
of the greatest college football coaches in history. That's over, done  
with, intact, and can't be taken away.

Now... his record and career as an administrator begins. And in one  
way you haven't mentioned, we rewind to yesterday. Had Frank stayed,  
the team's talent going downhill, if SP hadn't fired him, we would  
have fired both the athletic director and head coach (this isn't about  
whether or not the guy would have been successful, it's about a point  
of view), which is where we'll be if Tom's experiment doesn't work out.

Damage his legacy? Yeah, as a manager, he'll join a list of other guys  
who came back and failed.

In the big journey of Nebraska football, this has to happen. Tom  
Osborne has to return and we had to experience either his success or  
failure.

That's how the story is written.

Jon Johnston
http://www.cornnation.com



_______________________________________________
husker site list
husker at tssi.com
http://romaine.tssi.com/mailman/listinfo/husker

Note:  Comcast has been bouncing a lot of list traffic recently.  The
problem appears to be on their end.