"Eric W. Biederman" wrote: > > Be sure lo is established before eth0 and you won't see this message. > > Hmm. How does the interaction work. I've been meaning to track it for > a while but haven't yet. > > >From the cases I have observed it seems to be connected with arp requests > that aren't answered. (I.e when something is misconfigured and you try to nfsroot off > of the wrong ip on your subnet) > And I keep thinking neighbour table underflow would have been a better message. I'm not sure, I'm repeating what Alexey (iirc) has said in the past. I've been there/done that and sure enough making sure 'lo' is brought up first prevents that message. As to the NFS, no idea, I've never messed w/ nfsroot. -d
begin:vcard n:Ford;David x-mozilla-html:TRUE adr:;;;;;; version:2.1 email;internet:[EMAIL PROTECTED] title:Blue Labs Developer x-mozilla-cpt:;14688 fn:David Ford end:vcard
