I believe that was a symptom of not listing lo0 first in the network
interfaces line in rc.conf - try checking that?
On Sat, 22 Jan 2000, Matt M. wrote:
> I cvsupd current, and did a make buildworld last night - i didn't do make
> installworld - now when i boot my system (when it is initializing
-On [2122 17:17], Matt M. ([EMAIL PROTECTED]) wrote:
>I cvsupd current, and did a make buildworld last night - i didn't do make
>installworld - now when i boot my system (when it is initializing the
>network) I get a message that is similar to "cannot allocate llinfo for
>/kernel" - i tried an
I cvsupd current, and did a make buildworld last night - i didn't do make
installworld - now when i boot my system (when it is initializing the
network) I get a message that is similar to "cannot allocate llinfo for
/kernel" - i tried an older kernel and i got the same message. I am using
DHCP, so
I forgot to mention that the network is no longer functional with these
error messages.
> I cvsupd current, and did a make buildworld last night - i didn't do make
> installworld - now when i boot my system (when it is initializing the
> network) I get a message that is similar to "cannot alloca
I cvsupd current, and did a make buildworld last night - i didn't do make
installworld - now when i boot my system (when it is initializing the
network) I get a message that is similar to "cannot allocate llinfo for
/kernel" - i tried an older kernel and i got the same message. I am using
DHCP, so
