[EMAIL PROTECTED] wrote:
> lo is loopback. doesn't have to do with any real nics
Yes, but due to a bug in Aurora, it hangs on the last message that
succeeded, not the current one, which is the one that failed. In other
words, if my eth0 hangs when coming up, the last message I see in Aurora
is that it was trying to active interface lo. Logically, I would assume
that it's lo that failed... after all, Aurora hasn't even told me about
eth0 yet. so this may have been what happened here.
--
Sincerely,
David Walluck
<[EMAIL PROTECTED]>
